Hi Andy,

please find my comments below.

Il 12/07/2023 15:35, Andrew Newton ha scritto:
Thanks for the review Pawel. My response is in-line:

On Wed, Jul 12, 2023 at 2:41 AM Pawel Kowalik<[email protected]>  wrote:
Hi Andy,

Thanks for putting down this draft. A method for the client to signal
supported or wanted extensions is really needed.

A remark to the Section 3: I think all cases should be covered by this
section. Currently I'm missing, the case when the server would support
more extensions than requested/understood by the client. I think it
would be good to make a recommendation for the server implementation
what is the desired behavior in such case. My suggestion is the server
SHOULD respond with no additional extensions as far as the server
capable of doing so (e.g. can render dynamic responses). It may be
relevant for the cases where the extensions define not only JSON
structures, which in general should not be an issue for the client
receiving an unsupported extension, but also define a response profile
which not necessarily have to be compatible with each other.
Yes, I think we should cover this scenario. Thanks for pointing it out.
And I agree with your suggested behavior.

[ML]

1) In addition to Pawel's feedback, it seems to me that, unless you leverage a REST plugin, you are unable to use this extension through a web browser.

Neither setting the "type" property in the links could be useful.

In particular, with regard to the farv1 extension, the REST plugin couldn't be used either because the user is redirected to the OP authentication form at login.

Therefore, IMO a text is needed to clarify that this extension is primarily intended for RDAP clients.


2) Does this document update RFC 9083 ?

RFC 9083 states that type is an OPTIONAL member of the link data structure while this document states that "application/rdap+json media type is RECOMMENDED when the URI references RDAP resources"



As an aside note of the considerations at point 1, would like to know the current WG's opinion about how relevant is making an RDAP server easily accessible by a web browser.

If I remember well, it has been vey relevant in the past. But this document goes in the opposite direction. Hence I'm not so sure it will keep on being relevant in the future.


Best,

Mario

[snip]

_______________________________________________
regext mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/regext

--
Dott. Mario Loffredo
Senior Technologist
Technological Unit “Digital Innovation”
Institute of Informatics and Telematics (IIT)
National Research Council (CNR)
via G. Moruzzi 1, I-56124 PISA, Italy
Phone: +39.0503153497
Web:http://www.iit.cnr.it/mario.loffredo

_______________________________________________
regext mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/regext

Reply via email to