RFC 8334 on Launch Phase Mapping for the Extensible Provisioning Protocol (EPP)
rfc-editor@rfc-editor.org Mon, 05 March 2018 19:28 UTC
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ietf-announce@ietfa.amsl.com
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AC31012E8A3; Mon, 5 Mar 2018 11:28:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.21
X-Spam-Level:
X-Spam-Status: No, score=-4.21 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, 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 4TUt_3qka1GI; Mon, 5 Mar 2018 11:28:44 -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 9CA2012DA6B; Mon, 5 Mar 2018 11:28:41 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id 3B61BB80DAD; Mon, 5 Mar 2018 11:28:26 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 8334 on Launch Phase Mapping for the Extensible Provisioning Protocol (EPP)
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, regext@ietf.org
Content-type: text/plain; charset="UTF-8"
Message-Id: <20180305192826.3B61BB80DAD@rfc-editor.org>
Date: Mon, 05 Mar 2018 11:28:26 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/sJtC2RdO7aQDJX-zEPWmqMMGJBY>
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf-announce/>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 05 Mar 2018 19:28:49 -0000
A new Request for Comments is now available in online RFC libraries. RFC 8334 Title: Launch Phase Mapping for the Extensible Provisioning Protocol (EPP) Author: J. Gould, W. Tan, G. Brown Status: Standards Track Stream: IETF Date: March 2018 Mailbox: jgould@verisign.com, wil@cloudregistry.net, gavin.brown@centralnic.com Pages: 58 Characters: 106211 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-regext-launchphase-07.txt URL: https://www.rfc-editor.org/info/rfc8334 DOI: 10.17487/RFC8334 This document describes an Extensible Provisioning Protocol (EPP) extension mapping for the provisioning and management of domain name registrations and applications during the launch of a domain name registry. This document is a product of the Registration Protocols Extensions 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