A new Request for Comments is now available in online RFC libraries.
BCP 244
RFC 9874
Title: Best Practices for Deletion of
Domain and Host Objects in the
Extensible Provisioning Protocol (EPP)
Author: S. Hollenbeck,
W. Carroll,
G. Akiwate
Status: Best Current Practice
Stream: IETF
Date: September 2025
Mailbox: [email protected],
[email protected],
[email protected]
Pages: 18
See Also: BCP 244
I-D Tag: draft-ietf-regext-epp-delete-bcp-10.txt
URL: https://www.rfc-editor.org/info/rfc9874
DOI: 10.17487/RFC9874
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.
This document is a product of the Registration Protocols Extensions Working
Group of the IETF.
BCP: This document specifies an Internet Best Current Practices for the
Internet Community, and requests discussion and suggestions for
improvements. 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 [email protected]. Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.
The RFC Editor Team
_______________________________________________
rfc-dist mailing list -- [email protected]
To unsubscribe send an email to [email protected]
http://www.rfc-editor.org
