> -----Original Message----- > From: Hollenbeck, Scott > Sent: Thursday, October 5, 2023 8:58 AM > To: 'r...@cert.org' <r...@cert.org>; 'regext@ietf.org' <regext@ietf.org> > Cc: 'jric...@mit.edu' <jric...@mit.edu> > Subject: RE: [EXTERNAL] [regext] Feedback on draft-ietf-regext-rdap-openid > from OAuth WG
[SAH] [snip] > ยง5.2.4.2 > > - the device code is included here as a query parameter instead of a body > parameter, what's the purpose of that? As written it's incompatible with > RFC8628, which is claims to be a profile of (eg, "This request performs the > polling function described in...") > > [SAH] Yes, that needs to be fixed. [SAH] I took a closer look at this as part of making the updates needed to address IESG review feedback. The current text is actually correct as written. It doesn't describe the polling from Section 3.4 of RFC 8628, it's describing how the RDAP client tells the RDAP server to start polling. The RDAP server is then responsible for submitting the device access token request as described in 8628. I'll add text to make this clear. Scott _______________________________________________ regext mailing list regext@ietf.org https://www.ietf.org/mailman/listinfo/regext
