Re: [regext] WGLC: draft-ietf-regext-rdap-reverse-search-20

The WGLC for this document is now closed. The chairs confirm this document has received enough support to be submitted to the IESG for publication as a Proposed Standard. Mario and Maurizio should publish a revision based on the comments received and then Tom Harrison, as the Document Shepherd

Re: [regext] WGLC: draft-ietf-regext-rdap-reverse-search-20

From: Mario Loffredo Date: Friday, April 7, 2023 at 1:28 PM To: Jasdip Singh , "Hollenbeck, Scott" , Andy Newton Cc: "regext@ietf.org" Subject: Re: [regext] WGLC: draft-ietf-regext-rdap-reverse-search-20 Il 07/04/2023 18:56, Jasdip Singh ha scritto: On 4/5/23, 12:56

Re: [regext] WGLC: draft-ietf-regext-rdap-reverse-search-20

Il 07/04/2023 18:56, Jasdip Singh ha scritto: On 4/5/23, 12:56 PM, "Mario Loffredo" mailto:mario.loffr...@iit.cnr.it>> wrote: [SAH] Nit: as alluded to by Jasdip above, RFC 7231 has been obsoleted by RFC 9110. The 501 text is 9110 is consistent with 7231, but I don’t think it’s limited to a

Re: [regext] WGLC: draft-ietf-regext-rdap-reverse-search-20

On 4/5/23, 12:56 PM, "Mario Loffredo" mailto:mario.loffr...@iit.cnr.it>> wrote: >> [SAH] Nit: as alluded to by Jasdip above, RFC 7231 has been >> obsoleted by RFC 9110. >> >> The 501 text is 9110 is consistent with 7231, but I don’t think >> it’s limited to an inval

Re: [regext] WGLC: draft-ietf-regext-rdap-reverse-search-20

Loffredo Sent: Wednesday, April 5, 2023 4:24 AM To: Andrew Newton ; Hollenbeck, Scott Cc: jasd...@arin.net; regext@ietf.org Subject: [EXTERNAL] Re: [regext] WGLC: draft-ietf-regext-rdap-reverse-search- 20 Caution: This email originated from outside the organization. Do not click links or open

Re: [regext] WGLC: draft-ietf-regext-rdap-reverse-search-20

Singh , Andy Newton *Cc: *"regext@ietf.org" *Subject: *Re: [regext] WGLC: draft-ietf-regext-rdap-reverse-search-20 Il 04/04/2023 17:37, Jasdip Singh ha scritto: On Mon, Apr 3, 2023 at 7:57 AM Jasdip Singh <mailto:jasd...@arin.net> wrote:

Re: [regext] WGLC: draft-ietf-regext-rdap-reverse-search-20

Hello Mario, I have attached my comment to Scott’s comment in the other thread. :) Thanks, Jasdip From: Mario Loffredo Date: Wednesday, April 5, 2023 at 4:07 AM To: Jasdip Singh , Andy Newton Cc: "regext@ietf.org" Subject: Re: [regext] WGLC: draft-ietf-regext-rdap-reverse-search-2

Re: [regext] WGLC: draft-ietf-regext-rdap-reverse-search-20

> -Original Message- > From: Mario Loffredo > Sent: Wednesday, April 5, 2023 10:04 AM > To: Hollenbeck, Scott ; a...@hxr.us > Cc: jasd...@arin.net; regext@ietf.org > Subject: [EXTERNAL] Re: [regext] WGLC: > draft-ietf-regext-rdap-reverse-search- > 20 > >

Re: [regext] WGLC: draft-ietf-regext-rdap-reverse-search-20

> -Original Message- > From: Jasdip Singh > Sent: Wednesday, April 5, 2023 10:40 AM > To: Hollenbeck, Scott ; mario.loffr...@iit.cnr.it; > a...@hxr.us > Cc: regext@ietf.org > Subject: [EXTERNAL] Re: [regext] WGLC: draft-ietf-regext-rdap-reverse-search- > 20

Re: [regext] WGLC: draft-ietf-regext-rdap-reverse-search-20

t;>; Hollenbeck, Scott > mailto:shollenb...@verisign.com>> > Cc: jasd...@arin.net <mailto:jasd...@arin.net>; regext@ietf.org > <mailto:regext@ietf.org> > Subject: [EXTERNAL] Re: [regext] WGLC: draft-ietf-regext-rdap-reverse-search- > 20 > > Caution: This email ori

