[rpp] Re: New Version Notification for draft-kowalik-rpp-data-objects-03.txt

[Pawel Kowalik <[e-mail]>]

Hi,

the -03 version of RPP data objects document has now full coverage for 
domain, host and contact objects incl. DNSSEC ext. and RGP ext.
DNS data model was added - aligned with draft-simmen-rpp-dns-data-01.
Extensibility has been described better.

I think this document is now almost complete in the terms of scope of 
what it should describe.
There are still some open TODOs and questions that I would like to 
discuss in WG session:

- shall we carry over "urgent" flag from RFC 9364 ?
- is it still a best practice to include AuthInfo in every object info 
read operation for sponsoring client? Maybe it shall be separated or 
only retrieved with a special flag?
- shall restore report be carried over in the current form from EPP, or 
maybe simplified/generalised?
- is this draft the right place to describe business logic (example RGP 
in 2.5.5.)? If not, where?

Kind Regards,
Pawel


On 02.03.26 22:37, [e-mail] wrote:
> A new version of Internet-Draft draft-kowalik-rpp-data-objects-03.txt has been
> successfully submitted by Pawel Kowalik and posted to the
> IETF repository.
>
> Name:     draft-kowalik-rpp-data-objects
> Revision: 03
> Title:    RESTful Provisioning Protocol (RPP) Data Objects
> Date:     2026-03-02
> Group:    Individual Submission
> Pages:    79
> URL:      https://www.ietf.org/archive/id/draft-kowalik-rpp-data-objects-03.txt
> Status:   https://datatracker.ietf.org/doc/draft-kowalik-rpp-data-objects/
> HTML:     https://www.ietf.org/archive/id/draft-kowalik-rpp-data-objects-03.html
> HTMLized: https://datatracker.ietf.org/doc/html/draft-kowalik-rpp-data-objects
> Diff:     https://author-tools.ietf.org/iddiff?url2=draft-kowalik-rpp-data-objects-03
>
> Abstract:
>
>     This document defines data objects for the RESTful Provisioning
>     Protocol (RPP) and sets up IANA RPP Data Object Registry to describe
>     and catalogue them.  Specifically, it details the logical structure,
>     constraints, and protocol operations (including their inputs, outputs
>     and business logic) for foundational resources: domain names,
>     contacts, and hosts.  In accordance with the RPP architecture
>     [I-D.kowalik-rpp-architecture], these definitions focus entirely on
>     the semantics, remaining independent of any specific data
>     representation or media type (e.g., JSON or XML).
>
>
>
> The IETF Secretariat
>
>