BCP 242, RFC 9812 on Clarification of IPv6 Address Allocation Policy
rfc-editor@rfc-editor.org Wed, 22 October 2025 00:08 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 CC6A979F79E2; Tue, 21 Oct 2025 17:08:05 -0700 (PDT)
Received: by rfcpa.rfc-editor.org (Postfix, from userid 461) id A371DC000168; Tue, 21 Oct 2025 17:08:05 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: BCP 242, RFC 9812 on Clarification of IPv6 Address Allocation Policy
From: rfc-editor@rfc-editor.org
Content-type: text/plain; charset="UTF-8"
Message-Id: <20251022000805.A371DC000168@rfcpa.rfc-editor.org>
Date: Tue, 21 Oct 2025 17:08:05 -0700
Message-ID-Hash: EVWE6LD5AQJS7RRJL73SUDJ6DRLWDC3C
X-Message-ID-Hash: EVWE6LD5AQJS7RRJL73SUDJ6DRLWDC3C
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/uosG6YiYi1mAsTWaq_Ly1HOBopg>
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.
BCP 242
RFC 9812
Title: Clarification of IPv6 Address Allocation
Policy
Author: B. Carpenter,
S. Krishnan,
D. Farmer
Status: Best Current Practice
Stream: IETF
Date: October 2025
Mailbox: brian.e.carpenter@gmail.com,
suresh.krishnan@gmail.com,
farmer@umn.edu
Pages: 5
Updates: RFC 7249
See Also: BCP 242
I-D Tag: draft-ietf-6man-addr-assign-05.txt
URL: https://www.rfc-editor.org/info/rfc9812
DOI: 10.17487/RFC9812
This document specifies the approval process for changes to the "IPv6
Address Space" registry. It also updates RFC 7249.
This document is a product of the IPv6 Maintenance Working Group of the IETF.
BCP: This document specifies an Internet Best Current Practices for the
Internet Community, and requests discussion and suggestions for
improvements. 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