[regext] Re: I-D Action: draft-ietf-regext-rdap-extensions-02.txt
"Gould, James" <jgould@verisign.com> Fri, 23 August 2024 14:00 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 CAE50C14CE42 for <regext@ietfa.amsl.com>; Fri, 23 Aug 2024 07:00:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.407
X-Spam-Level:
X-Spam-Status: No, score=-4.407 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_MED=-2.3, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, 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 9f_9Ctt1m8oA for <regext@ietfa.amsl.com>; Fri, 23 Aug 2024 07:00:52 -0700 (PDT)
Received: from mail3.verisign.com (mail3.verisign.com [72.13.63.32]) by ietfa.amsl.com (Postfix) with ESMTP id 194A5C14F71C for <regext@ietf.org>; Fri, 23 Aug 2024 07:00:51 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=verisign.com; l=5818; q=dns/txt; s=VRSN; t=1724421652; h=from:to:date:message-id:references:in-reply-to: content-id:content-transfer-encoding:mime-version:subject; bh=o7qjDuXoOtFji3FNhv1JqI1X1/DU5quQssapHUUcsmg=; b=m8k5nIdX1S1V668GVYKj0NycESeUWV4D3KVRKcmkrJ2RgTC0z2cT4kpJ R1cyao7sF6c/nnE1mO6WtaPljyrw4yUGM0zdSydb2pTF9yAiNzv2/PHtP TlmI7D1cp5J5nKszmVNrkZqh1Gc4VS6CvXJGc00Qk620EW7rd9rWTZ5I6 f6rScTwrALx1fdck3DiVHIvdQq8vSBkpqtYG+t481aMGLxhT/u+fuCYmY wllBb9MxxNmXOjAaAFFLpmsejTsocnGpwIp+uEHlyzg4pc40TiFaOl6pt eYbyskodIWHmB2JDdYdBh2JD4cXh0FMhQtFQR0PlZb0hlksCQy5GLMDtD g==;
X-CSE-ConnectionGUID: swG6FMlaQDaaVb4OQVCDLg==
X-CSE-MsgGUID: SyQs+70zR7+GKf7HEpi2Bg==
X-ThreatScanner-Verdict: Negative
IronPort-Data: A9a23:ZFq/CKxNC4JaBANc6Pd6t+dExyrEfRIJ4+MujC+fZmUNrF6WrkVWm GobWmGDMv7bMGSjfo9waorkox8C7JKDzIcxTlRo+S00HyNBpPSeCIXCJC8cHc8wwu7rFxs7s ppEOrEsCOhuExcwcz/0auCJQUFUjPzOG/ylTraZZ0idfCc8IA85kxVvhuUltYBhhNm9Emult Mj7yyHlEAbNNwVcbCRNs8pvlDs15K6u4GNC5QRkDRx2lAS2e0c9Xcp3yZ6ZciOQrrl8RoaSW +vFxbelyWLVlz9FIs+liLvybnoRSbfUOwWU4lIOM0R1qkEfzsCa+v9T2Ms0MS+7uR3Q9zxC4 IwlWaiLdOscFvakdNI1CEAETn4kbcWqz5ecSZS3mZT7I0TuLSOwk602ZK08FdVwFu1fWQmi+ RGEQdykg9/qa++emdqGpudQassLN9bEYq06vnhZ4TjQM/x6Zqn9aInu6ooNtNswrpgm8ff2T fA/MAVJQSSYOVtRMVANENQ3kKG2nGL5NTZfrTp5p4Juuy6Kk1c3ieW2doaEEjCJbZw9ckKwp G3B4mD1Kg8XLt2EyDWDtHmrg4cjmAugBdxDT+Dmq5aGhnWo11UIS0JOR2Hk4taahBGedspec WYbr39GQa8asRbDosPGdxS+rG+svg4GHcdLe8Ug5Q6A2rb84guFCC4DVDEpVTA9nMUsQ2U10 FKZx4msHiJ19riUUjeX8fGetzXrfzYPNmlEbigBJecY3+TeTEgIpkqnZr5e/GSd1LUZxRmYL +i2kRUD
IronPort-HdrOrdr: A9a23:IUa/z6kyqXypzQA4uO/MuJov1ovpDfL13DAbv31ZSRFFG/Fwz/ re+cjyTXfP+UwssQIb6LS90c67MA7hHP9OkPIs1NiZPTUO1FHDEGgm1/qB/9SCIVyDygc+78 ddmsFFYbWaMbE5t7eY3ODSKbodKay8npxA8t2w854Cd2xXgupbnmBE406gYytLrEMtP+tBKH Oz3Ls+mwad
X-Talos-CUID: 9a23:o3U3XGrBYhKMC2z5WaoyLGPmUds6XSPz6XPZGmOxAFhjFJqsd3S83Kwxxg==
X-Talos-MUID: 9a23:fab66Q97JLluw7x4rO/fO7OQf/x52r/tVxgfq8pFlOqKagxdIzbHpjviFw==
X-IronPort-AV: E=Sophos;i="6.10,170,1719878400"; d="scan'208";a="35693565"
Received: from BRN1WNEX01.vcorp.ad.vrsn.com (10.173.153.48) by BRN1WNEX02.vcorp.ad.vrsn.com (10.173.153.49) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.1.2507.37; Fri, 23 Aug 2024 10:00:50 -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.2507.037; Fri, 23 Aug 2024 10:00:50 -0400
From: "Gould, James" <jgould@verisign.com>
To: "andy@hxr.us" <andy@hxr.us>, "regext@ietf.org" <regext@ietf.org>
Thread-Topic: [EXTERNAL] Re: [regext] Re: I-D Action: draft-ietf-regext-rdap-extensions-02.txt
Thread-Index: AQHa9LsY21zW75RhSUmnKsWGOpqz9bI04EIA
Date: Fri, 23 Aug 2024 14:00:50 +0000
Message-ID: <B0B74EBF-6A29-4529-BE5B-EBB70B64B815@verisign.com>
References: <172415634166.2088655.15896242296287714306@dt-datatracker-6df4c9dcf5-t2x2k> <7f9c41fc-9582-4c08-9320-ad4d844079b1@hxr.us> <16F179E7-855A-45BA-A491-512960F5B464@verisign.com> <7a574cd8-16a1-43fe-ad1e-fef03e9af068@hxr.us>
In-Reply-To: <7a574cd8-16a1-43fe-ad1e-fef03e9af068@hxr.us>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/16.82.24021116
x-originating-ip: [10.170.148.18]
Content-Type: text/plain; charset="utf-8"
Content-ID: <128147D608DE61418E3BA1EB97350437@verisign.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Message-ID-Hash: EKTSRP6IFTUMYDTZCDSKUGPMH23EFFPW
X-Message-ID-Hash: EKTSRP6IFTUMYDTZCDSKUGPMH23EFFPW
X-MailFrom: jgould@verisign.com
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-regext.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
X-Mailman-Version: 3.3.9rc4
Precedence: list
Subject: [regext] Re: I-D Action: draft-ietf-regext-rdap-extensions-02.txt
List-Id: Registration Protocols Extensions Working Group <regext.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/regext/t9nYd-LqACvAuCYkB9zuV8UJowM>
List-Archive: <https://mailarchive.ietf.org/arch/browse/regext>
List-Help: <mailto:regext-request@ietf.org?subject=help>
List-Owner: <mailto:regext-owner@ietf.org>
List-Post: <mailto:regext@ietf.org>
List-Subscribe: <mailto:regext-join@ietf.org>
List-Unsubscribe: <mailto:regext-leave@ietf.org>
Andy, It may be useful to include guidance for RDAP extensions use of the RDAP JSON Values registry in the extensions draft. I believe that new RDAP extensions should be encouraged to support standard values to increase interoperability, where extending the RDAP JSON Values registry is better than creating a new registry specific to the RDAP extension and certainly better than not leveraging the RDAP JSON Values registry at all. The Redacted Extension did this to define three new types with "redacted name", "redacted reason", and "redacted expression language", and the language used in the first paragraph of section 6.2 supported the extension of the types. We could look to have any new types define the expected format of the values to help support the review by the DEs, where some types may be more freeform than others (e.g., support mixed case). For example, the "redacted name" values did use mixed case to match the source policy and I believe the "redacted reason" values would be in more sentence form with mixed case and potentially punctuation. The "redacted expression language" is more of an identifier, so it could be predefined as being only lowercase. The Versioning Extension has a similar extension of the RDAP JSON Values registry types with the "versioning" type and registration of the values of "opaque" and "semantic". I view the "versioning" type as more of an identifier, where being lowercase makes sense. The extensions draft could clarify the expected value format for the predefined types in the RDAP RFCs and provide the guidance for how to define new types with the expected value format for future RDAP extensions. -- 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 8/22/24, 1:45 PM, "Andrew Newton (andy)" <andy@hxr.us <mailto:andy@hxr.us>> wrote: Caution: This email originated from outside the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe. On 8/20/24 09:15, Gould, James wrote: > Andy, > > In reviewing the updates to draft-ietf-regext-rdap-extensions, I believe that we need to reconsider the criteria for the RDAP JSON Registry values. Based on the types initially defined, the use of lowercase only values may make sense, but for the recently registered values from the RDAP Profile for redaction includes mixed case to exactly match the values in the source policy. The use of lowercase is a non-normative "should", so would future registration requests that have justification for mixed case run into an issue and be considered a violation of the criteria? Should we consider updating the criteria in RFC 9083 based on the implementation experience of the recent registrations or provide additional clarity in draft-ietf-regext-rdap-extensions? > > Thanks, > James, Those are all good points, and I am unaware of any impact on implementations from the mixed case registrations. I think the need to match text from another document is a good use case and overrides any desired "style". I'll change this section in a PR and pass the link when it is up. Until then I have created this tracking issue. https://secure-web.cisco.com/1Zq4w5NqHzo9F6L15R_wLRX0WkvUHoF83pLe4eWxLEsuO64JE79TRPYRH_UVeXEIKpwpR2yn4hvDLf1buT0qfqe_q5IQDcS-9zC7ZVyEfeaY0S2v3JmS7PybtvJOIknRiwar9KLvORxRAOaYPPl_YcJuGjWZtHlOx0hIkaH7aSxR7NbpZvrCvrkCCGBrrHxqNI9Zc6ZNi_qxjpyXEZZr8mFj701Blsl0rXX0_Sandxg8W87sagRZS34NwkbSxkMaR0Uk3dImFBAXes5vD-rZVCn7taRB16m4OGFVX5WuOP-4/https%3A%2F%2Fgithub.com%2Fanewton1998%2Fdraft-regext-rdap-extensions%2Fissues%2F29 <https://secure-web.cisco.com/1Zq4w5NqHzo9F6L15R_wLRX0WkvUHoF83pLe4eWxLEsuO64JE79TRPYRH_UVeXEIKpwpR2yn4hvDLf1buT0qfqe_q5IQDcS-9zC7ZVyEfeaY0S2v3JmS7PybtvJOIknRiwar9KLvORxRAOaYPPl_YcJuGjWZtHlOx0hIkaH7aSxR7NbpZvrCvrkCCGBrrHxqNI9Zc6ZNi_qxjpyXEZZr8mFj701Blsl0rXX0_Sandxg8W87sagRZS34NwkbSxkMaR0Uk3dImFBAXes5vD-rZVCn7taRB16m4OGFVX5WuOP-4/https%3A%2F%2Fgithub.com%2Fanewton1998%2Fdraft-regext-rdap-extensions%2Fissues%2F29> Thanks for the input. -andy
- [regext] I-D Action: draft-ietf-regext-rdap-exten… internet-drafts
- [regext] Re: I-D Action: draft-ietf-regext-rdap-e… Andrew Newton (andy)
- [regext] Re: I-D Action: draft-ietf-regext-rdap-e… Gould, James
- [regext] Re: I-D Action: draft-ietf-regext-rdap-e… Andrew Newton (andy)
- [regext] Re: I-D Action: draft-ietf-regext-rdap-e… Andrew Newton (andy)
- [regext] Re: I-D Action: draft-ietf-regext-rdap-e… Gould, James
- [regext] Re: I-D Action: draft-ietf-regext-rdap-e… Hollenbeck, Scott
- [regext] Re: I-D Action: draft-ietf-regext-rdap-e… Andrew Newton (andy)
- [regext] Re: I-D Action: draft-ietf-regext-rdap-e… Gould, James
- [regext] Re: I-D Action: draft-ietf-regext-rdap-e… Andrew Newton (andy)