IETF Logo Mail Archive

[DNSOP] Re: [v6ops] Re: Re: Re: Moving DNS64 (RFC6147) to Internet Standard

Michael Richardson <mcr+ietf@sandelman.ca> Mon, 13 April 2026 15:06 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 34FDBDB52219; Mon, 13 Apr 2026 08:06:22 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1776092782; bh=CY7oyTikXf0GrHeMPVu2WOgWA7P2IbytIl0d8n+bvAs=; h=From:To:Subject:In-Reply-To:References:Date; b=TBmhCCo1ChXZyj4RAFiDX29YBSu4l2uPl+Ruu1CsGW0nBfM/LzIjP+QBwSv0JmKIa m8yYj5tH8t6D59UEDbhGD75uj3lJXP0H33pHAgjqDB775QGtCwOzuKFym5QBSJUol5 N6MXBEV1cyX5KzN6Eb8M4EMHcVHeyby1lPwphDV8=
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level:
X-Spam-Status: No, score=-2.098 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_VALIDITY_CERTIFIED_BLOCKED=0.001, RCVD_IN_VALIDITY_RPBL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham 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 mjdwbAsqWKV9; Mon, 13 Apr 2026 08:06:21 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [209.87.249.19]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-256)) (No client certificate requested) by mail2.ietf.org (Postfix) with ESMTPS id 91949DB5220F; Mon, 13 Apr 2026 08:06:21 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by tuna.sandelman.ca (Postfix) with ESMTP id 3551D39F39; Mon, 13 Apr 2026 11:06:21 -0400 (EDT)
Received: from tuna.sandelman.ca ([127.0.0.1]) by localhost (localhost [127.0.0.1]) (amavis, port 10024) with LMTP id ESvMjgG858Ir; Mon, 13 Apr 2026 11:06:19 -0400 (EDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sandelman.ca; s=mail; t=1776092779; bh=mTFN1xc3iTTnB62zdTDp7+nBhOjYdGZMxP6yO8VXpkE=; h=From:To:Subject:In-Reply-To:References:Date:From; b=siTih0m27/aMtIQmUNsD7kiCUXGOJxTg9Fr8JfzmNB6prDhw5P/DpFHF9pysfGs40 L2SRKC9U4rz1Y5qJmqwORlLJERobVf3t7Qcxnol06JAzI2ko7uPyvGTFct5pmWoCs6 UW4jF2NYA+atQcrPnFqOnJp8CSLpYOgTOkRAw0je+2+eKq2UgpxXeKEezuZ1tWzUbY N0culkPNSWMCoN/pM3IXdCAnDwkpC0i6OX/4ZZyICGByMajzyDThicUUcHu81Qfmai A6rbBBScyZ2mW/uWReRMT5sNOS437Asz/DM2YGyb1eva0pYMICfaVK7mMCi+lQC9e1 POiBzr8nJVjRA==
Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id 1897A39EAF; Mon, 13 Apr 2026 11:06:19 -0400 (EDT)
Received: from obiwan.sandelman.ca (obiwan.sandelman.ca [127.0.0.1]) by sandelman.ca (Postfix) with ESMTP id 118691CD; Mon, 13 Apr 2026 11:06:19 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: Tim Chown <Tim.Chown@jisc.ac.uk>, "dnsop@ietf.org" <dnsop@ietf.org>, IPv6 Operations <v6ops@ietf.org>
In-Reply-To: <DB9PR07MB7771839D4A9F2D4380926DCCD6242@DB9PR07MB7771.eurprd07.prod.outlook.com>
References: <m1wAunU-0000NEC@stereo.hq.phicoh.net> <2338256.t9SDvczpPo@localhost> <038ae9d1-34fc-4085-aa6d-76ef79287857@gmail.com> <PARP264MB6760A67BB8F2060962E8A64088592@PARP264MB6760.FRAP264.PROD.OUTLOOK.COM> <B93DB6C8-2974-4915-93DE-DFCB6B858AFA@consulintel.es> <21557.1775841053@obiwan.sandelman.ca> <DB9PR07MB7771839D4A9F2D4380926DCCD6242@DB9PR07MB7771.eurprd07.prod.outlook.com>
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, 13 Apr 2026 11:06:19 -0400
Message-ID: <16874.1776092779@obiwan.sandelman.ca>
Message-ID-Hash: JHRY4OTLEHUYZ2QU45FAVAFJRLG5PKBE
X-Message-ID-Hash: JHRY4OTLEHUYZ2QU45FAVAFJRLG5PKBE
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: [v6ops] Re: Re: Re: Moving DNS64 (RFC6147) to Internet Standard
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/gvj74PUxlzylrlTi6fwJzyIX6_Y>
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>

Tim Chown <Tim.Chown@jisc.ac.uk> wrote:
    > It is widely implemented, and there are multiple implementations, but
    > at the same time there very much is​​ a health warning to be carried with
    > it, and its use will (hopefully) decrease over time.  It served a
    > purpose, but we’ve learnt and moved on.

yeah... so the mbone was prematurely killed based upon the same argument.
"We moved on".
So we have no multicast anywhere.  Not even for people with a clue.

IPv6 would have suffered the same fate, when 6bone got
killed, and if not for 6to4 and Teredo, it would have completely failed.
(Even the way in which 6to4 and Teredo were killed was silly)

    > We need that health warning to be clearly stated, noting that DNS64
    > serves a purpose (with caveats) particularly for devices that will
    > never see a host-based shim supported, as Michael points out.

The health warning is entirely appropriate.
Go read RFC2705 for the whopper of health warnings...

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

**       My working hours and your working hours may be different.         **
** Please do not feel obligated to reply outside your normal working hours **

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