Draft:RESTful Provisioning Protocol
Where to get help
How to improve a draft
You can also browse Wikipedia:Featured articles and Wikipedia:Good articles to find examples of Wikipedia's best writing on topics similar to your proposed article. Improving your odds of a speedy review To improve your odds of a faster review, tag your draft with relevant WikiProject tags using the button below. This will let reviewers know a new draft has been submitted in their area of interest. For instance, if you wrote about a female astronomer, you would want to add the Biography, Astronomy, and Women scientists tags. Editor resources
|  |
 | This is a draft article. It is a work in progress open to editing by anyone. Please ensure core content policies are met before publishing it as a live Wikipedia article. Find sources: Google (books · news · scholar · free images · WP refs) · FENS · JSTOR · TWL Last edited by Mdavids (talk | contribs) 3 months ago. (Update)
Finished drafting? |
 | The topic of this draft may not meet Wikipedia's general notability guideline. (September 2025) |
| Communication protocol | |
 RPP WG Logo | |
| Abbreviation | RPP |
|---|---|
| Purpose | Automated domain name transactions like registrations and renewals |
| Developer | Internet Engineering Task Force (IETF) |
| Introduction | 2025 |
The RESTful Provisioning Protocol (RPP) is a proposed series of IETF specifications aimed at a modern, web-native protocol for provisioning domain names, hosts, and contacts via HTTPS and JSON. It is intended to provide communication between domain name registries and domain name registrars whenever a domain name is registered or renewed. It is designed as a RESTful complement to the XML-based Extensible Provisioning Protocol (EPP), leveraging common web tools like OpenAPI, API gateways, and RESTful principles to improve scalability and integration.
History
- November 2023: RPP concept introduced at IETF118 in Prague,[1] initially presented to REGEXT WG.
- September 2024: BOF proposal approved.[2]
- February 2025: IESG formally approves the RPP charter; WG officially formed.
- March 2025: First WG meeting and hackathon held during IETF 122 in Bangkok.
See also
- Extensible Provisioning Protocol (EPP)
- Registration Data Access Protocol (RDAP)
- Richardson Maturity Model
Trivia
The concept originated in 2012 under the name "RESTful EPP (REPP)", in a draft authored by SIDN.
External links
- IETF Charter for RPP Working Group
- GitHub organisation for WG
- IETF Wiki for RPP
- APNIC blog: RESTful Provisioning Protocol: From vision to IETF Working Group
- DENIC blog: RPP: Why Registries and Registrars Should Help Shape the Future of Domain Provisioning
- AFNIC blog: RPP, a future protocol for creating and managing domain names
- RPP blog from the Estionian Internet Foundation
- SWITCH Report 2024 - page 56
- Announcement at ICANN81, November 2024
References
- ^ "RESTful Provisioning Protocol at CENTR R&D Workshop" (PDF). sidnlabs.nl. 2024-10-09. Retrieved 2025-06-18.
- ^ "RESTful Provisioning Protocol - Approved BOF request". ietf.org. 2024-09-27. Retrieved 2025-06-18.
Content Disclaimer
Informasi ini disarikan dari Wikipedia dan disajikan kembali untuk tujuan edukasi. Konten tersedia di bawah lisensi CC BY-SA 3.0. Kami tidak bertanggung jawab atas ketidakakuratan data yang bersumber dari kontribusi publik tersebut.
- The information displayed on this website is sourced in part or in whole from Wikipedia and has been adapted for the purpose of restating it. We strive to provide accurate and relevant information, however:
- There is no guarantee of absolute accuracy. Wikipedia is an open, collaborative project that can be edited by anyone, so information is subject to change.
- It is not intended to constitute professional advice. The content displayed is for informational and educational purposes only. For important decisions (e.g., medical, legal, or financial), please consult a professional.
- Content copyright. Wikipedia is licensed under the Creative Commons Attribution-ShareAlike License (CC BY-SA). This means that content may be reused with appropriate attribution and shared under a similar license.
- Responsible use. Any risk arising from the use of information from this website is entirely the responsibility of the user.
- provide significant coverage: discuss the subject in detail, not just brief mentions or routine announcements;
- are reliable: from reputable outlets with editorial oversight;
- are independent: not connected to the subject, such as interviews, press releases, the subject's own website, or sponsored content.
Please add references that meet all three of these criteria. If none exist, the subject is not yet suitable for Wikipedia.