Search RFCs

RFC Editor

File formats:

Status:

PROPOSED STANDARD

Authors:

J. Gould
K. Feher

Stream:

IETF

Source:

regext (art)

Cite this RFC:TXT  | XML  |  BibTeX

DOI:  https://doi.org/10.17487/RFC8590

Discuss this RFC: Send questions or comments to the mailing listregext@ietf.org

Other actions:View Errata  | Submit Errata  | Find IPR Disclosures from the IETF  | View History of RFC 8590

Abstract

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

For the definition ofStatus,seeRFC 2026.

For the definition ofStream, seeRFC 8729.