Re: [regext] [EXTERNAL] Re: jCard to JSContact transition

On Mon, Apr 3, 2023 at 3:18 PM Jasdip Singh wrote: > > Hi. > > > > If the response size increase is not a concern when both jCard and JSContact > objects are returned for some time, it seems Andy’s proposal (option 3) is > the way to go. IMO, it keeps things simple without having to worry about

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

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

Re: [regext] [EXTERNAL] Re: jCard to JSContact transition

Hi Jasdip, please find my comments below. Il 04/04/2023 00:18, Jasdip Singh ha scritto: Hi. If the response size increase is not a concern when both jCard and JSContact objects are returned for some time, it seems Andy’s proposal (option 3) is the way to go. IMO, it keeps things simple

Re: [regext] [Ext] Re: Redacting JSContact uid in RDAP - Updated

Hi Gustavo, thanks for you comment. For the sake of limiting the implications of rdap-jscontact on rdap-redacted, just checked on some web sites providing UUID generators that "nil UUID" and "empty UUID" are synonyms. Since rdap-redacted defines "redaction by Empty Value" (rather than

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,