> -Original Message-
> From: regext On Behalf Of Hollenbeck, Scott
> Sent: Tuesday, February 8, 2022 1:58 PM
> To: regext@ietf.org
> Subject: [EXTERNAL] Re: [regext] I-D Action: draft-ietf-regext-rdap-openid-
> 10.txt
>
> Caution: This email originated from outside the organization. Do no
> -Original Message-
> From: regext On Behalf Of Hollenbeck, Scott
> Sent: Wednesday, February 9, 2022 8:35 AM
> To: regext@ietf.org
> Subject: [EXTERNAL] Re: [regext] I-D Action: draft-ietf-regext-rdap-openid-
> 10.txt
>
> Caution: This email originated from outside the organization. Do n
Scott,
Overall, I think that the modifications move the I-D in a good direction.
Thanks for your work on this.
I don’t have running code so this is more of a document review, rather than
comments from an implementer perspective.
Pls see the below.
3.1.2:
NIT: 3.1.2 #2 uses the term ‘ “logi
Thanks for the feedback, Rick! More below.
From: Rick Wilhelm
Sent: Wednesday, February 9, 2022 10:12 AM
To: Hollenbeck, Scott ; regext@ietf.org
Subject: [EXTERNAL] Re: [EXTERNAL] Re: [regext] I-D Action:
draft-ietf-regext-rdap-openid-10.txt
Caution: This email originated from outside th
Hi Scott,
a first feedback is about the "notice" object used in the examples.
It seems to me that the values of the "description" member are not
compliant with what is stated in section 4.3 of RFC 9083:
*an array of strings named "description" for the purposes of conveying
any descriptive te
From: regext On Behalf Of Mario Loffredo
Sent: Wednesday, February 9, 2022 1:07 PM
To: Hollenbeck, Scott ;
regext@ietf.org
Subject: [EXTERNAL] Re: [regext] I-D Action:
draft-ietf-regext-rdap-openid-10.txt
Caution: This email originated from outside the organization. Do not click
links or o
