RFC 9874: Best Practices for Deletion of Domain and Host Objects in the Extensible Provisioning Protocol (EPP)
In plain English — editorial summary, not part of the RFC
The Extensible Provisioning Protocol (EPP) includes commands for clients to delete domain and host objects, both of which are used to publish information in the Domain Name System (DNS). EPP also includes guidance for deletions that is intended to avoid DNS resolution disruptions and maintain data consistency. However, operational relationships between objects can make that guidance difficult to implement. Some EPP clients have developed operational practices to delete those objects that have unintended impacts on DNS resolution and security. This document describes best current practices and proposes new potential practices to delete domain and host objects that reduce the risk of DNS resolution failure and maintain client-server data consistency.
Document record
- Document ID
- RFC9874
- Published
- September 2025
- Authors
- S. Hollenbeck; W. Carroll; G. Akiwate
- Status
- BEST CURRENT PRACTICE
- Stream
- IETF
- Area
- ops
- Pages
- 18
- Also known as
- BCP244
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 9803Extensible Provisioning Protocol (EPP) Mapping for DNS Time-to-Live (TTL) ValuesCurrent
June 2025
- RFC 9154Extensible Provisioning Protocol (EPP) Secure Authorization Information for TransferCurrent
December 2021
- RFC 8334Launch Phase Mapping for the Extensible Provisioning Protocol (EPP)Current
March 2018
- RFC 5910Domain Name System (DNS) Security Extensions Mapping for the Extensible Provisioning Protocol (EPP)Current
May 2010
- RFC 5734Extensible Provisioning Protocol (EPP) Transport over TCPUpdated
August 2009
- RFC 5733Extensible Provisioning Protocol (EPP) Contact MappingCurrent
August 2009
- RFC 5732Extensible Provisioning Protocol (EPP) Host MappingCurrent
August 2009
- RFC 5731Extensible Provisioning Protocol (EPP) Domain Name MappingCurrent
August 2009
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?