Re: [regext] I-D Action: draft-ietf-regext-rdap-redacted-04.txt

"Gould, James" <jgould@verisign.com> Mon, 23 May 2022 12:25 UTC

Return-Path: <jgould@verisign.com>
X-Original-To: regext@ietfa.amsl.com
Delivered-To: regext@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EA635C157B48 for <regext@ietfa.amsl.com>; Mon, 23 May 2022 05:25:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.097
X-Spam-Level:
X-Spam-Status: No, score=-7.097 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_DNSWL_HI=-5, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=verisign.com
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HjV_uSk6rKYV for <regext@ietfa.amsl.com>; Mon, 23 May 2022 05:25:09 -0700 (PDT)
Received: from mail2.verisign.com (mail2.verisign.com [72.13.63.31]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E7CD6C157B37 for <regext@ietf.org>; Mon, 23 May 2022 05:25:08 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=verisign.com; l=2818; q=dns/txt; s=VRSN; t=1653308709; h=from:to:cc:subject:date:message-id:content-id: content-transfer-encoding:mime-version; bh=INJ5E3tfFtXc/jQ2snpj4xM9G/48PTMeGVtRgxBCMaU=; b=S9bDlc0jEbuXDqyd+lkMd10LnY5+UzVo5Hbpx91BHumjNpDaOMxgev2C 3Oe/3HzsqxBvyubu79d7u6kotlyxmEUW3njYyqOzGrtpsWNKIrkb0k0B1 LNrmrv9inp1MHlJ77v1O3jVda8ldamTG8VPK0W5yez5B9mcTIvEpOAtHi hm5cbPY7QnldR+deOhYO2GQQu0RaC38BtI5Ic4qT6uGvWD3dx0AXI5rrh h4uRhkv5Gdz6T9NryRpiLlISvO7x5tc9ywF9gvoSr6Kc7NNrQLk/Ane64 gXG9nPXygHfvbj/G+xoF6CoYssMiti8h4UeJ1w4G9BweLQWLkk+p2sYmE Q==;
IronPort-Data: A9a23:jXrau6xVGwwKoJSK1ll6t+dkxyrEfRIJ4+MujC+fZmUNrF6WrkUBm mBNWGDXa/2IMWb8fNglPo6w/E8Hu8XRnYNnT1Fu+C00HyNBpPSeCIXCJC8cHc8wwu7rFxs7s ppEOrEsCOhuExcwcz/0auCJQUGRUchkf5KkYAL+EnkZqTRMFWFw0HqPp8Zj2tQy2YXjWFvU0 T/Pi5a31GGNimYc3l08tvrrRCNH5JwebxtB4zTSzdgS1LPvvyF94KA3fMldHFOhKmVgJdNWc s6YpF2P1jiAo0pyUIPNfoHTKSXmSpaKVeSHoiQOB/j62nCurARqukowHKJ0hUu6F1xlNj2+o TlAncXYdOsnAkHDsMYYQgQDHwB0B6hf+6HNHHuFuMio90KTJhMAw902ZK03Faci3L9IJ0x+r aVeNjsKdAjFju7w3qigTK9ngcFLwMvDZdtZ4y47i2iEVrB6EfgvQI2TjTNc9DU/gd1KEd7Aa tAYcjtgalLLZBgn1lI/Uc5kw7z51yGXnztwsA63rO08xGfo8B1djpmuLcHQefrSbJAA9qqfj iecl4jjOTkGM9mf4TOd9HOnwOnCgUvTXYsIFbr+8vlkjkeeyms7CRwKE1C9u7+4liaWQd9QJ lwI0isjsaZ081akJuQRRDWyunjdoRgRS4IJVvYk8keIy7GR6QHfDHICF3hfcscg8sQxQFTGy 2O0oj8gPhQ32JX9dJ5X3u78Qe+aUcTNEVI/WA==
IronPort-HdrOrdr: A9a23:KiSxkKw/iXv98z3DmffAKrPw8b1zdoMgy1knxilNoHtuA6mlfq GV7ZYmPHDP6Ar5NEtPpTniAsa9qBrnnPZICOIqTNSftWfd2VeAHcVN4Yzv2DX8FyC73f4178 tdWpk7LNHrF1B1gYLZ7BnQKbwd6ejC1Kyzn+/RwzNWUAdwZ8hbgjtREAqBDUFsfgVACKc4EJ b03KF6mwY=
X-IronPort-AV: E=Sophos;i="5.91,246,1647302400"; d="scan'208";a="14273990"
Received: from BRN1WNEX01.vcorp.ad.vrsn.com (10.173.153.48) by BRN1WNEX01.vcorp.ad.vrsn.com (10.173.153.48) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.1.2375.24; Mon, 23 May 2022 08:25:07 -0400
Received: from BRN1WNEX01.vcorp.ad.vrsn.com ([10.173.153.48]) by BRN1WNEX01.vcorp.ad.vrsn.com ([10.173.153.48]) with mapi id 15.01.2375.024; Mon, 23 May 2022 08:25:07 -0400
From: "Gould, James" <jgould@verisign.com>
To: "tomh@apnic.net" <tomh@apnic.net>, "mario.loffredo@iit.cnr.it" <mario.loffredo@iit.cnr.it>
CC: "regext@ietf.org" <regext@ietf.org>
Thread-Topic: Re: [regext] I-D Action: draft-ietf-regext-rdap-redacted-04.txt
Thread-Index: AQHYbqAiMy4sgZY0206o8PDbLrdE8Q==
Date: Mon, 23 May 2022 12:25:06 +0000
Message-ID: <A41C59DD-A62D-4262-8E56-7641DC02D72F@verisign.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/16.59.22031300
x-originating-ip: [10.170.148.18]
Content-Type: text/plain; charset="utf-8"
Content-ID: <49198CB1A11E3949B47BCF71A9AD7031@verisign.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/regext/PfhrNpvRSmXGr1dzbEu5EDQ-4wY>
Subject: Re: [regext] I-D Action: draft-ietf-regext-rdap-redacted-04.txt
X-BeenThere: regext@ietf.org
X-Mailman-Version: 2.1.34
Precedence: list
List-Id: Registration Protocols Extensions <regext.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/regext>, <mailto:regext-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/regext/>
List-Post: <mailto:regext@ietf.org>
List-Help: <mailto:regext-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/regext>, <mailto:regext-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 23 May 2022 12:25:15 -0000

Tom,

Thank you for bringing this up, since I was overly focused on the Domain Name Registries (DNRs).   Will the Regional Internet Registries (RIRs) redact via draft-ietf-regext-rdap-redacted, and will the Redaction by Replacement Value Method be used?  

Signaling the replacement of a property is straight forward, with Figure 5 as an example.  The main complexity comes with replacing the property using a different property, with Figure 7 as an example.  Do you have the path reference the property that is being replaced (email), the property that is replacing (contact-uri), or do you reference both (email and contact-uri)?   Figure 7 references the property that is replacing (contact-uri), but a case could be made to point to the property that is being replaced.  In the end, I'm thinking that it may be better to add another optional path (replacementPath) for use of pointing to the property that is replacing (contact-uri) the redacted property (email). 

Thoughts?  

-- 
 
JG



James Gould
Fellow Engineer
jgould@Verisign.com <applewebdata://13890C55-AAE8-4BF3-A6CE-B4BA42740803/jgould@Verisign.com>

703-948-3271
12061 Bluemont Way
Reston, VA 20190

Verisign.com <http://verisigninc.com/>

On 5/19/22, 9:06 PM, "Tom Harrison" <tomh@apnic.net> wrote:


    Hi all,

    On Thu, May 19, 2022 at 03:57:41PM +0200, Mario Loffredo wrote:
    > I know that entities mapped to EPP contacts cannot support multiple
    > emails but such contacts match only a subset of the roles defined in
    > RDAP so, in theory, they don't cover all the cases.

    We have entities with multiple email addresses in our system.  For
    example:

        $ curl -s rdap.apnic.net/entity/IRT-01LINK-HK | jq '.vcardArray[1]'
        ...
        [
          "email",
          {},
          "text",
          "hostmaster@01link.net"
        ],
        [
          "email",
          {
            "pref": "1"
          },
          "text",
          "support@01link.net"
        ]
        $

    -Tom