[regext] Re: I-D Action: draft-ietf-regext-rdap-extensions-02.txt

"Andrew Newton (andy)" <andy@hxr.us> Thu, 22 August 2024 17:45 UTC

Return-Path: <andy@hxr.us>
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 9538AC19ECBA for <regext@ietfa.amsl.com>; Thu, 22 Aug 2024 10:45:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.908
X-Spam-Level:
X-Spam-Status: No, score=-1.908 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, SPF_HELO_NONE=0.001, SPF_NONE=0.001, T_SCC_BODY_TEXT_LINE=-0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=hxr-us.20230601.gappssmtp.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 cH98nmH3utVj for <regext@ietfa.amsl.com>; Thu, 22 Aug 2024 10:45:35 -0700 (PDT)
Received: from mail-qt1-x82d.google.com (mail-qt1-x82d.google.com [IPv6:2607:f8b0:4864:20::82d]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EA94FC151549 for <regext@ietf.org>; Thu, 22 Aug 2024 10:45:35 -0700 (PDT)
Received: by mail-qt1-x82d.google.com with SMTP id d75a77b69052e-44fe58fcf2bso6531231cf.2 for <regext@ietf.org>; Thu, 22 Aug 2024 10:45:35 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=hxr-us.20230601.gappssmtp.com; s=20230601; t=1724348735; x=1724953535; darn=ietf.org; h=content-transfer-encoding:in-reply-to:from:content-language :references:to:subject:user-agent:mime-version:date:message-id:from :to:cc:subject:date:message-id:reply-to; bh=+xUIZQZCLKlRMH7jFmo/Tqvwo8FiHKguUtYgPks8c/Q=; b=uTalslLaaUthlXmq84lY5Q5A7JUXmXPbTgKavaJw5V/JVjgHZbUFWeUoo8zRUCvqhF Ff6GbscSkV6Xd3zaVaRqG8wxlaMyXF//UmgwjUoWsml/rUwIxPiNsbE2Pun8uOFh6OyV byCXwNGV/92l6ep17U8S6BFKTCh19gAaojbayZ26Gb/tynfV2Qis2INJ5xPAuD3yll/f jXNZp3utWxBDzLHppBaBCmSDppiOPfCLpFJkyUM7b7n3/7aHmvMQO64C56du6ovoKlmY vOOF3UWSyWMVnxECEy9hLmmOqD2Z/BiFuThyIB3o0NnIv4l+xO/eiXhASpDkZePcgQZ2 d3Aw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1724348735; x=1724953535; h=content-transfer-encoding:in-reply-to:from:content-language :references:to:subject:user-agent:mime-version:date:message-id :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=+xUIZQZCLKlRMH7jFmo/Tqvwo8FiHKguUtYgPks8c/Q=; b=n9QJQKjX2XnY8/2ijq8/Rwasy4A52w59jkfWHg4xHT6dIxlSCuWAaLiq0Jrcp2TKtU zRS+HWvc7myV9qgm0uK+EUzkGPFYX7iyjm8lQtElqRxRR7FeZrZxlS+hJnnjloaqokzy ClAiWlJvgVrrLrkOxvx3/+WgNMU0JVd45U7cc9MOXo9eLH4KFHl8MxrhwRrpmJBoIas6 6RSad/ZDNvVyE2ZxqN2BJRj1bThCt44a6mfXMVDSfZ1q1LgsOV/HhfH9hP14f/3libeh dFu8LdGZ+/6hWUX38pVu2IHi0kYZAT7M1K0qp2KzY+35hPsycz05CW4NPKWjgYAAuC/2 1zuQ==
X-Forwarded-Encrypted: i=1; AJvYcCV34Qq/yuqkjYgmFOCAmsSSLGEWzSMAhGHkkJzehvdsr2AKB9XpnPLR1G5rPzCPJfHM5BE83p0=@ietf.org
X-Gm-Message-State: AOJu0YxGNBP7AwXF1xIX3YeqASmPOL+R6tkqiGgh5c40JQShJhX9oy3Z G04FReInYOtwJeG2TvHN2hXXreBzQoHH9NTeZISv5OE14PE9UZdnDzqNO4MdyH4k5GAJL8rqErh 9
X-Google-Smtp-Source: AGHT+IGuhJqrrgb9gNr+tYuoA8/azVu0x+A6PwboxH0r/5wQ/GNnepyK4BjYUGoQcdvdXalgQacHcQ==
X-Received: by 2002:a05:622a:5b86:b0:450:180:11f0 with SMTP id d75a77b69052e-454ff830590mr31754741cf.50.1724348734564; Thu, 22 Aug 2024 10:45:34 -0700 (PDT)
Received: from [10.2.8.160] (pool-72-83-25-32.washdc.fios.verizon.net. [72.83.25.32]) by smtp.gmail.com with ESMTPSA id d75a77b69052e-454fdfbfa58sm9091021cf.9.2024.08.22.10.45.33 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Thu, 22 Aug 2024 10:45:34 -0700 (PDT)
Message-ID: <7a574cd8-16a1-43fe-ad1e-fef03e9af068@hxr.us>
Date: Thu, 22 Aug 2024 13:45:33 -0400
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
To: "Gould, James" <jgould@verisign.com>, "regext@ietf.org" <regext@ietf.org>
References: <172415634166.2088655.15896242296287714306@dt-datatracker-6df4c9dcf5-t2x2k> <7f9c41fc-9582-4c08-9320-ad4d844079b1@hxr.us> <16F179E7-855A-45BA-A491-512960F5B464@verisign.com>
Content-Language: en-US
From: "Andrew Newton (andy)" <andy@hxr.us>
In-Reply-To: <16F179E7-855A-45BA-A491-512960F5B464@verisign.com>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 7bit
Message-ID-Hash: U43SRNC6PEC7FWDQ4QYLVEXBJRO26AAW
X-Message-ID-Hash: U43SRNC6PEC7FWDQ4QYLVEXBJRO26AAW
X-MailFrom: andy@hxr.us
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/-iXxSuEytKMq7w9QJLQTYZ1NlT4>
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>

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://github.com/anewton1998/draft-regext-rdap-extensions/issues/29

Thanks for the input.

-andy