Scott and everyone in the WG, Speaking as co-Chair, Antoin and I meet earlier today to decide how to handle the WGLC for this document. We have decided to pull this back to the WG. I will be sending a separate note in the WGLC thread to explain this.
Short response is simply that this document, like far too many of REGEXT working group documents, did not get attention until it went to WGLC. This generated quite some discussion, which arguably should have happened before WGLC. Scott’s suggestion below about the two choices actually makes this painfully obvious. A technical concern has been raised as to the scope of clients that the specification should consider. The Chairs see this as a substantive technical question that deserves a full discussion in the working group. WGLC should be for stable documents and the Chairs are concerned this question suggests we are not as stable as we thought. WGLC is not the time to discuss and answer the question of scope of the document. It should happen within the ordinary work of the working group, not during what should be a time constrained WGLC. Separately I’ll be sending a message to close the WGLC. I encourage everyone to continue this discussion of the scope of clients on the list and, depending on how that goes, arrange to add appropriate text to this document or create a task to develop the separate document. Jim co-Chair On 14 Nov 2022, at 9:09, Hollenbeck, Scott wrote: > We need to decide what to do with draft-ietf-regext-rdap-openid and web > service clients. Our choices: > > 1. Finish the draft as-is, noting that it's limited to clients that can > implement OpenID Connect flows and can process session cookies. This implies > that we need another draft to describe OAuth-like token processing for clients > and servers that need that capability. > > 2. Add text to the draft that describes OAuth-like token processing for > clients and servers that need that capability. > > My preference is for the first option. > > Scott > > _______________________________________________ > regext mailing list > [email protected] > https://www.ietf.org/mailman/listinfo/regext _______________________________________________ regext mailing list [email protected] https://www.ietf.org/mailman/listinfo/regext
