[rfc-dist] RFC 8590 on Change Poll Extension for the Extensible Provisioning Protocol (EPP)

rfc-editor@rfc-editor.org Fri, 10 May 2019 19:48 UTC

Return-Path: <rfc-dist-bounces@rfc-editor.org>
X-Original-To: ietfarch-rfc-dist-archive@ietfa.amsl.com
Delivered-To: ietfarch-rfc-dist-archive@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B8C671200F1 for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Fri, 10 May 2019 12:48:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.2
X-Spam-Level:
X-Spam-Status: No, score=-5.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable 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 Xs5emzOgBfkE for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Fri, 10 May 2019 12:48:01 -0700 (PDT)
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 CD4FC12006D for <rfc-dist-archive-yuw6Xa6hiena@ietf.org>; Fri, 10 May 2019 12:48:01 -0700 (PDT)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id 1BAE7B81727; Fri, 10 May 2019 12:47:54 -0700 (PDT)
X-Original-To: rfc-dist@rfc-editor.org
Delivered-To: rfc-dist@rfc-editor.org
Received: by rfc-editor.org (Postfix, from userid 30) id DE2E2B81715; Fri, 10 May 2019 12:47:51 -0700 (PDT)
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: <20190510194751.DE2E2B81715@rfc-editor.org>
Date: Fri, 10 May 2019 12:47:51 -0700 (PDT)
Subject: [rfc-dist] =?utf-8?q?RFC_8590_on_Change_Poll_Extension_for_the_E?= =?utf-8?q?xtensible_Provisioning_Protocol_=28EPP=29?=
X-BeenThere: rfc-dist@rfc-editor.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: RFC Announcements <rfc-dist.rfc-editor.org>
List-Unsubscribe: <https://www.rfc-editor.org/mailman/options/rfc-dist>, <mailto:rfc-dist-request@rfc-editor.org?subject=unsubscribe>
List-Archive: <http://www.rfc-editor.org/pipermail/rfc-dist/>
List-Post: <mailto:rfc-dist@rfc-editor.org>
List-Help: <mailto:rfc-dist-request@rfc-editor.org?subject=help>
List-Subscribe: <https://www.rfc-editor.org/mailman/listinfo/rfc-dist>, <mailto:rfc-dist-request@rfc-editor.org?subject=subscribe>
Cc: drafts-update-ref@iana.org, regext@ietf.org, rfc-editor@rfc-editor.org
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: rfc-dist-bounces@rfc-editor.org
Sender: "rfc-dist" <rfc-dist-bounces@rfc-editor.org>

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

        
        RFC 8590

        Title:      Change Poll Extension for the 
                    Extensible Provisioning Protocol (EPP) 
        Author:     J. Gould,
                    K. Feher
        Status:     Standards Track
        Stream:     IETF
        Date:       May 2019
        Mailbox:    jgould@verisign.com, 
                    ietf@feherfamily.org
        Pages:      20
        Characters: 39444
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-regext-change-poll-12.txt

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

        DOI:        10.17487/RFC8590

This document describes an Extensible Provisioning Protocol (EPP)
extension for notifying clients of operations on client-sponsored
objects that were not initiated by the client through EPP.  These
operations may include contractual or policy requirements including,
but not limited to, regular batch processes, customer support
actions, Uniform Domain-Name Dispute-Resolution Policy (UDRP) or
Uniform Rapid Suspension (URS) actions, court-directed actions, and
bulk updates based on customer requests.  Since the client is not
directly involved or knowledgable of these operations, the extension
is used along with an EPP object mapping to provide the resulting
state of the postoperation object, and optionally a preoperation
object, with the operation metadata of what, when, who, and why.

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


_______________________________________________
rfc-dist mailing list
rfc-dist@rfc-editor.org
https://www.rfc-editor.org/mailman/listinfo/rfc-dist
http://www.rfc-editor.org