[rpp] Re: I-D Action: draft-ietf-rpp-architecture-01.txt

[Pawel Kowalik <[e-mail]>]

Hi,

the new version of RPP architecture aligns the document with the current 
version of requirements draft-ietf-rpp-requirements-03.

As a baseline for actual standard design documents, the editors consider 
this document as complete and ready for WG review.

List of changes  -00 to -01

    *  Extension Mechanisms
       -  Refactoring of Extension mechanisms Section and addition of
          extensibility with transient request parameters and responses
          (Issues #94 and #95)
       -  Added HTTP Headers to the "extension-mechanisms" section (Issue
          #93).
       -  Added Extension Security and Extension Review Sections to
          Section 5.4 (Issue #91).

    *  Service Discovery & Profiles
       -  Added data privacy to Service discovery mechanisms and new
          "Data privacy" section.  Refactored the whole section
          Section 5.1.22 (Issue #100).
       -  Added Advertising of maintenance notices to "Service Discovery"
          section.  (Issue #88)
       -  Added text about compatibility profiles to "Profiles" section.
          (Issue #29)

    *  Collections, Bulk Operations & Filtering
       -  Added Section Collection Representation for API-level
          collection retrieval and expanded container element description
          in Data Elements Section.  (Issue #85)
       -  Extended Collection Representation to clarify that bulk
          operations, listing, and filtering are optional and must not be
          mandated where they negatively impact scalability or
          performance (Issue #41).

    *  Security & Authentication
       -  Added "additional measures to verify the client" to
          Section 5.1.3.4 (Issue #76).
       -  Added TLS mandatory to Section 5.1.1 (Issue #78).
       -  Create "Credential management" section for updating credentials
          using an extension.
       -  Added Section Section 5.1.3.5 for credential and token
          revocation/replacement mechanisms (Issue #79).
       -  Added text about signing messages in the "Message verification"
          section.  (Issue #33)
       -  Added reference to RFC9154 in the "Object level authorisation"
          section.  (Issue #89)

    *  HTTP Layer
       -  Added "Canonical Addressing" section (Issue #81)
       -  Added "Optionality" section to explicitly allow empty HTTP
          message body in a response (Issue #97).
       -  Fixed inconsistent usage of HTTP status codes (Issue #108).

    *  Resource Definition & Data Model
       -  Added a "Relationships" section to describe resource type
          relationships.  (Issue #83)
       -  Added Section Required and Optional Data Elements to Data
          Elements to explicitly address protocol-level vs. server-
          policy-level data element requirements (Requirement R4.3).
       -  Added Server-Managed Resources Section to HTTP Transport Layer
          Details and Server-Managed Resource Types Section to Resource
          Definition Layer to define read-only server-managed resources
          (Issue #84).
       -  Explicitly state that all parties involved in a process are
          allowed to retrieve the process status.  (Issue #98)
       -  Added Section Section 5.1.15 to describe poll message
          equivalent (Issue #87).

    *  Protocol Behaviour
       -  Changed default validation from lenient to strict. (Issue #82)
       -  Added "Scalability" section.  (Issue #92)

    *  Editorial & Terminology
       -  Added IDN to "Terminology" and "Service discovery mechanisms"
          sections
       -  Added boilerplate IANA Considerations section
       -  Editorial: updated document references

Kind Regards,
Pawel

On 27.02.26 17:38, [e-mail] wrote:
> Internet-Draft draft-ietf-rpp-architecture-01.txt is now available. It is a
> work item of the RESTful Provisioning Protocol (RPP) WG of the IETF.
>
>     Title:   RPP Architecture
>     Authors: P Kowalik
>              M Wullink
>     Name:    draft-ietf-rpp-architecture-01.txt
>     Pages:   42
>     Dates:   2026-02-27
>
> 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 standardise 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.
>
> The IETF datatracker status page for this Internet-Draft is:
> https://datatracker.ietf.org/doc/draft-ietf-rpp-architecture/
>
> There is also an HTML version available at:
> https://www.ietf.org/archive/id/draft-ietf-rpp-architecture-01.html
>
> A diff from the previous version is available at:
> https://author-tools.ietf.org/iddiff?url2=draft-ietf-rpp-architecture-01
>
> Internet-Drafts are also available by rsync at:
> rsync.ietf.org::internet-drafts
>
>
> _______________________________________________
> rpp mailing list -- [e-mail]
> To unsubscribe send an email to [e-mail]