+1
On 9/26/22, 7:03 AM, "regext on behalf of James Galvin"
wrote:
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.
The document editors have indicated that the followin
> -Original Message-
> From: regext On Behalf Of James Galvin
> Sent: Monday, September 26, 2022 10:04 AM
> To: REGEXT WG
> Subject: [EXTERNAL] [regext] WGLC: draft-ietf-regext-rdap-openid-17
>
> Caution: This email originated from outside the organization. Do not click
> links
> or open
The document editors have indicated that the following document is ready for
submission to the IESG to be considered for publication as a Proposed Standard:
Federated Authentication for the Registration Data Access Protocol (RDAP) using
OpenID Connect
https://datatracker.ietf.org/doc/draft-ietf-
Given the discussion below, we are considering to extend this WGLC for at most
1 week until this discussion is settled.
When there are any other objections, or expressions of support, this WGLC would
have ended today with enough support for consensus.
So please let's try to settle this issue befo
Very sorry to be late with my reply, and for not replying to the latest
posting from John Klensin in this thread.
On 2022-09-14 04:03, John C Klensin wrote:
James,
My apologies for not having responded to your note sooner.
I've been preoccupied with several unrelated things.
I greatly appreci
Gavin,
Just a +1 for having this extension cover both the domain and host objects.
The sibling glue model has enough deployment that having the extension cover
both models makes sense.
One other thing… and this is not a call for a change, just concurrence to an
existing design choice that is
Hi Patrick,
thanks for your review.
Please find my comments inline.
Il 25/09/2022 18:21, Patrick Mevzek ha scritto:
On Mon, Sep 12, 2022, at 08:54, Antoin Verschuren wrote:
Please review this document and indicate your support (a simple “+1” is
sufficient) or concerns with the publication of
