> Le 14 nov. 2022 à 09:09, Hollenbeck, Scott > <shollenbeck=40verisign....@dmarc.ietf.org> a écrit : > > 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.
I would prefer option 2, as one single document will contain all different ways to use this technology. If we do 2 documents, we will need to partly repeat stuff and this is a slippery slope to be unsynched. Moreover, if we need to rev one of them, will the wg/editors/authors think of updating the second one? Finally, some platforms may be able to do both methods and the developer may choose appropriately if the developer has both in the same document. Marc. > > 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
