HI Andy,
Il 31/03/2023 23:36, Andrew Newton ha scritto:
If the uid can be free text according to JSContact, why do we need to
override that? RDAP servers can just put random text in that field,
which has the same effect of the UUID URN.
That said, I like Gavin's idea. I could live with Option 4
If the uid can be free text according to JSContact, why do we need to
override that? RDAP servers can just put random text in that field,
which has the same effect of the UUID URN.
That said, I like Gavin's idea. I could live with Option 4 or Option 3.
-andy
On Fri, Mar 31, 2023 at 11:52 PM Mari
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 o
> 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 JSContact uid in RDAP - Updated
>>
>> Caution: This em
> -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. Do not click
> links
> or
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
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
12061
