AD review: I note that the shepherd writeup's last question points out the creation of a registry using Specification Required rules, and thus doesn't need a designated expert, referencing RFC 8126 Section 4.6. However, that section of that RFC says:
This policy is the same as Expert Review, with the additional requirement of a formal public specification. In addition to the normal review of such a request, the designated expert will review the public specification and evaluate whether it is sufficiently stable and permanent, and sufficiently clear and technically sound to allow interoperable implementations. So yes, we do need to appoint designated expert(s) and this document needs to include any advice that they should have when reviewing specifications. Such advice is missing here. Do you want to add any? I also note from the writeup that you attempted to get OAUTH WG input but were not successful. I will raise this to the SEC ADs and ask them for advice as soon as I've sent this. For that matter, you might want to trigger an early SECDIR review, although there's going to be one as part of Last Call anyway. In Section 3.1.2, what is a "given period of interaction"? In Section 3.1.3, bullet 1, "OpenID OpenID Providers". In Section 3.1.3, bullet 1, why is that only a SHOULD? Why might I not do this? In Section 3.1.4, why is that only a SHOULD? Why might I not do this? In Section 3.1.4.1, same question. In Section 5.1.1, the entire object is OPTIONAL. This doesn't seem right. Would there be any practical use to such a thing? In Section 5.5, why is that SHOULD not a MUST? In Section 9.2, at least in the HTML version I looked at, the two registrations are run together. It would be helpful to readers to separate them somehow, at least with a blank line, though you could also make each a subsection. Thanks for including Section 10. -MSK, ART AD On Mon, Aug 7, 2023 at 6:36 AM James Galvin via Datatracker < nore...@ietf.org> wrote: > James Galvin has requested publication of draft-ietf-regext-rdap-openid-23 > as Proposed Standard on behalf of the REGEXT working group. > > Please verify the document's state at > https://datatracker.ietf.org/doc/draft-ietf-regext-rdap-openid/ > > >
_______________________________________________ regext mailing list regext@ietf.org https://www.ietf.org/mailman/listinfo/regext