Re: [regext] WGLC: draft-ietf-regext-rdap-reverse-search-20

Il 05/04/2023 14:40, Hollenbeck, Scott ha scritto: -Original Message- From: Mario Loffredo Sent: Wednesday, April 5, 2023 4:24 AM To: Andrew Newton ; Hollenbeck, Scott Cc: jasd...@arin.net; regext@ietf.org Subject: [EXTERNAL] Re: [regext] WGLC: draft-ietf-regext-rdap-reverse-search

Re: [regext] WGLC: draft-ietf-regext-rdap-reverse-search-20

> -Original Message- > From: Mario Loffredo > Sent: Wednesday, April 5, 2023 4:24 AM > To: Andrew Newton ; Hollenbeck, Scott > > Cc: jasd...@arin.net; regext@ietf.org > Subject: [EXTERNAL] Re: [regext] WGLC: draft-ietf-regext-rdap-reverse-search- > 20 > >

Re: [regext] WGLC: draft-ietf-regext-rdap-reverse-search-20

Hi Scott and Andy, Il 04/04/2023 18:33, Andrew Newton ha scritto: On Tue, Apr 4, 2023 at 9:20 AM Hollenbeck, Scott wrote: [SAH] Nit: as alluded to by Jasdip above, RFC 7231 has been obsoleted by RFC 9110. The 501 text is 9110 is consistent with 7231, but I don’t think it’s limited to an i

Re: [regext] WGLC: draft-ietf-regext-rdap-reverse-search-20

Il 04/04/2023 17:37, Jasdip Singh ha scritto: On Mon, Apr 3, 2023 at 7:57 AM Jasdip Singh wrote: What I gather from Andy’s suggestion is that 501 could also be returned for the reverse search queries that are not implemented (supported) on

Re: [regext] WGLC: draft-ietf-regext-rdap-reverse-search-20

On 4/4/23, 12:33 PM, "Andrew Newton" mailto:a...@hxr.us>> wrote: On Tue, Apr 4, 2023 at 9:20 AM Hollenbeck, Scott mailto:shollenb...@verisign.com>> wrote: > > [SAH] Nit: as alluded to by Jasdip above, RFC 7231 has been obsoleted by RFC > 9110. > > > > The 501 text is 9110 is consistent with 7231

Re: [regext] WGLC: draft-ietf-regext-rdap-reverse-search-20

On Tue, Apr 4, 2023 at 9:20 AM Hollenbeck, Scott wrote: > > [SAH] Nit: as alluded to by Jasdip above, RFC 7231 has been obsoleted by RFC > 9110. > > > > The 501 text is 9110 is consistent with 7231, but I don’t think it’s limited > to an invalid method. If the operative text is “the server does

Re: [regext] WGLC: draft-ietf-regext-rdap-reverse-search-20

From: regext On Behalf Of Jasdip Singh Sent: Tuesday, April 4, 2023 11:38 AM To: Mario Loffredo ; Andrew Newton Cc: regext@ietf.org Subject: [EXTERNAL] Re: [regext] WGLC: draft-ietf-regext-rdap-reverse-search-20 Caution: This email originated from outside the organization. Do not click links

Re: [regext] WGLC: draft-ietf-regext-rdap-reverse-search-20

From: regext On Behalf Of Jasdip Singh Sent: Tuesday, April 4, 2023 11:38 AM To: Mario Loffredo ; Andrew Newton Cc: regext@ietf.org Subject: [EXTERNAL] Re: [regext] WGLC: draft-ietf-regext-rdap-reverse-search-20 Caution: This email originated from outside the organization. Do not click

Re: [regext] WGLC: draft-ietf-regext-rdap-reverse-search-20

On Mon, Apr 3, 2023 at 7:57 AM Jasdip Singh wrote: What I gather from Andy’s suggestion is that 501 could also be returned for the reverse search queries that are not implemented (supported) on the server side. That said, your observation of applying HTTP 501 to un

Re: [regext] WGLC: draft-ietf-regext-rdap-reverse-search-20

Hi Andy and Jasdip, Il 03/04/2023 22:30, Andrew Newton ha scritto: On Mon, Apr 3, 2023 at 7:57 AM Jasdip Singh wrote: What I gather from Andy’s suggestion is that 501 could also be returned for the reverse search queries that are not implemented (supported) on the server side. That said, you

