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

"jordi.palet@consulintel.es" <jordi.palet@consulintel.es> Sat, 11 April 2026 08:20 UTC

Return-Path: <prvs=1561945371=jordi.palet@consulintel.es>
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 43BF8DA473DA; Sat, 11 Apr 2026 01:20:24 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1775895624; bh=f7hnkSiiwrOFazKXEZGahmujzf60wGI+ULtobZ9WDzM=; h=Subject:From:In-Reply-To:Date:Cc:References:To; b=WSoXSVMyYJjvj/r0Yqp7ceiyjAIwLC8aXjw4JIYXMxUBgVZVnQ34uqZxaOL5jXzEW p1i6Kb8tFTF188+/JnTNN7VtukV+8L2u/flLDbrDY2xvrycxz9MGYlj+P+rQhyrM6H XY6ZIsYi32P9K0Odgek0ZALOKdLbZfHgmhduODZE=
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_HELO_NONE=0.001] autolearn=ham autolearn_force=no
Authentication-Results: mail2.ietf.org (amavisd-new); dkim=pass (2048-bit key) header.d=consulintel.es
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 gyX_UgmroKNN; Sat, 11 Apr 2026 01:20:23 -0700 (PDT)
Received: from mail.consulintel.es (mail.consulintel.es [IPv6:2001:470:1f09:495::5]) (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 BC05CDA473D2; Sat, 11 Apr 2026 01:20:23 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=consulintel.es; s=mailer; t=1775895623; x=1776500423; i=jordi.palet@consulintel.es; q=dns/txt; h=Content-Type: Mime-Version:Subject:From:In-Reply-To:Date:Cc: Content-Transfer-Encoding:Message-Id:References:To; bh=f7hnkSiiw rOFazKXEZGahmujzf60wGI+ULtobZ9WDzM=; b=WKyRjv9b8Qyk1wB5PXXVw7i5y oaM8X1xhV3u6CpDtjvAzGME+L16rg+0lDYHD6sLJOgBb1GUo+B93fLV1nLzpCH15 s68aHx+9OiRsyaeeLRf+jhsjfRGDlyzykHfQ+MAAKVAhem9h4spUNjG1Zp/nSlwf p5ZUEKtX2Qy7xdwCd4YWx9/nKDALGY7088Y5+FVEECmJeYhZR5ISTMVTD2+kbL0n hlxIZOb3jHO+lcIruVh/R+On2/+B/EvP9kXPZyAFRgRTQh4e/BbOp7WauVkt9ve2 S4JyBFzuumhE1Zw+Ls+B4eAwbb1jjl9ctyyVmdQdGBFCEFux1VB0ASeVHtOcw==
X-MDAV-Processed: mail.consulintel.es, Sat, 11 Apr 2026 10:20:23 +0200 (not processed: message from trusted source)
X-Spam-Processed: mail.consulintel.es, Sat, 11 Apr 2026 10:20:22 +0200
Received: from smtpclient.apple by mail.consulintel.es (10.10.10.5) (MDaemon PRO v25.5.0) with ESMTPSA id md5001002618785.msg; Sat, 11 Apr 2026 10:20:22 +0200
X-MDRemoteIP: 2001:470:1f09:495:c5db:75f:ddd9:542e
X-MDArrival-Date: Sat, 11 Apr 2026 10:20:22 +0200
X-Authenticated-Sender: jordi.palet@consulintel.es
X-Return-Path: prvs=1561945371=jordi.palet@consulintel.es
X-Envelope-From: jordi.palet@consulintel.es
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3864.500.181\))
From: "jordi.palet@consulintel.es" <jordi.palet@consulintel.es>
In-Reply-To: <AA531AEF-836A-4A4E-83D6-3579EEB246F1@icann.org>
Date: Sat, 11 Apr 2026 10:20:09 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <606FA99B-CB14-44F6-B041-6439489D157E@consulintel.es>
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> <AA531AEF-836A-4A4E-83D6-3579EEB246F1@icann.org>
To: "dnsop@ietf.org" <dnsop@ietf.org>
X-Mailer: Apple Mail (2.3864.500.181)
X-MDCFSigsAdded: consulintel.es
Message-ID-Hash: COJA5LC26RHS7SSGNNDMAMIQWT3TVKMD
X-Message-ID-Hash: COJA5LC26RHS7SSGNNDMAMIQWT3TVKMD
X-MailFrom: prvs=1561945371=jordi.palet@consulintel.es
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: IPv6 Operations <v6ops@ietf.org>
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [DNSOP] Re: [v6ops] [Ext] Re: 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/cLAQJ3P4cBSeYgI0YpnUM29y-Yg>
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>

My understanding about the process is that if we don’t change the protocol in the sense of breaking back-wards interoperability, it can be advanced to IS.

In any case, I’m happy with a two steps process if needed.

Regards,
Jordi

@jordipalet


> El 10 abr 2026, a las 19:18, Paul Hoffman <paul.hoffman@icann.org> escribió:
> 
> As a process issue, I don't think that DNS64 can be moved to Internet Standard and at the same time add wording to it that says how it should or should not be used on the Internet.
> 
> I also don't think RFC 6147 *has* to be moved to Internet Standard at the same time as other IPv6ish things are being moved up. Because of the significant amount of hesitancy shown, I don't think it is appropriate to move the standard up without a revision of its use and applicability statements. If those are accepted, it can be moved to IS a few years later.
> 
> --Paul Hoffman
> 
> _______________________________________________
> v6ops mailing list -- v6ops@ietf.org
> To unsubscribe send an email to v6ops-leave@ietf.org


**********************************************
IPv4 is over
Are you ready for the new Internet ?
http://www.theipv6company.com
The IPv6 Company

This electronic message contains information which may be privileged or confidential. The information is intended to be for the exclusive use of the individual(s) named above and further non-explicilty authorized disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited and will be considered a criminal offense. If you are not the intended recipient be aware that any disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited, will be considered a criminal offense, so you must reply to the original sender to inform about this communication and delete it.