RPP Architecture
draft-kowalik-rpp-architecture-03
| Document | Type |
Replaced Internet-Draft
(rpp WG)
Expired & archived
|
|
|---|---|---|---|
| Authors | Paweł Kowalik , Maarten Wullink | ||
| Last updated | 2025-10-27 (Latest revision 2025-10-10) | ||
| Replaced by | draft-ietf-rpp-architecture | ||
| RFC stream | Internet Engineering Task Force (IETF) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Additional resources |
GitHub Repository
Mailing List Mailing List Archive Mailing list discussion |
||
| Stream | WG state | Adopted by a WG | |
| Document shepherd | (None) | ||
| IESG | IESG state | Replaced by draft-ietf-rpp-architecture | |
| Consensus boilerplate | Unknown | ||
| 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:
Abstract
Advancements in development, integration, deployment environments and operational paradigms have led to a desire for an alternative for the Extensible Provisioning Protocol (EPP). This document defines the architecture for the RESTful Provisioning Protocol (RPP) an HTTP based provisioning protocol leveraging the REST architectural style and JSON data-interchange format, aiming to standardize a RESTful protocol for provisioning database objects. The architecture includes support for extensibility, allowing for multiple possible use cases. RPP is intended to co-exist with EPP, offering an alternative protocol including data model compatibility with EPP core objects and the benefits associated with the REST architectural style and widely adopted HTTP-based technologies.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)