[DNSOP] blasphemy in the DNS

Jim Reid <jim@rfc1035.com> Mon, 23 February 2026 16:40 UTC

Return-Path: <jim@rfc1035.com>
X-Original-To: dnsop@mail2.ietf.org
Delivered-To: dnsop@mail2.ietf.org
Received: from localhost (localhost [127.0.0.1]) by mail2.ietf.org (Postfix) with ESMTP id 87377BC51A3D for <dnsop@mail2.ietf.org>; Mon, 23 Feb 2026 08:40:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail2.ietf.org ([166.84.6.31]) by localhost (mail2.ietf.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xkkiNfekaCHD for <dnsop@mail2.ietf.org>; Mon, 23 Feb 2026 08:40:54 -0800 (PST)
Received: from shaun.rfc1035.com (shaun.rfc1035.com [IPv6:2a00:1098:4b8::1]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by mail2.ietf.org (Postfix) with ESMTPS id E740DBC51A2B for <dnsop@ietf.org>; Mon, 23 Feb 2026 08:40:53 -0800 (PST)
Received: from smtpclient.apple (gromit.rfc1035.com [195.54.233.69]) (using TLSv1.2 with cipher ECDHE-ECDSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by shaun.rfc1035.com (Postfix) with ESMTPSA id 8C9742614D5; Mon, 23 Feb 2026 16:40:47 +0000 (UTC)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3826.700.81\))
From: Jim Reid <jim@rfc1035.com>
In-Reply-To: <DS0PR15MB567463427587984BB42F3CD0B377A@DS0PR15MB5674.namprd15.prod.outlook.com>
Date: Mon, 23 Feb 2026 16:40:46 +0000
Content-Transfer-Encoding: quoted-printable
Message-Id: <14CECC2A-4108-4146-8BB2-D91B45D7BA7E@rfc1035.com>
References: <177154390721.1462366.14455153337258556573@dt-datatracker-6ff7c68975-7k42g> <AFA212A4-FDDA-4BBC-AD07-655152EE08CC@mnot.net> <1c735c0f-2964-f0f1-1917-ab430c24d16e@nohats.ca> <5EBD15F2-5A0D-437B-96F7-9B9D3E73A37E@mnot.net> <5595.1771779435@obiwan.sandelman.ca> <651D7B0B-AD27-4F84-829A-698D3B3A2847@mnot.net> <18321.1771825961@obiwan.sandelman.ca> <E98247D1-4A86-478F-8AAB-4AD8433AEB61@mnot.net> <13125.1771831184@obiwan.sandelman.ca> <F397C063-87A3-42C8-9BE1-267729BE874C@mnot.net> <17468.1771845396@obiwan.sandelman.ca> <DS0PR15MB567463427587984BB42F3CD0B377A@DS0PR15MB5674.namprd15.prod.outlook.com>
To: Ben Schwartz <bemasc=40meta.com@dmarc.ietf.org>
X-Mailer: Apple Mail (2.3826.700.81)
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.4.3 (shaun.rfc1035.com); Mon, 23 Feb 2026 16:40:47 +0000 (UTC)
Message-ID-Hash: TVIX22RGIYTVDHBKSLCJPKN7G22I5BUR
X-Message-ID-Hash: TVIX22RGIYTVDHBKSLCJPKN7G22I5BUR
X-MailFrom: jim@rfc1035.com
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-dnsop.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: Michael Richardson <mcr+ietf@sandelman.ca>, Mark Nottingham <mnot@mnot.net>, "dnsop@ietf.org WG" <dnsop@ietf.org>
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [DNSOP] blasphemy in the DNS
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/_-Bvk2CinXmsuFOQJYZh9OZ0Ncw>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Owner: <mailto:dnsop-owner@ietf.org>
List-Post: <mailto:dnsop@ietf.org>
List-Subscribe: <mailto:dnsop-join@ietf.org>
List-Unsubscribe: <mailto:dnsop-leave@ietf.org>


> On 23 Feb 2026, at 16:11, Ben Schwartz <bemasc=40meta.com@dmarc.ietf.org> wrote:
> 
> In general, I am skeptical of extending the lexicon, because I don't want to end up in the position of needing an IANA registered error code for "blocked due to blasphemy", etc.

I agree Ben. OTOH a DNS error code for blasphemy would be *really, really* cool. :-)