> -----Original Message----- > From: regext <[email protected]> On Behalf Of Pawel Kowalik > Sent: Monday, November 14, 2022 12:18 PM > To: [email protected] > Subject: [EXTERNAL] Re: [regext] draft-ietf-regext-rdap-openid Post IETF-115 > > Caution: This email originated from outside the organization. Do not click > links > or open attachments unless you recognize the sender and know the content is > safe. > > 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.
[SAH] Based on the testing you and I've been doing, we already know that web service clients require token processing features that aren't currently specified. That's fixable; earlier versions of the draft included text that was demonstrated to work. However, we also know that login processing will be a problem if the client-side application can't process third-party cookies. That might be more difficult to overcome. What do you have in mind? Scott _______________________________________________ regext mailing list [email protected] https://www.ietf.org/mailman/listinfo/regext
