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
