RFC 8748: Registry Fee Extension for the Extensible Provisioning Protocol (EPP)
In plain English — editorial summary, not part of the RFC
Given the expansion of the DNS namespace and the proliferation of novel business models, it is desirable to provide a method for Extensible Provisioning Protocol (EPP) clients to query EPP servers for the fees and credits associated with various billable transactions and provide expected fees and credits for certain commands and objects. This document describes an EPP extension mapping for registry fees.
Document record
- Document ID
- RFC8748
- Published
- March 2020
- Authors
- R. Carney; G. Brown; J. Frakes
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- ops
- Pages
- 30
- Also known as
- —
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 8749Moving DNSSEC Lookaside Validation (DLV) to Historic StatusCurrent
March 2020
- RFC 8762Simple Two-Way Active Measurement ProtocolUpdated
March 2020
- RFC 8767Serving Stale Data to Improve DNS ResiliencyCurrent
March 2020
- RFC 8777DNS Reverse IP Automatic Multicast Tunneling (AMT) DiscoveryCurrent
April 2020
- RFC 8791YANG Data Structure ExtensionsCurrent
June 2020
- RFC 8792Handling Long Lines in Content of Internet-Drafts and RFCsCurrent
June 2020
- RFC 8704Enhanced Feasible-Path Unicast Reverse Path ForwardingCurrent
February 2020
- RFC 8806Running a Root Server Local to a ResolverCurrent
June 2020
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?