[rpp] Fwd: I-D Action: draft-ietf-rpp-requirements-03.txt

[Maarten Wullink <[e-mail]>]

Hi,

We’ve published version -03 of the requirements document, we ask that the chairs now start a consensus call.

When there is consensus about the requirements, then we can continue with the design work, we can always return to the requirements document to
update it when necessary.

The idea is to put this requirements document on hold for now, and publish it as an Informational RFC when we are done.

-
Maarten


Summary of changes:

    • Added reference to tiger team extension lists to A1.3 and A2.3
    • Add R9.16 to support registry operator use-case on authorization
    • Renamed section "Operations and responses" to "Operations and request handling" (Issue #140)
    • "Common" section of "(#req_for_object_type, use title)" clearly structured (Issue #140)
    • Corrected numbering in "(#privacy_considerations, use title)" section. DP1.5 added with a clear reference to other privacy-related requirements (Issue #140)
    • Added introduction to "(#data_model, use title)" and "(#data_representation, use title)" sections for clarity (Issue #140)
    • Moved R11.4 from "(#scalability, use title)" to "(#performance, use title)" as R12.5 for better section fit (Issue #140)
    • Functional Equivalent defined as term (Issue #140)
    • Changed R12.2, D2.4 and C2.3 from MAY to SHOULD (Issue #139)
    • Changed R8.6 from SHOULD to MUST (Issue #139)
    • Removed R7.10 and D1.7 (Issue #139)
    • Changed R6.4 from MUST to SHOULD (Issue #139)
    • Fixed Typos and references (Issue #139)
    • Moved R6.1, R6.2 and R6.3 to R5.14, R5.15 and R5.16 respectively (Issue #139)
    • Revised and added necessary teminology (Issue #26)
    • Updated R4.3 to only mandate data fields that are strictly necessary
    • Merged R7.9 and R5.10 (Issue #124)
    • Updated R4.4 to better describe profiles (Issue #15)
    • Removed mandatory password change facility in R9.10. Added extensibility requirement in R10.16 and an essential extension in A1.2 (Issue #70)
    • Replaced O1.1 with R5.13 and updated R10.14 (Issue #125)
    • Added requirements R2.5, R10.15 and R10.3 (changed) related to Generic Protocol Design Recommendations from the Tiger Team recommendations [@?TigerTeamRecc]
    • Added Acknowledgements section




> 
> Internet-Draft draft-ietf-rpp-requirements-03.txt is now available. It is a
> work item of the RESTful Provisioning Protocol (RPP) WG of the IETF.
> 
>   Title:   RESTful Provisioning Protocol (RPP) - Requirements
>   Authors: Maarten Wullink
>            Pawel Kowalik
>   Name:    draft-ietf-rpp-requirements-03.txt
>   Pages:   33
>   Dates:   2025-12-05
> 
> Abstract:
> 
>   This document describes the requirements for the development of the
>   RESTful Provisioning Protocol (RPP).
> 
> The IETF datatracker status page for this Internet-Draft is:
> https://datatracker.ietf.org/doc/draft-ietf-rpp-requirements/
> 
> There is also an HTML version available at:
> https://www.ietf.org/archive/id/draft-ietf-rpp-requirements-03.html
> 
> A diff from the previous version is available at:
> https://author-tools.ietf.org/iddiff?url2=draft-ietf-rpp-requirements-03
> 
> 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]