RFC 8590: Change Poll Extension for the Extensible Provisioning Protocol (EPP)
In plain English — editorial summary, not part of the RFC
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.
Document record
- Document ID
- RFC8590
- Published
- May 2019
- Authors
- J. Gould; K. Feher
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- ops
- Pages
- 20
- Also known as
- —
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 8585Requirements for IPv6 Customer Edge Routers to Support IPv4-as-a-ServiceCurrent
May 2019
- RFC 8583Diameter Load Information ConveyanceCurrent
August 2019
- RFC 8582Diameter Overload Rate ControlCurrent
August 2019
- RFC 8581Diameter Agent Overload and the Peer Overload ReportCurrent
August 2019
- RFC 8608BGPsec Algorithms, Key Formats, and Signature FormatsCurrent
June 2019
- RFC 8572Secure Zero Touch Provisioning (SZTP)Updated
April 2019
- RFC 8618Compacted-DNS (C-DNS): A Format for DNS Packet CaptureCurrent
September 2019
- RFC 8624Algorithm Implementation Requirements and Usage Guidance for DNSSECObsoleted
June 2019
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?