Last Call: <draft-ietf-v6ops-6mops-12.txt> (IPv6-mostly Networks: Deployment and Operations Considerations) to Informational RFC
The IESG <iesg-secretary@ietf.org> Thu, 29 October 2026 17:29 UTC
Received: by mx.ietf.org (Postfix) id B84C346; Thu, 29 Oct 2026 17:29:33 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ietf.org; s=mail; t=1793294974; h=from:from:sender:sender:reply-to:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:cc:mime-version:mime-version: content-type:content-type: content-transfer-encoding:content-transfer-encoding; bh=0du6MZE3v7Qgr4z9+S9bTFDMyMu7mUxdE8Nrt1EtrCY=; b=BCt/vecXoGSDgGy28og58TQfJipIrf/fdnM98vgL4VZWNbTKugrt7szxorRlK3MCgh3Cr6 0uPHnKPDazgZ9yrarE05F/iyDiLwAonDxfLZD/u8P6UNmfKHKZB7AiYzqWZ6glM+Yc/Ozg r6/yrzLihpX+fQhl6PZ6QK6LBc/YP2k=
Authentication-Results: ORIGINATING; auth=pass smtp.auth=mail2@ietf.org smtp.mailfrom=iesg-secretary@ietf.org
Received: from [10.244.9.51] (gaia.k8s.ietf.org [4.156.85.76]) by mail2.ietf.org (Postfix) with ESMTP id 831C513B3D8DA; Thu, 29 Oct 2026 10:29:33 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Subject: Last Call: <draft-ietf-v6ops-6mops-12.txt> (IPv6-mostly Networks: Deployment and Operations Considerations) to Informational RFC
X-Test-IDTracker: no
X-IETF-IDTracker: 12.82.1
Auto-Submitted: auto-generated
Precedence: bulk
Sender: iesg-secretary@ietf.org
Message-ID: <179329497342.705070.8158010883192755127@dt-datatracker-7dc874ff8f-sl5zv>
Date: Thu, 29 Oct 2026 10:29:33 -0700
Message-ID-Hash: KMCJWHNYGGUX2BPABVLSOBCHGTMFESK2
X-Message-ID-Hash: KMCJWHNYGGUX2BPABVLSOBCHGTMFESK2
X-MailFrom: iesg-secretary@ietf.org
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; loop; banned-address; header-match-ietf-announce.ietf.org-0; emergency; member-moderation; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: draft-ietf-v6ops-6mops@ietf.org, mohamed.boucadair@orange.com, tim.chown@jisc.ac.uk, v6ops-chairs@ietf.org, v6ops@ietf.org
X-Mailman-Version: 3.3.10
Reply-To: last-call@ietf.org, v6ops@ietf.org
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/csrsiYxf-BKgvfsZPcus2_BvPHQ>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf-announce>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Owner: <mailto:ietf-announce-owner@ietf.org>
List-Post: <mailto:ietf-announce@ietf.org>
List-Subscribe: <mailto:ietf-announce-join@ietf.org>
List-Unsubscribe: <mailto:ietf-announce-leave@ietf.org>
The IESG has received a request from the IPv6 Operations WG (v6ops) to consider the following document: 'IPv6-mostly Networks: Deployment and Operations Considerations' <draft-ietf-v6ops-6mops-12.txt> as Informational RFC The IESG plans to make a decision on this document in the coming weeks, and solicits last-call comments. Please send substantive comments to the last-call@ietf.org mailing list, with v6ops@ietf.org copied, no later than 2026-11-12. Please retain the beginning of the Subject line to facilitate automated sorting. Abstract This document discusses a deployment scenario called "an IPv6-mostly network", when IPv6-only and IPv4-enabled endpoints coexist on the same network (e.g. local area network (LAN)). This approach enables incremental transition from dual-stack to IPv6-only networks by allowing IPv6-capable devices to remain IPv6-only while the network is seamlessly supplying IPv4 addresses to those devices that require them. This document discusses the requirements, recommendations, and challenges associated with deploying IPv6-mostly networks in enterprise and public Wi-Fi environments. The file can be obtained via https://datatracker.ietf.org/doc/draft-ietf-v6ops-6mops/ No IPR declarations have been submitted directly on this I-D.