Hi,
I would opt to work on the option 2, at least to the point we can see
how much both types of clients have in common and how much do they go
split ways.
Based on this the WG could take more educated decision whether to break
it into 2 drafts or remain with one.
Kind Regards,
Pawel
Am 14.11.22 um 15:09 schrieb Hollenbeck, Scott:
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
regext@ietf.org
https://www.ietf.org/mailman/listinfo/regext
_______________________________________________
regext mailing list
regext@ietf.org
https://www.ietf.org/mailman/listinfo/regext
