Skip to main content

Registry Lock Extension for the Extensible Provisioning Protocol (EPP)

Document Type Expired Internet-Draft (individual)
Expired & archived
Author Ulrich Wisser
Last updated 2022-01-08 (Latest revision 2021-07-07)
RFC stream (None)
Stream Stream state (No stream defined)
Consensus boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Expired
Telechat date (None)
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:


This extensions defines an additional protective layer for changes to domain [RFC5731], host [RFC5732] and contact [RFC5733] objects managed through EPP. EPP allows changes to objects only by the sponsoring client. EPP objects are usually managed by the sponsoring client on behalf of the sponsoring clients customers. All of these interactions are ususally fully automated. In case of a system breach, there is no protection in EPP to changes to any object by the intruder. This extension defines a protective layer that aims to break automated changes and work flows by requiring manual intervention. The actual form of manual intervention is out-of-scope for this document. By whom and how changes can be made is up to the registry and registrars to decide.


Ulrich Wisser

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)