RFC 9154: Extensible Provisioning Protocol (EPP) Secure Authorization Information for Transfer
In plain English — editorial summary, not part of the RFC
The Extensible Provisioning Protocol (EPP) (RFC 5730) defines the use of authorization information to authorize a transfer of an EPP object, such as a domain name, between clients that are referred to as "registrars". Object-specific, password-based authorization information (see RFCs 5731 and 5733) is commonly used but raises issues related to the security, complexity, storage, and lifetime of authentication information. This document defines an operational practice, using the EPP RFCs, that leverages the use of strong random authorization information values that are short lived, not stored by the client, and stored by the server using a cryptographic hash that provides for secure authorization information that can safely be used for object transfers.
Document record
- Document ID
- RFC9154
- Published
- December 2021
- Authors
- J. Gould; R. Wilhelm
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- ops
- Pages
- 22
- Also known as
- —
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 9874Best Practices for Deletion of Domain and Host Objects in the Extensible Provisioning Protocol (EPP)Current
September 2025
- 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?