[IPv6]WG Last Call: draft-ietf-6man-slaac-renum-10 (Ends 2025-09-26)

Bob Hinden via Datatracker <noreply@ietf.org> Fri, 12 September 2025 15:14 UTC

Return-Path: <noreply@ietf.org>
X-Original-To: ipv6@ietf.org
Delivered-To: ipv6@mail2.ietf.org
Received: from [10.244.8.59] (unknown [4.156.85.76]) by mail2.ietf.org (Postfix) with ESMTP id A790F61A5AAE; Fri, 12 Sep 2025 08:14:41 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Bob Hinden via Datatracker <noreply@ietf.org>
To: 6man-chairs@ietf.org, draft-ietf-6man-slaac-renum@ietf.org, ipv6@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 12.49.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <175769008162.1551510.12699105800158422047@dt-datatracker-f7c8fdcb7-pjx77>
Date: Fri, 12 Sep 2025 08:14:41 -0700
Message-ID-Hash: A642OX5LPAVX6DOKLOBYT36ARS563RSE
X-Message-ID-Hash: A642OX5LPAVX6DOKLOBYT36ARS563RSE
X-MailFrom: noreply@ietf.org
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-ipv6.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: Bob Hinden <bob.hinden@gmail.com>
Subject: [IPv6]WG Last Call: draft-ietf-6man-slaac-renum-10 (Ends 2025-09-26)
List-Id: "IPv6 Maintenance Working Group (6man)" <ipv6.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/hdw9xtL-GUGRCrNsDrCauM9gTs4>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Owner: <mailto:ipv6-owner@ietf.org>
List-Post: <mailto:ipv6@ietf.org>
List-Subscribe: <mailto:ipv6-join@ietf.org>
List-Unsubscribe: <mailto:ipv6-leave@ietf.org>

Subject: WG Last Call: draft-ietf-6man-slaac-renum-10 (Ends 2025-09-26)

This message starts a 2-week WG Last Call for this document.

Abstract:
   In scenarios where network configuration information becomes invalid
   without explicit notification to the local network, local hosts may
   end up employing stale information for an unacceptably long period of
   time, thus resulting in interoperability problems.  This document
   improves the reaction of IPv6 Stateless Address Autoconfiguration to
   such configuration changes.  It formally updates RFC 4191, RFC 4861,
   RFC 4862, and RFC 8106.

File can be retrieved from:
https://datatracker.ietf.org/doc/draft-ietf-6man-slaac-renum/

Please review and indicate your support or objection to proceed with the
publication of this document by replying to this email keeping ipv6@ietf.org
in copy. Objections should be motivated and suggestions to resolve them are
highly appreciated.

Authors, and WG participants in general, are reminded again of the
Intellectual Property Rights (IPR) disclosure obligations described in BCP 79
[1]. 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/