RFC 9686 on Registering Self-Generated IPv6 Addresses Using DHCPv6

rfc-editor@rfc-editor.org Thu, 05 December 2024 23:00 UTC

Return-Path: <wwwrun@rfcpa.rfc-editor.org>
X-Original-To: ietf-announce@ietf.org
Delivered-To: ietf-announce@ietfa.amsl.com
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 ietfa.amsl.com (Postfix) with ESMTPS id 0F65FC14F686; Thu, 5 Dec 2024 15:00:37 -0800 (PST)
Received: by rfcpa.rfc-editor.org (Postfix, from userid 461) id 714711DFDDD; Thu, 5 Dec 2024 15:00:36 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 9686 on Registering Self-Generated IPv6 Addresses Using DHCPv6
From: rfc-editor@rfc-editor.org
Content-type: text/plain; charset="UTF-8"
Message-Id: <20241205230036.714711DFDDD@rfcpa.rfc-editor.org>
Date: Thu, 05 Dec 2024 15:00:36 -0800
Message-ID-Hash: ZJP2L4SY27M7YVX4OVGA3A32JK73RMZG
X-Message-ID-Hash: ZJP2L4SY27M7YVX4OVGA3A32JK73RMZG
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, dhcwg@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/Sv8C2SZVAzyw_NisqWymbXoskpk>
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 9686

        Title:      Registering Self-Generated IPv6 Addresses 
                    Using DHCPv6 
        Author:     W. Kumari,
                    S. Krishnan,
                    R. Asati,
                    L. Colitti,
                    J. Linkova,
                    S. Jiang
        Status:     Standards Track
        Stream:     IETF
        Date:       December 2024
        Mailbox:    warren@kumari.net,
                    suresh.krishnan@gmail.com,
                    rajiv.asati@gmail.com,
                    lorenzo@google.com,
                    furry13@gmail.com,
                    shengjiang@bupt.edu.cn
        Pages:      15
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-dhc-addr-notification-13.txt

        URL:        https://www.rfc-editor.org/info/rfc9686

        DOI:        10.17487/RFC9686

This document defines a method to inform a DHCPv6 server that a
device has one or more self-generated or statically configured
addresses.

This document is a product of the Dynamic Host Configuration 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
Association Management Solutions, LLC