[regext] RFC 8056 on Extensible Provisioning Protocol (EPP) and Registration Data Access Protocol (RDAP) Status Mapping
rfc-editor@rfc-editor.org Tue, 17 January 2017 22:00 UTC
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: regext@ietfa.amsl.com
Delivered-To: regext@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C76551295E4; Tue, 17 Jan 2017 14:00:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.401
X-Spam-Level:
X-Spam-Status: No, score=-7.401 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-3.199, SPF_HELO_PASS=-0.001, SPF_PASS=-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 CLSd-DiSqCV7; Tue, 17 Jan 2017 13:59:59 -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 19CEF1295D2; Tue, 17 Jan 2017 13:59:59 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id 09E96B8016A; Tue, 17 Jan 2017 13:59:59 -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
Message-Id: <20170117215959.09E96B8016A@rfc-editor.org>
Date: Tue, 17 Jan 2017 13:59:59 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/regext/veqsOiOmJwzxELSUrVHumQYBqGU>
Cc: drafts-update-ref@iana.org, regext@ietf.org, rfc-editor@rfc-editor.org
Subject: [regext] RFC 8056 on Extensible Provisioning Protocol (EPP) and Registration Data Access Protocol (RDAP) Status Mapping
X-BeenThere: regext@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Registration Protocols Extensions <regext.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/regext>, <mailto:regext-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/regext/>
List-Post: <mailto:regext@ietf.org>
List-Help: <mailto:regext-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/regext>, <mailto:regext-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 17 Jan 2017 22:00:08 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 8056
Title: Extensible Provisioning Protocol (EPP) and
Registration Data Access Protocol (RDAP) Status
Mapping
Author: J. Gould
Status: Standards Track
Stream: IETF
Date: January 2017
Mailbox: jgould@verisign.com
Pages: 11
Characters: 22084
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-regext-epp-rdap-status-mapping-04.txt
URL: https://www.rfc-editor.org/info/rfc8056
DOI: 10.17487/RFC8056
This document describes the mapping of the Extensible Provisioning
Protocol (EPP) statuses with the statuses registered for use in the
Registration Data Access Protocol (RDAP). This document identifies
gaps in the mapping, and registers RDAP statuses to fill those gaps
to ensure that all of the EPP statuses specified in RFCs are
supported in RDAP.
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