Cite this STD: TXT
STD 69 contains the following RFCs:| Number | Files | Title | Authors | Date | More Info | Status |
|---|---|---|---|---|---|---|
| RFC 5730, STD 69 | Extensible Provisioning Protocol (EPP) | S. Hollenbeck | August 2009 | Obsoletes RFC 4930, Errata | Internet Standard | |
| RFC 5731, STD 69 | Extensible Provisioning Protocol (EPP) Domain Name Mapping | S. Hollenbeck | August 2009 | Obsoletes RFC 4931, Errata | Internet Standard | |
| RFC 5732, STD 69 | Extensible Provisioning Protocol (EPP) Host Mapping | S. Hollenbeck | August 2009 | Obsoletes RFC 4932 | Internet Standard | |
| RFC 5733, STD 69 | Extensible Provisioning Protocol (EPP) Contact Mapping | S. Hollenbeck | August 2009 | Obsoletes RFC 4933 | Internet Standard | |
| RFC 5734, STD 69 | Extensible Provisioning Protocol (EPP) Transport over TCP | S. Hollenbeck | August 2009 | Obsoletes RFC 4934, Updated by RFC 8996, Errata | Internet Standard |
Abstract of RFC 5730
This document describes an application-layer client-server protocol for the provisioning and management of objects stored in a shared central repository. Specified in XML, the protocol defines generic object management operations and an extensible framework that maps protocol operations to objects. This document includes a protocol specification, an object mapping template, and an XML media type registration. This document obsoletes RFC 4930. [STANDARDS-TRACK]
Abstract of RFC 5731
This document describes an Extensible Provisioning Protocol (EPP) mapping for the provisioning and management of Internet domain names stored in a shared central repository. Specified in XML, the mapping defines EPP command syntax and semantics as applied to domain names. This document obsoletes RFC 4931. [STANDARDS-TRACK]
Abstract of RFC 5732
This document describes an Extensible Provisioning Protocol (EPP) mapping for the provisioning and management of Internet host names stored in a shared central repository. Specified in XML, the mapping defines EPP command syntax and semantics as applied to host names. This document obsoletes RFC 4932. [STANDARDS-TRACK]
Abstract of RFC 5733
This document describes an Extensible Provisioning Protocol (EPP) mapping for the provisioning and management of individual or organizational social information identifiers (known as "contacts") stored in a shared central repository. Specified in Extensible Markup Language (XML), the mapping defines EPP command syntax and semantics as applied to contacts. This document obsoletes RFC 4933. [STANDARDS-TRACK]
Abstract of RFC 5734
This document describes how an Extensible Provisioning Protocol (EPP) session is mapped onto a single Transmission Control Protocol (TCP) connection. This mapping requires use of the Transport Layer Security (TLS) protocol to protect information exchanged between an EPP client and an EPP server. This document obsoletes RFC 4934. [STANDARDS-TRACK]
For the definition of Status, see RFC 2026.
For the definition of Stream, see RFC 8729.