Re: [dnsext] Draft: RRTYPE B - Web Resource Integrity

Klaus Malorny <Klaus.Malorny@knipp.de> Thu, 16 November 2023 08:33 UTC

Return-Path: <Klaus.Malorny@knipp.de>
X-Original-To: dnsext@ietfa.amsl.com
Delivered-To: dnsext@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 58A0DC151061 for <dnsext@ietfa.amsl.com>; Thu, 16 Nov 2023 00:33:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.909
X-Spam-Level:
X-Spam-Status: No, score=-1.909 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01] autolearn=ham autolearn_force=no
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 DHQcPNSsw7av for <dnsext@ietfa.amsl.com>; Thu, 16 Nov 2023 00:33:12 -0800 (PST)
Received: from kmx5a.knipp.de (kmx5a.knipp.de [195.253.6.99]) (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 0B71AC14CF01 for <dnsext@ietf.org>; Thu, 16 Nov 2023 00:33:10 -0800 (PST)
Received: from hp9000.do.knipp.de (hp9000.do.knipp.de [IPv6:2a01:5b0:0:25::36]) by kmx5a.knipp.de (Postfix) with ESMTP id 4SWCwN2RLsz4vBy; Thu, 16 Nov 2023 09:33:08 +0100 (CET)
Authentication-Results: kmx5a.knipp.de; dkim=none; spf=softfail (kmx5a.knipp.de: 2a01:5b0:0:25::36 is neither permitted nor denied by domain of Klaus.Malorny@knipp.de) smtp.mailfrom=Klaus.Malorny@knipp.de; dmarc=none
Received: from [IPV6:2a01:5b0:0:25::1b] (unknown [IPv6:2a01:5b0:0:25::1b]) by hp9000.do.knipp.de (Postfix) with ESMTP id 1736271985; Thu, 16 Nov 2023 09:33:07 +0100 (MEZ)
Message-ID: <f658adcb-c65f-4577-b6c1-a6d299592c03@knipp.de>
Date: Thu, 16 Nov 2023 09:33:01 +0100
MIME-Version: 1.0
User-Agent: Thunderbird Daily
Content-Language: en-US
To: dnsext@ietf.org
References: <CAF3AkiPt98c5By3M1qY=31qW4ESV9_TF7bzH+wdqz2iqzBB+6w@mail.gmail.com>
From: Klaus Malorny <Klaus.Malorny@knipp.de>
In-Reply-To: <CAF3AkiPt98c5By3M1qY=31qW4ESV9_TF7bzH+wdqz2iqzBB+6w@mail.gmail.com>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Rspamd-Queue-Id: 4SWCwN2RLsz4vBy
X-Spamd-Bar: /
X-Rspamd-Pre-Result: action=no action; module=multimap; Matched map: LOCAL_WL_IP
X-Spamd-Result: default: False [-0.09 / 15.00]; MIME_GOOD(-0.10)[text/plain]; XM_UA_NO_VERSION(0.01)[]; ASN(0.00)[asn:8391, ipnet:2a01:5b0::/32, country:DE]; MIME_TRACE(0.00)[0:+]; R_SPF_SOFTFAIL(0.00)[~all:c]; R_DKIM_NA(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; LOCAL_WL_IP(0.00)[2a01:5b0:0:25::36]; FROM_HAS_DN(0.00)[]; DMARC_NA(0.00)[knipp.de]
X-Rspamd-Action: no action
X-Rspamd-Server: v1117
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsext/t-aRUSGz6LdboO8kF_fAwg1p5hM>
Subject: Re: [dnsext] Draft: RRTYPE B - Web Resource Integrity
X-BeenThere: dnsext@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: DNS Extensions working group discussion list <dnsext.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsext>, <mailto:dnsext-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsext/>
List-Post: <mailto:dnsext@ietf.org>
List-Help: <mailto:dnsext-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsext>, <mailto:dnsext-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 16 Nov 2023 08:33:16 -0000

On 14.11.23 18:36, James Addison wrote:
> A. Submission Date: N/A (draft / RFC)
> 
> B.1 Submission Type:  [x] New RRTYPE  [ ] Modification to RRTYPE
> B.2 Kind of RR:  [x] Data RR  [ ] Meta-RR
> 
> C. Contact Information for submitter (will be publicly posted):
>     Name: James Addison              Email Address: james@reciperadar.com
>     International telephone number: N/A
>     Other contact handles: N/A
> 
> D. Motivation for the new RRTYPE application.
> [...]

Hi,

I cannot contribute to the question whether the proposed record type is 
necessary or not or whether it accomplishes its task. Since you don't 
give an explanation where the name "B" comes from, could you please give 
it a reasonable, perhaps mnemonic name? Since the types are represented 
by a numeric constant in the protocol, a longer name does not hurt in 
any way but makes the understanding and recognition a lot easier. Thanks.

Regards,

Klaus