With this message the Chairs are closing this WGLC.
Unfortunately, this document did not achieve consensus sufficient to advance to
being submitted to the IESG.
This document has gotten quite some discussion during WGLC. One item in
particular concerns the Chairs and that is the question of
Am 13.10.22 um 14:24 schrieb Hollenbeck, Scott
For the token revocation RFC 7009 can be used as-is, all we'd need to
specify would be the path segment like farv1_token_revocation and add
signalling if the RDAP server supports it or not in the /help
response.
[SAH] 7009 describes the interaction
> -Original Message-
> From: Pawel Kowalik
> Sent: Wednesday, October 12, 2022 3:35 PM
> To: Hollenbeck, Scott ; regext@ietf.org
> Subject: [EXTERNAL] Re: [regext] WGLC: draft-ietf-regext-rdap-openid-17 -
> Clients
>
> Caution: This email originated from outs
Am 12.10.22 um 19:07 schrieb Hollenbeck, Scott:
For the token revocation RFC 7009 can be used as-is, all we'd need to
specify
would be the path segment like farv1_token_revocation and add signalling if
the RDAP server supports it or not in the /help response.
[SAH] 7009 describes the
> -Original Message-
> From: Pawel Kowalik
> Sent: Wednesday, October 12, 2022 12:36 PM
> To: Hollenbeck, Scott ; regext@ietf.org
> Subject: [EXTERNAL] Re: [regext] WGLC: draft-ietf-regext-rdap-openid-17 -
> Clients
>
> Caution: This email originated from outs
Am 12.10.22 um 14:56 schrieb Hollenbeck, Scott:
[SAH] Since the draft already includes text that describes support for two
different types of clients, I'm OK with the idea of adding (or re-adding) text
that describes support for web service clients, too. The challenge is in
deciding how to
> -Original Message-
> From: regext On Behalf Of Pawel Kowalik
> Sent: Tuesday, October 11, 2022 11:42 AM
> To: regext@ietf.org
> Subject: [EXTERNAL] Re: [regext] WGLC: draft-ietf-regext-rdap-openid-17 -
> Clients
>
> Caution: This email originated from outs
On Tue, Oct 11, 2022 at 12:29:40PM +, Scott Hollenbeck wrote:
What should a logged-in end user see when they submit a standard
RDAP query, but their session has expired?
>>>
>>> [SAH] The query should be processed as if no
>>> identification/authentication information is available.
Hi Pavel,
please find me comments below.
Il 11/10/2022 17:42, Pawel Kowalik ha scritto:
Hi Mario,
Am 11.10.22 um 16:38 schrieb Mario Loffredo:
Il 11/10/2022 15:04, Andrew Newton ha scritto:
On Tue, Oct 11, 2022 at 8:16 AM Mario Loffredo
wrote:
my humble opinion is that this document
Hi Mario,
Am 11.10.22 um 16:38 schrieb Mario Loffredo:
Il 11/10/2022 15:04, Andrew Newton ha scritto:
On Tue, Oct 11, 2022 at 8:16 AM Mario Loffredo
wrote:
my humble opinion is that this document shouldn't deal with any kind
of RDAP client other than a browser.
Looking at the chapter 1 of
Il 11/10/2022 15:04, Andrew Newton ha scritto:
On Tue, Oct 11, 2022 at 8:16 AM Mario Loffredo
wrote:
my humble opinion is that this document shouldn't deal with any kind of RDAP
client other than a browser.
At the moment, I disagree with this. Authentication for non-browser
clients can be
> Le 11 oct. 2022 à 09:04, Andrew Newton a écrit :
>
> On Tue, Oct 11, 2022 at 8:16 AM Mario Loffredo
> wrote:
>>
>> my humble opinion is that this document shouldn't deal with any kind of RDAP
>> client other than a browser.
>
> At the moment, I disagree with this. Authentication for
On Tue, Oct 11, 2022 at 8:16 AM Mario Loffredo
wrote:
>
> my humble opinion is that this document shouldn't deal with any kind of RDAP
> client other than a browser.
At the moment, I disagree with this. Authentication for non-browser
clients can be very useful. GitHub's client is a great
> -Original Message-
> From: Tom Harrison
> Sent: Monday, October 10, 2022 7:16 PM
> To: Hollenbeck, Scott
> Cc: gal...@elistx.com; regext@ietf.org
> Subject: [EXTERNAL] Re: Re: [regext] WGLC: draft-ietf-regext-rdap-openid-17
>
> Caution: This email
/10/2022 15:47, Pawel Kowalik ha scritto:
Am 07.10.2022 um 14:49 schrieb Hollenbeck, Scott
:
*From:* regext *On Behalf Of *Pawel Kowalik
*Sent:* Thursday, October 6, 2022 7:24 PM
*To:* Andrew Newton
*Cc:* regext@ietf.org
*Subject:* [EXTERNAL] Re: [regext] WGLC: draft-ietf-regext-rdap
Hi Scott and Tom,
would like to add something to the points below.
Section 4.8 has:
If a client sends any request that includes an unknown HTTP
cookie, the server MUST return an HTTP 409 (Conflict) error.
What is an "unknown HTTP cookie"?
[SAH] It's a cookie that isn't associated
Hi Scott,
On Mon, Oct 10, 2022 at 06:39:30PM +, Scott Hollenbeck wrote:
>> In section 4.1.1, the "farv1_session" data structure has a member
>> called "clientID", defined as being "a string value that represents
>> the client identifier associated with the session". The example
>> indicates
Thanks for the feedback, Tom! More below...
> -Original Message-
> From: regext On Behalf Of Tom Harrison
> Sent: Monday, October 10, 2022 10:13 AM
> To: James Galvin
> Cc: REGEXT WG
> Subject: [EXTERNAL] Re: [regext] WGLC: draft-ietf-regext-rdap-openid-17
>
Hello Scott,
> 1.2: "It can also provide the ability to collect additional user
> identification
> information, and that information can be shared with the consent of the
> user."
> ... Not clear who that information could be shared with.
[SAH] "shared with the RDAP
On Mon, Sep 26, 2022 at 10:03:35PM +0800, James Galvin wrote:
> 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
>
Thanks for the feedback, Jasdip! More below...
> -Original Message-
> From: regext On Behalf Of Jasdip Singh
> Sent: Sunday, October 9, 2022 5:16 PM
> To: James Galvin ; regext@ietf.org
> Subject: [EXTERNAL] Re: [regext] WGLC: draft-ietf-regext-rdap-openid-17
>
>
Hi.
Overall, +1.
While reviewing the latest draft, wanted to share few comments (sorry, if a bit
late):
1.2: "willing to share more information about them self" ... Minor: wouldn't
"themselves" read better than "them self"?
1.2: "It can also provide the ability to collect additional user
Am 07.10.2022 um 14:49 schrieb Hollenbeck, Scott :
From: regext On Behalf Of
Pawel Kowalik
Sent: Thursday, October 6, 2022 7:24 PM
To: Andrew Newton
Cc: regext@ietf.org
Subject: [EXTERNAL] Re: [regext] WGLC: draft-ietf-regext-rdap-openid-17
Caution
From: regext On Behalf Of Pawel Kowalik
Sent: Thursday, October 6, 2022 7:24 PM
To: Andrew Newton
Cc: regext@ietf.org
Subject: [EXTERNAL] Re: [regext] WGLC: draft-ietf-regext-rdap-openid-17
Caution: This email originated from outside the organization. Do not click
links or open attachments
From: regext On Behalf Of Pawel Kowalik
Sent: Thursday, October 6, 2022 7:24 PM
To: Andrew Newton
Cc: regext@ietf.org
Subject: [EXTERNAL] Re: [regext] WGLC: draft-ietf-regext-rdap-openid-17
Caution: This email originated from outside the organization. Do not click
links or open attachments
Comment inline
On Thu, Oct 6, 2022 at 8:22 AM Pawel Kowalik wrote:
In my opinion the WG shall get the consensus around whether these web
application related use-cases shall be supported in order to move
forward with the WGLC.
Can you elaborate on what you mean by "web application"? Do you
On Thu, Oct 6, 2022 at 8:22 AM Pawel Kowalik wrote:
>
>
> In my opinion the WG shall get the consensus around whether these web
> application related use-cases shall be supported in order to move
> forward with the WGLC.
Can you elaborate on what you mean by "web application"? Do you mean
an
To: regext@ietf.org
Subject: [EXTERNAL] Re: [regext] WGLC: draft-ietf-regext-rdap-openid-17
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,
The discussion is ongoing but I will try to
Thursday, October 6, 2022 8:22 AM
> To: regext@ietf.org
> Subject: [EXTERNAL] Re: [regext] WGLC: draft-ietf-regext-rdap-openid-17
>
> Caution: This email originated from outside the organization. Do not click
> links
> or open attachments unless you recognize the sender and
.
Kind regards,
Pawel
Am 04.10.22 um 15:42 schrieb Hollenbeck, Scott:
-Original Message-
From: regext On Behalf Of James Galvin
Sent: Monday, October 3, 2022 8:40 AM
To: REGEXT WG
Subject: [EXTERNAL] Re: [regext] WGLC: draft-ietf-regext-rdap-openid-17
Caution: This email originated
Thanks for the feedback, Andy. More below...
> -Original Message-
> From: Andrew Newton
> Sent: Tuesday, October 4, 2022 10:37 AM
> To: REGEXT WG ; Hollenbeck, Scott
>
> Cc: James Galvin
> Subject: [EXTERNAL] Re: [regext] WGLC: draft-ietf-regext-rdap-openid-17
&g
Scott (and the WG),
My apologies for not taking the time to do a more read of this
document earlier. Overall, I believe it to be good. And I believe it
to cover the range of features I have seen discussed in the various
RDAP circles. Below you will find my comments.
Section 3.1.2 could benefit
> -Original Message-
> From: regext On Behalf Of James Galvin
> Sent: Monday, October 3, 2022 8:40 AM
> To: REGEXT WG
> Subject: [EXTERNAL] Re: [regext] WGLC: draft-ietf-regext-rdap-openid-17
>
> Caution: This email originated from outside the organization.
REMINDER:
This document is in WGLC and has only received support from its Editor and its
Document Shepherd.
To advance this document we need expressions of support from others to advance
this document to the IESG to be considered for publication as a Proposed
Standard.
WGLC remains open
+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
> -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.
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
37 matches
Mail list logo
