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

2023-04-03 Thread Mario Loffredo
Scott, Il 31/03/2023 14:32, Hollenbeck, Scott ha scritto: -Original Message- From: regext On Behalf Of Mario Loffredo Sent: Friday, March 31, 2023 7:45 AM To:regext@ietf.org Subject: [EXTERNAL] [regext] Redacting JSContact uid in RDAP - Updated Caution: This email originated from

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

2023-03-31 Thread Andrew Newton
Mario Loffredo wrote: > > Hi Scott, > > Il 31/03/2023 14:32, Hollenbeck, Scott ha scritto: > >> -Original Message- > >> From: regext On Behalf Of Mario Loffredo > >> Sent: Friday, March 31, 2023 7:45 AM > >> To: regext@ietf.org > >> Sub

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

2023-03-31 Thread Mario Loffredo
Hi Scott, Il 31/03/2023 14:32, Hollenbeck, Scott ha scritto: -Original Message- From: regext On Behalf Of Mario Loffredo Sent: Friday, March 31, 2023 7:45 AM To: regext@ietf.org Subject: [EXTERNAL] [regext] Redacting JSContact uid in RDAP - Updated Caution: This email originated from

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

2023-03-31 Thread Marc Blanchet
> Le 31 mars 2023 à 08:32, Hollenbeck, Scott > a écrit : > >> -Original Message- >> From: regext On Behalf Of Mario Loffredo >> Sent: Friday, March 31, 2023 7:45 AM >> To: regext@ietf.org >> Subject: [EXTERNAL] [regext] Redacting JSConta

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

2023-03-31 Thread Hollenbeck, Scott
> -Original Message- > From: regext On Behalf Of Mario Loffredo > Sent: Friday, March 31, 2023 7:45 AM > To: regext@ietf.org > Subject: [EXTERNAL] [regext] Redacting JSContact uid in RDAP - Updated > > Caution: This email originated from outside the organization.

[regext] Redacting JSContact uid in RDAP - Updated

2023-03-31 Thread Mario Loffredo
Hi folks, just reported below all the options (including Gavin's proposal) and the preferences given thus far. Please, express your preference(s). Thanks a lot in advance. 1) Redacting by Empty Value method 2) Making uid optional in RDAP and then redacting by Removal method - J.Gould 3)

Re: [regext] Redacting JSContact uid in RDAP

2023-03-31 Thread Gavin Brown
Ciao Mario, Can I propose an alternative? Since (IIRC) a UID can be a URN, and IANA maintains its own URN namespace, could we register a URN that would be used to redact the UID? Something like "urn:ietf:params:json:rdap+jscontact:uidRedacted"? Servers could publish this value in the UID of a

Re: [regext] Redacting JSContact uid in RDAP

2023-03-30 Thread Gould, James
Mario, Thank you for posting the options to the list. I'll mirror the preference that I stated at the REGEXT meeting, which is option 2 "Making uid optional in RDAP and then redacting by Removal method". Thanks, -- JG James Gould Fellow Engineer jgo...@verisign.com 703-948-3271

[regext] Redacting JSContact uid in RDAP

2023-03-30 Thread Mario Loffredo
Hi folks, this is a post to resume the discussion about how to redact JSContact uid in RDAP. The goal is to reach consensus or majority on one of the following solutuions: 1) Redacting by Empty Value method 2) Making uid optional in RDAP and then redacting by Removal method 3) Recommending