Hi Scott,
Responses below.
Am 04.01.23 um 13:58 schrieb Hollenbeck, Scott:
- in the Section 3.1.3 the Sequence diagram for session-oriented client
should
also contain RDAP server <-> OP interactions to correspond to the sequence
diagram of token-oriented clients
[SAH] What exactly is missing
> -Original Message-
> From: Pawel Kowalik
> Sent: Tuesday, December 6, 2022 4:12 AM
> To: Hollenbeck, Scott ; regext@ietf.org
> Subject: [EXTERNAL] Re: [regext] I-D Action: draft-ietf-regext-rdap-openid-
> 19.txt
[SAH] I'm working on -20. I need a few more clar
Hi Scott,
Feedback below.
Am 06.12.22 um 15:23 schrieb Hollenbeck, Scott:
Thanks for the feedback. More below...
- we discussed that we do not care that much about remote OPs, however the
issue of access_token coming from an unknown OP remains. My proposal for a
simple solution would be just
Thanks for the feedback. More below...
> -Original Message-
> From: Pawel Kowalik
> Sent: Tuesday, December 6, 2022 4:12 AM
> To: Hollenbeck, Scott ; regext@ietf.org
> Subject: [EXTERNAL] Re: [regext] I-D Action: draft-ietf-regext-rdap-openid-
> 19.txt
>
> Cautio
Hi Scott,
Thanks for the progress on that.
I have the following remarks:
- 3.1.1 refers to "Access Token" in RFC9068 instead of RFC6749. I think
this might be misleading to exclude opaque access tokens just by
redefining it in the terminology. If the intention is to limit to "JWT
Access Tok
> -Original Message-
> From: regext On Behalf Of internet-dra...@ietf.org
> Sent: Friday, December 2, 2022 9:26 AM
> To: i-d-annou...@ietf.org
> Cc: regext@ietf.org
> Subject: [EXTERNAL] [regext] I-D Action: draft-ietf-regext-rdap-openid-19.txt
>
> Caution: This email originated from outsi
