[v6ops] Call for adoption: draft-palet-v6ops-rfc6146-bis-03 (Ends 2026-02-13)
Nick Buraglio via Datatracker <noreply@ietf.org> Fri, 23 January 2026 15:32 UTC
Return-Path: <noreply@ietf.org>
X-Original-To: v6ops@ietf.org
Delivered-To: v6ops@mail2.ietf.org
Received: from [10.244.6.51] (unknown [4.156.85.76]) by mail2.ietf.org (Postfix) with ESMTP id D4C3EAC08084; Fri, 23 Jan 2026 07:32:22 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Nick Buraglio via Datatracker <noreply@ietf.org>
To: v6ops@ietf.org, v6ops-chairs@ietf.org, draft-palet-v6ops-rfc6146-bis@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 12.57.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <176918234280.145871.1981677279828833616@dt-datatracker-77f8b84995-z4hzn>
Date: Fri, 23 Jan 2026 07:32:22 -0800
Message-ID-Hash: TE4OYTRV53BA57ZCWLYEOVQKTFHODQN7
X-Message-ID-Hash: TE4OYTRV53BA57ZCWLYEOVQKTFHODQN7
X-MailFrom: noreply@ietf.org
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-v6ops.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
Reply-To: Nick Buraglio <buraglio@forwardingplane.net>
Subject: [v6ops] Call for adoption: draft-palet-v6ops-rfc6146-bis-03 (Ends 2026-02-13)
List-Id: v6ops discussion list <v6ops.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/5wiyoA8Cia-WKW4vZITA9PfiLcs>
List-Archive: <https://mailarchive.ietf.org/arch/browse/v6ops>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Owner: <mailto:v6ops-owner@ietf.org>
List-Post: <mailto:v6ops@ietf.org>
List-Subscribe: <mailto:v6ops-join@ietf.org>
List-Unsubscribe: <mailto:v6ops-leave@ietf.org>
This message starts a v6ops WG Call for Adoption of: draft-palet-v6ops-rfc6146-bis-03 This Working Group Call for Adoption ends on 2026-02-13 Abstract: This document describes stateful NAT64 translation, which allows IPv6-only clients to contact IPv4 servers using unicast UDP, TCP, or ICMP. One or more public IPv4 addresses assigned to a NAT64 translator are shared among several IPv6-only clients. When stateful NAT64 is used in conjunction with DNS64, no changes are usually required in the IPv6 client or the IPv4 server. Please reply to this message and indicate whether or not you support adoption of this Internet-Draft by the v6ops WG. Comments to explain your preference are greatly appreciated. Please reply to all recipients of this message and include this message in your response. Authors, and WG participants in general, are reminded of the Intellectual Property Rights (IPR) disclosure obligations described in BCP 79 [2]. Appropriate IPR disclosures required for full conformance with the provisions of BCP 78 [1] and BCP 79 [2] must be filed, if you are aware of any. Sanctions available for application to violators of IETF IPR Policy can be found at [3]. Thank you. [1] https://datatracker.ietf.org/doc/bcp78/ [2] https://datatracker.ietf.org/doc/bcp79/ [3] https://datatracker.ietf.org/doc/rfc6701/ The IETF datatracker status page for this Internet-Draft is: https://datatracker.ietf.org/doc/draft-palet-v6ops-rfc6146-bis/ There is also an HTMLized version available at: https://datatracker.ietf.org/doc/html/draft-palet-v6ops-rfc6146-bis-03 A diff from the previous version is available at: https://author-tools.ietf.org/iddiff?url2=draft-palet-v6ops-rfc6146-bis-03
- [v6ops] Call for adoption: draft-palet-v6ops-rfc6… Nick Buraglio via Datatracker
- [v6ops] Re: Call for adoption: draft-palet-v6ops-… Gábor LENCSE
- [v6ops] Re: Call for adoption: draft-palet-v6ops-… Michael Richardson
- [v6ops] Re: Call for adoption: draft-palet-v6ops-… jordi.palet@consulintel.es