Hi Gavin, Just gave an initial read. I’m not quite sure of the use-case that would motivate this, other than trying to eliminate round-trips. But maybe that’s the point. :-)
One bit of initial feedback: In section 3, I was expecting to see “MUST” in this sentence: “When determining whether to include a related object in the <ro:infData> element, servers SHOULD apply the same access control rules that are used to determine whether a client is authorised to perform an <info> on those objects.” I don’t understand why the protocol would allow the server to use different access rules for the same data accessed via a different path. Thanks Rick From: regext <regext-boun...@ietf.org> on behalf of Gavin Brown <gavin.br...@centralnic.com> Date: Monday, March 27, 2023 at 8:03 PM To: regext@ietf.org <regext@ietf.org> Subject: [EXTERNAL] [regext] Fw: New Version Notification for draft-regext-brown-epp-related-objects-00.txt CAUTION: This email came from outside your organization. Don’t trust emails, links, or attachments from senders that seem suspicious or you are not expecting. ________________________________ Hi all, Here is the first draft of an EPP extension designed to allow servers to include information about "related" objects in responses to <info> commands. >From the introduction: "The EPP <info> command allows clients to retrieve information (subject to authorisation) about objects in the repository. Since EPP operates on a strictly per-object basis, and since objects may be related to one another, a client may often need to issue multiple <info> commands in order to retrieve the data it needs to carry out its operation. This document describes an extension to the <info> command that allows clients to request the inclusion of information about related objects in responses. This allows clients to retrieve all the required information about an object in a single round-trip to the server." Feedback welcome! Regards, ________________________________ From: internet-dra...@ietf.org <internet-dra...@ietf.org> Sent: 27 March 2023 11:59 To: Gavin Brown <gavin.br...@centralnic.com> Subject: New Version Notification for draft-regext-brown-epp-related-objects-00.txt A new version of I-D, draft-regext-brown-epp-related-objects-00.txt has been successfully submitted by Gavin Brown and posted to the IETF repository. Name: draft-regext-brown-epp-related-objects Revision: 00 Title: Extensible Provisioning Protocol (EPP) Extension for Related Objects Document date: 2023-03-27 Group: Individual Submission Pages: 10 URL: https://www.ietf.org/archive/id/draft-regext-brown-epp-related-objects-00.txt<https://protect-us.mimecast.com/s/sdudCXD2y5HM5AXU6-4PX?domain=ietf.org> Status: https://datatracker.ietf.org/doc/draft-regext-brown-epp-related-objects/<https://protect-us.mimecast.com/s/8PTqCYENz5S61YLTGYXV8?domain=datatracker.ietf.org/> Htmlized: https://datatracker.ietf.org/doc/html/draft-regext-brown-epp-related-objects<https://protect-us.mimecast.com/s/iY-dCZ6NA0io4v5tKoblA?domain=datatracker.ietf.org> Abstract: This document describes an extension to the Extensible Provisioning Protocol (EPP) that allows EPP clients to request the inclusion of related objects in responses to <info> commands. The IETF Secretariat
_______________________________________________ regext mailing list regext@ietf.org https://www.ietf.org/mailman/listinfo/regext
