Best Practices for Deletion of Domain and Host Objects in the Extensible Provisioning Protocol (EPP)
draft-hollenbeck-regext-epp-delete-bcp-03
| Document | Type |
Replaced Internet-Draft
(regext WG)
Expired & archived
|
|
|---|---|---|---|
| Authors | Scott Hollenbeck , William Carroll , Gautam Akiwate | ||
| Last updated | 2024-02-19 (Latest revision 2024-01-17) | ||
| Replaced by | draft-ietf-regext-epp-delete-bcp | ||
| RFC stream | Internet Engineering Task Force (IETF) | ||
| Intended RFC status | Best Current Practice | ||
| Formats | |||
| Additional resources | Mailing list discussion | ||
| Stream | WG state | Adopted by a WG | |
| Document shepherd | Andy Newton | ||
| IESG | IESG state | Replaced by draft-ietf-regext-epp-delete-bcp | |
| Consensus boilerplate | Yes | ||
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | andy@hxr.us |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
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 includes guidance concerning those 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 practices to delete domain and host objects that reduce the risk of DNS resolution failure and maintain client-server data consistency.
Authors
Scott Hollenbeck
William Carroll
Gautam Akiwate
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)