Re: [regext] WGLC: draft-ietf-regext-rdap-reverse-search-20

On Mon, Apr 3, 2023 at 7:57 AM Jasdip Singh wrote: > > What I gather from Andy’s suggestion is that 501 could also be returned for > the reverse search queries that are not implemented (supported) on the server > side. > > That said, your observation of applying HTTP 501 to unsupported request

Re: [regext] WGLC: draft-ietf-regext-rdap-reverse-search-20

Hello Mario, Please find my comment below. Thanks, Jasdip From: Mario Loffredo Date: Monday, April 3, 2023 at 6:18 AM To: Jasdip Singh , Andy Newton , "regext@ietf.org" Subject: Re: [regext] WGLC: draft-ietf-regext-rdap-reverse-search-20 Hi Jasdip, Il 01/04/2023 23:55, Jasdi

Re: [regext] WGLC: draft-ietf-regext-rdap-reverse-search-20

Hi Jasdip, Il 01/04/2023 23:55, Jasdip Singh ha scritto: On 3/22/23, 5:44 PM, "regext on behalf of Andrew Newton" mailto:regext-boun...@ietf.org> on behalf ofa...@hxr.us > wrote: Ok. I did find one small issue. Should the draft give explicit mention of returning an HTTP 50

Re: [regext] WGLC: draft-ietf-regext-rdap-reverse-search-20

On 3/22/23, 5:44 PM, "regext on behalf of Andrew Newton" mailto:regext-boun...@ietf.org> on behalf of a...@hxr.us > wrote: Ok. I did find one small issue. Should the draft give explicit mention of returning an HTTP 501 for searches not supported by a server? [JS] Section 1 o

Re: [regext] WGLC: draft-ietf-regext-rdap-reverse-search-20

Hi I have no objections to this document being published. tim On Thu, Mar 23, 2023 at 3:17 AM Mario Loffredo wrote: > Hi Andy, > > Il 22/03/2023 22:37, Andrew Newton ha scritto: > > I have read the draft again and support it. > > > > That said, is there a plan to add this equivalent from this

Re: [regext] WGLC: draft-ietf-regext-rdap-reverse-search-20

Hi Andy, Il 22/03/2023 22:37, Andrew Newton ha scritto: I have read the draft again and support it. That said, is there a plan to add this equivalent from this draft to JSContact? Reverse search property: fn RDAP member path: $..entities[*].vcardArray[1][?(@[0]=='fn')][3] Referen

Re: [regext] WGLC: draft-ietf-regext-rdap-reverse-search-20

On Wed, Mar 22, 2023 at 2:37 PM Andrew Newton wrote: > > I have read the draft again and support it. > > That said, is there a plan to add this equivalent from this draft to > JSContact? > >Reverse search property: fn >RDAP member path: $..entities[*].vcardArray[1][?(@[0]=='fn')][3] >

Re: [regext] WGLC: draft-ietf-regext-rdap-reverse-search-20

I have read the draft again and support it. That said, is there a plan to add this equivalent from this draft to JSContact? Reverse search property: fn RDAP member path: $..entities[*].vcardArray[1][?(@[0]=='fn')][3] Reference: Section 6.2.1 of [RFC6350] -andy On Tue, Mar 21, 2023 a

Re: [regext] WGLC: draft-ietf-regext-rdap-reverse-search-20

> -Original Message- > From: regext On Behalf Of James Galvin > Sent: Monday, March 20, 2023 9:41 AM > To: REGEXT WG > Subject: [EXTERNAL] [regext] WGLC: draft-ietf-regext-rdap-reverse-search-20 > > Caution: This email originated from outside the organization. Do not click > links > or o

Re: [regext] WGLC: draft-ietf-regext-rdap-reverse-search-20

+1 Am 20.03.23 um 14:40 schrieb James Galvin: 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: Registration Data Access Protocol (RDAP) Reverse Search https://datatracker.ietf.org/doc/d

Re: [regext] WGLC: draft-ietf-regext-rdap-reverse-search-20

+1 Jasdip On 3/20/23, 9:41 AM, "regext on behalf of James Galvin" mailto:regext-boun...@ietf.org> on behalf of gal...@elistx.com > wrote: The document editors have indicated that the following document is ready for submission to the IESG to be considered for publica