IETF Logo Mail Archive

Re: [DNSOP] New Version Notification - draft-ietf-dnsop-dns-catalog-zones-09.txt

Paul Wouters <paul@nohats.ca> Thu, 09 February 2023 13:46 UTC

Return-Path: <paul@nohats.ca>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 05B32C14CE2F; Thu, 9 Feb 2023 05:46:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.093
X-Spam-Level:
X-Spam-Status: No, score=-2.093 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_BLOCKED=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_NONE=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 (1024-bit key) header.d=nohats.ca
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 lgQ9hxO8R5LA; Thu, 9 Feb 2023 05:46:46 -0800 (PST)
Received: from mx.nohats.ca (mx.nohats.ca [IPv6:2a03:6000:1004:1::85]) (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 DA626C14CF0C; Thu, 9 Feb 2023 05:46:45 -0800 (PST)
Received: from localhost (localhost [IPv6:::1]) by mx.nohats.ca (Postfix) with ESMTP id 4PCJ7Q481pz3CK; Thu, 9 Feb 2023 14:46:42 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nohats.ca; s=default; t=1675950402; bh=IXw7SQvAixrJoDG3LNxsTtbunJ41oW8RB6T/gr0ZOGs=; h=From:Date:Subject:Cc:To; b=NI6MU/zBdCBcUmSmMCLh0NbMNPYXWshupeNXr9qRK1O/Aqw1LfdsbSILUaHFRuaY8 Oh80tdvxFU3XaZylrDfoxi6QOf5LdvkvV7nYZ9+gdfyd1lLCan3m2526CUb5z8YcO4 ZhTN19hNIl92YO9HxRKyKTRTtbRYTvMCfoL0U7Lk=
X-Virus-Scanned: amavisd-new at mx.nohats.ca
Received: from mx.nohats.ca ([IPv6:::1]) by localhost (mx.nohats.ca [IPv6:::1]) (amavisd-new, port 10024) with ESMTP id Xx84sNHea5VW; Thu, 9 Feb 2023 14:46:41 +0100 (CET)
Received: from bofh.nohats.ca (bofh.nohats.ca [193.110.157.194]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx.nohats.ca (Postfix) with ESMTPS; Thu, 9 Feb 2023 14:46:41 +0100 (CET)
Received: from smtpclient.apple (unknown [193.110.157.208]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by bofh.nohats.ca (Postfix) with ESMTPSA id 96884691B46; Thu, 9 Feb 2023 08:46:40 -0500 (EST)
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: Paul Wouters <paul@nohats.ca>
Mime-Version: 1.0 (1.0)
Date: Thu, 09 Feb 2023 08:46:27 -0500
Message-Id: <4F7C6733-7F82-4BF7-9068-5733B3E50D87@nohats.ca>
Cc: Paul Wouters <paul.wouters@aiven.io>, draft-ietf-dnsop-dns-catalog-zones.authors@ietf.org, "dnsop@ietf.org WG" <dnsop@ietf.org>, Tim Wicinski <tjw.ietf@gmail.com>, "Murray S. Kucherawy" <superuser@gmail.com>
To: Willem Toorop <willem@nlnetlabs.nl>
X-Mailer: iPhone Mail (20C65)
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/0MXzJ7K5fa68j4e5bcRGLGnIJTg>
Subject: Re: [DNSOP] New Version Notification - draft-ietf-dnsop-dns-catalog-zones-09.txt
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 09 Feb 2023 13:46:50 -0000

On Feb 9, 2023, at 06:33, Willem Toorop <willem@nlnetlabs.nl> wrote:
> 
> Op 07-02-2023 om 16:45 schreef Paul Wouters:> I find the valid use of the name "invalid" to be pretty horrible. An
>> engineer looking at a catalog might quickly believe
>> the invalid is a bug where it should have shown a real domain. Why not _catalog.arpa or something ?
> 
> We, the co-authors, actually prefer producers to use a domain they own (because no chance on collisions with consumers from multiple producers). I've done a commit to express that more clearly. The new text is:
> 
>   ``It is RECOMMENDED to use a domain name owned by the catalog producer if possible, or if that is not possible use a name under a suitable name such as "invalid." [RFC6761].''

A name under a suitable name such as invalid would then be “example.com.invalid” and not as it has now just “invalid” ?

Or it could use “_catalog.example.com”  ?

Paul

v2.23.0 | Report a Bug | By Email