# Rotate temporary IPv6 addresses within lifetime and regeneration bounds > Use RFC 8981 — Temporary Address Extensions for Stateless Address Autoconfiguration in IPv6 to review this narrow operational decision without extending the source beyond its stated scope. - Canonical URL: https://update.dsesecurity.com/updates/rotate-temporary-ipv6-addresses-within-lifetime-and-regeneration-bounds/ - Publisher: Detection Systems & Engineering (DSE Security) - Author: DSE Security Editorial Team - Published: 2026-08-27T12:16:14+00:00 - Modified: 2026-08-27T12:53:57+00:00 - Last reviewed by DSE: 2026-08-26 - Resource type: Checklist - DSE priority: Advisory - Topics: IT, Networks & Infrastructure - Reading time: 3 minutes ## What you need to know Use RFC 8981 — Temporary Address Extensions for Stateless Address Autoconfiguration in IPv6 to review this narrow operational decision without extending the source beyond its stated scope. ## Potentially affected Teams, systems, services, or facilities within the stated scope of RFC 8981 — Temporary Address Extensions for Stateless Address Autoconfiguration in IPv6 ## DSE recommendation Compare the observed state with the cited official source, document applicability and exceptions, and test any approved change with rollback safeguards. ## Article Treat this document as a focused evidence review: Rotate temporary IPv6 addresses within lifetime and regeneration bounds. Only the official source and traced locations below supply facts. Confirm applicability before acting. ## Source fact: The official [RFC 8981 — Temporary Address Extensions for Stateless Address Autoconfiguration in IPv6](https://www.rfc-editor.org/rfc/rfc8981.html) from RFC Editor / Internet Engineering Task Force supports the following bounded statements: - When an autoconfiguration prefix has no temporary address, a host should create one unless a prefix-specific policy says otherwise. The research record locates this support at Section 3.4 (Generating Temporary Addresses), step 3. - A temporary address cannot remain valid or preferred beyond the configured temporary-address maxima, and its actual lifetimes are also bounded by the advertised prefix lifetimes. The research record locates this support at Section 3.4 (Generating Temporary Addresses), steps 1 and 4. - A host should begin regeneration before deprecation, must generate a successor when the preferred lifetime expires, and must replace old temporary addresses after moving to a different link. The research record locates this support at Sections 3.5 (Expiration of Temporary Addresses) and 3.6 (Regeneration of Temporary Addresses). Keep the evidence boundary at these traced claims. They support a review of address plans, interfaces, routes, peers, protocol roles, timers, middleboxes, and intended failure domains; they do not support conclusions outside the source’s stated conditions. ## What the source does not establish This RFC evidence supports only the named network-protocol decision; it does not select vendor settings, topology, capacity, or an acceptable failure mode. A correct source interpretation can still be inapplicable to a particular design. Confirm DNS, Active Directory authentication, PKI, time, routing policy, transport reachability, and monitoring, ownership, and change authority instead of treating documented behavior as a deployment guarantee. ## Applicability questions - For source statement 1 at Section 3.4 (Generating Temporary Addresses), step 3, which observable configuration, record, or test can confirm applicability here? - For source statement 2 at Section 3.4 (Generating Temporary Addresses), steps 1 and 4, which observable configuration, record, or test can confirm applicability here? - For source statement 3 at Sections 3.5 (Expiration of Temporary Addresses) and 3.6 (Regeneration of Temporary Addresses), which observable configuration, record, or test can confirm applicability here? - Within address plans, interfaces, routes, peers, protocol roles, timers, middleboxes, and intended failure domains, which versions, roles, and configuration states define the review population? - Could DNS, Active Directory authentication, PKI, time, routing policy, transport reachability, and monitoring invalidate the test, hide a failure, or change applicability? - Who owns the decision, and which observation requires stopping, escalation, or rollback? ## DSE recommendation: DSE recommends using the cited source as the evidence anchor for this decision. Anchor the review in the cited section and keep observation separate from interpretation. Record the source location, examined part of address plans, interfaces, routes, peers, protocol roles, timers, middleboxes, and intended failure domains, observed and expected states, owner, and reason for deviation. For an approved change, define prerequisites, a limited test path, success and stop conditions, monitoring, and rollback. Check DNS, Active Directory authentication, PKI, time, routing policy, transport reachability, and monitoring in design order. Protect credentials, keys, recovery material, personal data, and sensitive topology in evidence. ## Verification and evidence Keep the source locations Section 3.4 (Generating Temporary Addresses), step 3; Section 3.4 (Generating Temporary Addresses), steps 1 and 4; Sections 3.5 (Expiration of Temporary Addresses) and 3.6 (Regeneration of Temporary Addresses) adjacent to the sanitized artifacts used for comparison. Prefer configuration snapshots, route or neighbor state, packet captures, counters, topology records, and controlled failover results, with enough identity and timing data for an independent recheck. Preserve both successful and failed observations, along with approval and rollback evidence. Avoid uncontrolled production experiments. Assign an expiry or event-driven recheck so the conclusion is not treated as permanent. ## Official references - [RFC 8981 — Temporary Address Extensions for Stateless Address Autoconfiguration in IPv6](https://www.rfc-editor.org/rfc/rfc8981.html) — RFC Editor / Internet Engineering Task Force ## Primary reference - Name: RFC 8981 — Temporary Address Extensions for Stateless Address Autoconfiguration in IPv6 - Authority: www.rfc-editor.org - URL: https://www.rfc-editor.org/rfc/rfc8981.html - Source publication date: Not stated by the source ## Citation and use Preferred citation: “Rotate temporary IPv6 addresses within lifetime and regeneration bounds,” DSE Security, https://update.dsesecurity.com/updates/rotate-temporary-ipv6-addresses-within-lifetime-and-regeneration-bounds/ Publishing principles: https://update.dsesecurity.com/updates/dse-updates-editorial-methodology/ Usage and citation policy: https://update.dsesecurity.com/usage/ Copyright © 2026 Detection Systems & Engineering. All rights reserved.