IETF Logo Mail Archive

[DNSOP] Re: blasphemy in the DNS

Michael Richardson <mcr+ietf@sandelman.ca> Mon, 23 February 2026 23:52 UTC

Return-Path: <mcr+ietf@sandelman.ca>
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 E701BBC97C00 for <dnsop@mail2.ietf.org>; Mon, 23 Feb 2026 15:52:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -2.8
X-Spam-Level:
X-Spam-Status: No, score=-2.8 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_LOW=-0.7, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: mail2.ietf.org (amavisd-new); dkim=pass (2048-bit key) header.d=sandelman.ca
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 cTIJSA7SSh32 for <dnsop@mail2.ietf.org>; Mon, 23 Feb 2026 15:52:13 -0800 (PST)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [IPv6:2607:f0b0:f:3:216:3eff:fe7c:d1f3]) (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 80D3BBC97BF5 for <dnsop@ietf.org>; Mon, 23 Feb 2026 15:52:13 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by tuna.sandelman.ca (Postfix) with ESMTP id 58DD33897D; Mon, 23 Feb 2026 18:52:07 -0500 (EST)
Received: from tuna.sandelman.ca ([127.0.0.1]) by localhost (localhost [127.0.0.1]) (amavis, port 10024) with LMTP id yfGq9nvcaKfz; Mon, 23 Feb 2026 18:52:05 -0500 (EST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sandelman.ca; s=mail; t=1771890725; bh=Cg62Wde+zwOEI5LV6uykuL+EYE2JJm+zueHDZ5jhw5Q=; h=From:To:Subject:In-Reply-To:References:Date:From; b=gYf5p1f44tczVqp0uqJmx1l/Y8YcCnkqjFEE0DXvwrBCo7WQyzktGYlUUu66/Qf6t 1f+qBdDp6LWWEIVomUs8jucvYJe0fAhXKHfgxVqyAegbv4SvTwOs3Y84XS01tGu3Dw sE/w6hDLsfqTJ8k/GQfGmYDPJi8Ug8vrdA8yo/Fco5W9D3+eau8X7/g78wtld1odOF AH9/q5fi7hhS4hxThX7ll+GHCROydIMOOtR88ju87sp8khg89OtDT4TrDQ2N9R5ogz Tz0kGDLJDcx52ioTI0keekG9nlEyv1eE4/DzYXTlU0r/ZJSMMx/talkQ1mhCBzMmsQ a85PNTb6Giqbg==
Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id AF0E73897B; Mon, 23 Feb 2026 18:52:05 -0500 (EST)
Received: from obiwan.sandelman.ca (obiwan.sandelman.ca [127.0.0.1]) by sandelman.ca (Postfix) with ESMTP id A8B29184; Mon, 23 Feb 2026 18:52:05 -0500 (EST)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: Mark Nottingham <mnot@mnot.net>, Jim Reid <jim@rfc1035.com>, Ben Schwartz <bemasc=40meta.com@dmarc.ietf.org>, "dnsop@ietf.org WG" <dnsop@ietf.org>
In-Reply-To: <AD4FD6AB-9A31-47FA-90C7-EA528BC5F090@mnot.net>
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> <14CECC2A-4108-4146-8BB2-D91B45D7BA7E@rfc1035.com> <17973.1771890257@obiwan.sandelman.ca> <AD4FD6AB-9A31-47FA-90C7-EA528BC5F090@mnot.net>
X-Mailer: MH-E 8.6+git; nmh 1.8+dev; Emacs 30.1
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0;<'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg="pgp-sha512"; protocol="application/pgp-signature"
Date: Mon, 23 Feb 2026 18:52:05 -0500
Message-ID: <20179.1771890725@obiwan.sandelman.ca>
Message-ID-Hash: GVKANGWR4SVQML5U2INES4LV5FGI6RSR
X-Message-ID-Hash: GVKANGWR4SVQML5U2INES4LV5FGI6RSR
X-MailFrom: mcr+ietf@sandelman.ca
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
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [DNSOP] Re: blasphemy in the DNS
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/yteNuhVwQItO3TvUwR8oXA01kcg>
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>

Mark Nottingham <mnot@mnot.net> wrote:
    > I don't know if you're joking or not, but the goal here is NOT for IANA
    > to maintain a registry that enumerates the legal reasons for
    > censorship/filtering/whatever.

I don't yet know what parts go into IANA, I'm trying to understand what
information is intended to be returned to the user/browser.
It's not as I had first understood things. Probably I assumed I understood,
when actually, I was completely wrong.

Jim did *joke* that he wanted an error code for blasphemy, and if there was
one, I think this is how it would be used (in the context of Monty Python, Life of Brian).

I think that _blasphemy_ would *not* be an IANA code, but rather a charge/event/suit.

    >> to that end, My understanding is that it is desired to have
    >>
    >> code:    blasphemy,
    >> context: spoke name of diety while appreciating a piece of Halibut,
    >> on Tuesday September 3, 19 BCE.


--
Michael Richardson <mcr+IETF@sandelman.ca>   . o O ( IPv6 IøT consulting )
           Sandelman Software Works Inc, Ottawa and Worldwide

v2.46.0 | Report a Bug | By Email | System Status