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

Michael Richardson <mcr+ietf@sandelman.ca> Mon, 13 April 2026 15:01 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 9AECADB50A30; Mon, 13 Apr 2026 08:01:06 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1776092466; bh=VrGmTPokHx5t1QkSZbp32Q+9dzHNlbhq4IlqX2ZQkm8=; h=From:To:Subject:In-Reply-To:References:Date; b=DapFNIUy5nXuJ1OzUJ+ZX5N9us9hcPDCQsvshqvIAp3lnUp+oMTu69PRxUlTcK6cf C69RrvV1DdFTxqoNZ7ng6e8wT6OMtDfwT8JKPdk8/ls1Pj+wIAJPhl7JZR7b27/koR ImLQ28TDwWfNI8ttnWPYuWLHiB0WMYyNmUkqMtao=
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 R0H5KV0ILMQC; Mon, 13 Apr 2026 08:01:06 -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) server-digest SHA256) (No client certificate requested) by mail2.ietf.org (Postfix) with ESMTPS id F0058DB50A21; Mon, 13 Apr 2026 08:01:05 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by tuna.sandelman.ca (Postfix) with ESMTP id 8AB0339F39; Mon, 13 Apr 2026 11:01:05 -0400 (EDT)
Received: from tuna.sandelman.ca ([127.0.0.1]) by localhost (localhost [127.0.0.1]) (amavis, port 10024) with LMTP id SGlNUpVrxl5c; Mon, 13 Apr 2026 11:01:03 -0400 (EDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sandelman.ca; s=mail; t=1776092463; bh=CwfyMMLczfAe2VnCkEm5MeYTbBpR3kYlA62W8U1Th7Y=; h=From:To:Subject:In-Reply-To:References:Date:From; b=CP4CCSEt2uMWn8U8kJ1JPSCFpuNGI1azW67gQq4GP5JuPx11ZmkVN8PUSRxiOeLGp CZjEEGR2qybI42eIp7eLuu9GiJjPc5PV91351QAWGyGCTJhGVMlsR0gK7g4yvOFoXw UbxFGbcqifFZsLSm21mAb2t+ImSTAzYN7UqVRsTQGmBblI/n/YfUfzdnpKT6KWSaZm YTdtPnFQFnljjkVj9X9B8B+idfFTpt/qvucXS23RwPpRZjUsQdp5Vsl7pmKsL5pFNo j401VvkT4FO8h4+ebx+JG9/TMTHSdnzsDiRdJ+fcPnomTYqIa9SSr2fOv1a522dkIV BGVqa2PMq7m2Q==
Received: from sandelman.ca (obiwan.sandelman.ca [209.87.249.21]) by tuna.sandelman.ca (Postfix) with ESMTP id 5F8BA39EAF; Mon, 13 Apr 2026 11:01:03 -0400 (EDT)
Received: from obiwan.sandelman.ca (obiwan.sandelman.ca [127.0.0.1]) by sandelman.ca (Postfix) with ESMTP id 5B82B1CD; Mon, 13 Apr 2026 11:01:03 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: Philip Homburg <pch-dnsop-7@u-1.phicoh.com>, dnsop@ietf.org, IPv6 Operations <v6ops@ietf.org>
In-Reply-To: <m1wCHUo-0000QZC@stereo.hq.phicoh.net>
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> <m1wB6jW-0000VYC@stereo.hq.phicoh.net> <25022.1775841874@obiwan.sandelman.ca> <m1wBGFD-0000PhC@stereo.hq.phicoh.net> <5539.1775850116@obiwan.sandelman.ca> <m1wCHUo-0000QZC@stereo.hq.phicoh.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, 13 Apr 2026 11:01:03 -0400
Message-ID: <15458.1776092463@obiwan.sandelman.ca>
Message-ID-Hash: U4ZFAZW2CJME54EKUXCNBTRD7WNIRWWE
X-Message-ID-Hash: U4ZFAZW2CJME54EKUXCNBTRD7WNIRWWE
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: 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/Lv4JJVY0rWaHFeTpO1qdhJFmY5g>
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>

Philip Homburg <pch-dnsop-7@u-1.phicoh.com> wrote:
    > Maybe the RFC processes should not be abused for RFPs?

Uhm.  Being able to cite RFC in trade-agreement compliant RFPs are 96% of the
reason companies are willing to fund the IETF to produce RFCs.
If not for that, governments would be unable to procure either DNS servers or
IPv6 routers, etc.

It's not an abuse of the RFPs, for some, it's their primary purpose.
(Yes, I live in a government town.  Yes, I talk to people who do this.  I've
even had products on government standing offer, based upon RFC compliance)

    > If you cannot put a standards track RFC in an RFP (and RFC 6147 is standards
    > track) then that is not something the IETF needs to fix?

Depending upon how the other documents are advanced, if 6147 is not advanced
as well, it might well need to be removed from being referenced.  That
effectively deprecates it from a procurement point of view.

--
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 **