RFC 9762 on Using Router Advertisements to Signal the Availability of DHCPv6 Prefix Delegation to Clients
rfc-editor@rfc-editor.org Tue, 17 June 2025 04:04 UTC
Return-Path: <wwwrun@rfcpa.rfc-editor.org>
X-Original-To: ietf-announce@ietf.org
Delivered-To: ietf-announce@mail2.ietf.org
Received: from rfcpa.rfc-editor.org (unknown [167.172.21.234]) (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 4EBB035C3E05; Mon, 16 Jun 2025 21:04:04 -0700 (PDT)
Received: by rfcpa.rfc-editor.org (Postfix, from userid 461) id 19890268D4B; Mon, 16 Jun 2025 21:04:04 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 9762 on Using Router Advertisements to Signal the Availability of DHCPv6 Prefix Delegation to Clients
From: rfc-editor@rfc-editor.org
Content-type: text/plain; charset="UTF-8"
Message-Id: <20250617040404.19890268D4B@rfcpa.rfc-editor.org>
Date: Mon, 16 Jun 2025 21:04:04 -0700
Message-ID-Hash: TN6IDLKG452JZ4WBTIESVPIPKUJOYRLO
X-Message-ID-Hash: TN6IDLKG452JZ4WBTIESVPIPKUJOYRLO
X-MailFrom: wwwrun@rfcpa.rfc-editor.org
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-ietf-announce.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org, ipv6@ietf.org
X-Mailman-Version: 3.3.9rc6
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/hYNiud0mcH4UYQRXDP1z_dY5Ln8>
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>
A new Request for Comments is now available in online RFC libraries. RFC 9762 Title: Using Router Advertisements to Signal the Availability of DHCPv6 Prefix Delegation to Clients Author: L. Colitti, J. Linkova, X. Ma, Ed., D. Lamparter Status: Standards Track Stream: IETF Date: June 2025 Mailbox: lorenzo@google.com, furry13@gmail.com, xiaom@google.com, equinox@diac24.net Pages: 14 Updates: RFC 4861, RFC 4862 I-D Tag: draft-ietf-6man-pio-pflag-12.txt URL: https://www.rfc-editor.org/info/rfc9762 DOI: 10.17487/RFC9762 This document defines the P flag in the Prefix Information Option (PIO) of IPv6 Router Advertisements (RAs). The flag is used to indicate that the network prefers that clients use the deployment model in RFC 9663 instead of using individual addresses in the on-link prefix assigned using Stateless Address Autoconfiguration (SLAAC) or DHCPv6 address assignment. This document updates RFC 4862 to indicate that the Autonomous flag in a PIO needs to be ignored if the PIO has the P flag set. It also updates RFC 4861 to specify that the P flag indicates DHCPv6 prefix delegation support for clients. This document is a product of the IPv6 Maintenance Working Group of the IETF. This is now a Proposed Standard. STANDARDS TRACK: This document specifies an Internet Standards Track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the Official Internet Protocol Standards (https://www.rfc-editor.org/standards) for the standardization state and status of this protocol. Distribution of this memo is unlimited. This announcement is sent to the IETF-Announce and rfc-dist lists. To subscribe or unsubscribe, see https://www.ietf.org/mailman/listinfo/ietf-announce https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist For searching the RFC series, see https://www.rfc-editor.org/search For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk Requests for special distribution should be addressed to either the author of the RFC in question, or to rfc-editor@rfc-editor.org. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. The RFC Editor Team