{ "api_version": "1", "kind": "dse_post", "self": "https://update.dsesecurity.com/api/v1/posts/generate-and-route-ulas-without-leaking-them-as-global-ipv6-space/", "item": { "id": "https://update.dsesecurity.com/updates/generate-and-route-ulas-without-leaking-them-as-global-ipv6-space/", "slug": "generate-and-route-ulas-without-leaking-them-as-global-ipv6-space", "url": "https://update.dsesecurity.com/updates/generate-and-route-ulas-without-leaking-them-as-global-ipv6-space/", "alternate_urls": { "markdown": "https://update.dsesecurity.com/updates/generate-and-route-ulas-without-leaking-them-as-global-ipv6-space.md", "json": "https://update.dsesecurity.com/api/v1/posts/generate-and-route-ulas-without-leaking-them-as-global-ipv6-space/" }, "title": "Generate and route ULAs without leaking them as global IPv6 space", "summary": "Use RFC 4193 — Unique Local IPv6 Unicast Addresses to review this narrow operational decision without extending the source beyond its stated scope.", "format": { "slug": "explainer", "name": "Explainer" }, "priority": { "slug": "advisory", "name": "Advisory" }, "featured": false, "image": { "theme": "network-infrastructure", "label": "Networks & infrastructure", "alt": "Resilient network core with engineered blue and gold data paths.", "card_url": "https://update.dsesecurity.com/assets/editorial/network-infrastructure-card.webp?v=1.8.20", "hero_url": "https://update.dsesecurity.com/assets/editorial/network-infrastructure-hero.webp?v=1.8.20", "social_url": "https://update.dsesecurity.com/assets/editorial/network-infrastructure-social-v2.jpg?v=1.8.20", "width": 2400, "height": 1350 }, "topics": [ { "slug": "it", "name": "IT", "url": "https://update.dsesecurity.com/topic/it/" }, { "slug": "networks-infrastructure", "name": "Networks & Infrastructure", "url": "https://update.dsesecurity.com/topic/networks-infrastructure/" } ], "author": { "name": "DSE Security Editorial Team", "url": "https://update.dsesecurity.com/#editorial-team", "type": "Organization" }, "publisher": { "name": "Detection Systems & Engineering", "url": "https://dsesecurity.com/" }, "published_at": "2026-08-27T12:16:28+00:00", "modified_at": "2026-08-27T12:36:16+00:00", "reviewed_on": "2026-08-26", "reading_minutes": 3, "word_count": 570, "potentially_affected": "Teams, systems, services, or facilities within the stated scope of RFC 4193 — Unique Local IPv6 Unicast Addresses", "dse_recommendation": "Compare the observed state with the cited official source, document applicability and exceptions, and test any approved change with rollback safeguards.", "primary_source": { "name": "RFC 4193 — Unique Local IPv6 Unicast Addresses", "url": "https://www.rfc-editor.org/rfc/rfc4193.html", "published_on": null, "authority": "www.rfc-editor.org" }, "publishing_principles": "https://update.dsesecurity.com/updates/dse-updates-editorial-methodology/", "usage_info": "https://update.dsesecurity.com/usage/", "copyright_notice": "Copyright © 2026 Detection Systems & Engineering. All rights reserved.", "content_html": "

Frame this document as a source-led configuration and assurance check: Generate and route ULAs without leaking them as global IPv6 space. Only the official source and traced locations below supply facts. Confirm applicability before acting.

\n

Source fact:

\n

The official RFC 4193 — Unique Local IPv6 Unicast Addresses from RFC Editor / Internet Engineering Task Force supports the following bounded statements:

\n\n

Do not import neighboring assumptions into the source record. The supported task is a scoped comparison involving address plans, interfaces, routes, peers, protocol roles, timers, middleboxes, and intended failure domains and the conditions the source actually describes.

\n

What the source does not establish

\n

This RFC evidence supports only the named network-protocol decision; it does not select vendor settings, topology, capacity, or an acceptable failure mode. Do not read the source as proof of implementation or permission to change production. Its guidance remains conditional on DNS, Active Directory authentication, PKI, time, routing policy, transport reachability, and monitoring and the environment’s recorded constraints.

\n

Applicability questions

\n\n

DSE recommendation:

\n

DSE recommends using the cited source as the evidence anchor for this decision. Use a two-person review for the source interpretation and the resulting operational decision. 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.

\n

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.

\n

Verification and evidence

\n

Tie each conclusion back to Section 3.1 (Format); Section 3.2.1 (Locally Assigned Global IDs); Section 4.1 (Routing) and to observable material such as configuration snapshots, route or neighbor state, packet captures, counters, topology records, and controlled failover results. Preserve provenance and stable identifiers without copying secrets into the evidence set.

\n

Record the decision even when no change is made, including uncertainty and the next trigger. Use safe testing conditions for disruptive work, preserve rollback proof, and revisit the conclusion after relevant platform, dependency, vendor, or ownership changes.

\n

Official references

\n", "content_text": "Frame this document as a source-led configuration and assurance check: Generate and route ULAs without leaking them as global IPv6 space. Only the official source and traced locations below supply facts. Confirm applicability before acting.\nSource fact:\nThe official RFC 4193 — Unique Local IPv6 Unicast Addresses from RFC Editor / Internet Engineering Task Force supports the following bounded statements:\n\nA unique local IPv6 prefix uses FC00::/7, a local-assignment bit, a 40-bit Global ID, a 16-bit subnet ID, and a 64-bit interface ID. The research record locates this support at Section 3.1 (Format).\nA locally assigned Global ID must be generated with a pseudo-random algorithm to make independent /48 prefix collisions highly unlikely. The research record locates this support at Section 3.2.1 (Locally Assigned Global IDs).\nExterior routing should ignore and not advertise FC00::/7 by default, while site borders should reject local-address packets unless explicitly routed for a specific /48 or longer prefix. The research record locates this support at Section 4.1 (Routing).\n\nDo not import neighboring assumptions into the source record. The supported task is a scoped comparison involving address plans, interfaces, routes, peers, protocol roles, timers, middleboxes, and intended failure domains and the conditions the source actually describes.\nWhat the source does not establish\nThis RFC evidence supports only the named network-protocol decision; it does not select vendor settings, topology, capacity, or an acceptable failure mode. Do not read the source as proof of implementation or permission to change production. Its guidance remains conditional on DNS, Active Directory authentication, PKI, time, routing policy, transport reachability, and monitoring and the environment’s recorded constraints.\nApplicability questions\n\nFor source statement 1 at Section 3.1 (Format), which observable configuration, record, or test can confirm applicability here?\nFor source statement 2 at Section 3.2.1 (Locally Assigned Global IDs), which observable configuration, record, or test can confirm applicability here?\nFor source statement 3 at Section 4.1 (Routing), which observable configuration, record, or test can confirm applicability here?\nWithin address plans, interfaces, routes, peers, protocol roles, timers, middleboxes, and intended failure domains, which versions, roles, and configuration states define the review population?\nCould DNS, Active Directory authentication, PKI, time, routing policy, transport reachability, and monitoring invalidate the test, hide a failure, or change applicability?\nWho owns the decision, and which observation requires stopping, escalation, or rollback?\n\nDSE recommendation:\nDSE recommends using the cited source as the evidence anchor for this decision. Use a two-person review for the source interpretation and the resulting operational decision. 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.\nFor 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.\nVerification and evidence\nTie each conclusion back to Section 3.1 (Format); Section 3.2.1 (Locally Assigned Global IDs); Section 4.1 (Routing) and to observable material such as configuration snapshots, route or neighbor state, packet captures, counters, topology records, and controlled failover results. Preserve provenance and stable identifiers without copying secrets into the evidence set.\nRecord the decision even when no change is made, including uncertainty and the next trigger. Use safe testing conditions for disruptive work, preserve rollback proof, and revisit the conclusion after relevant platform, dependency, vendor, or ownership changes.\nOfficial references\n\nRFC 4193 — Unique Local IPv6 Unicast Addresses — RFC Editor / Internet Engineering Task Force", "content_markdown": "Frame this document as a source-led configuration and assurance check: Generate and route ULAs without leaking them as global IPv6 space. Only the official source and traced locations below supply facts. Confirm applicability before acting.\n\n## Source fact:\n\nThe official [RFC 4193 — Unique Local IPv6 Unicast Addresses](https://www.rfc-editor.org/rfc/rfc4193.html) from RFC Editor / Internet Engineering Task Force supports the following bounded statements:\n\n- A unique local IPv6 prefix uses FC00::/7, a local-assignment bit, a 40-bit Global ID, a 16-bit subnet ID, and a 64-bit interface ID. The research record locates this support at Section 3.1 (Format).\n\n- A locally assigned Global ID must be generated with a pseudo-random algorithm to make independent /48 prefix collisions highly unlikely. The research record locates this support at Section 3.2.1 (Locally Assigned Global IDs).\n\n- Exterior routing should ignore and not advertise FC00::/7 by default, while site borders should reject local-address packets unless explicitly routed for a specific /48 or longer prefix. The research record locates this support at Section 4.1 (Routing).\n\nDo not import neighboring assumptions into the source record. The supported task is a scoped comparison involving address plans, interfaces, routes, peers, protocol roles, timers, middleboxes, and intended failure domains and the conditions the source actually describes.\n\n## What the source does not establish\n\nThis RFC evidence supports only the named network-protocol decision; it does not select vendor settings, topology, capacity, or an acceptable failure mode. Do not read the source as proof of implementation or permission to change production. Its guidance remains conditional on DNS, Active Directory authentication, PKI, time, routing policy, transport reachability, and monitoring and the environment’s recorded constraints.\n\n## Applicability questions\n\n- For source statement 1 at Section 3.1 (Format), which observable configuration, record, or test can confirm applicability here?\n\n- For source statement 2 at Section 3.2.1 (Locally Assigned Global IDs), which observable configuration, record, or test can confirm applicability here?\n\n- For source statement 3 at Section 4.1 (Routing), which observable configuration, record, or test can confirm applicability here?\n\n- Within address plans, interfaces, routes, peers, protocol roles, timers, middleboxes, and intended failure domains, which versions, roles, and configuration states define the review population?\n\n- Could DNS, Active Directory authentication, PKI, time, routing policy, transport reachability, and monitoring invalidate the test, hide a failure, or change applicability?\n\n- Who owns the decision, and which observation requires stopping, escalation, or rollback?\n\n## DSE recommendation:\n\nDSE recommends using the cited source as the evidence anchor for this decision. Use a two-person review for the source interpretation and the resulting operational decision. 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.\n\nFor 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.\n\n## Verification and evidence\n\nTie each conclusion back to Section 3.1 (Format); Section 3.2.1 (Locally Assigned Global IDs); Section 4.1 (Routing) and to observable material such as configuration snapshots, route or neighbor state, packet captures, counters, topology records, and controlled failover results. Preserve provenance and stable identifiers without copying secrets into the evidence set.\n\nRecord the decision even when no change is made, including uncertainty and the next trigger. Use safe testing conditions for disruptive work, preserve rollback proof, and revisit the conclusion after relevant platform, dependency, vendor, or ownership changes.\n\n## Official references\n\n- [RFC 4193 — Unique Local IPv6 Unicast Addresses](https://www.rfc-editor.org/rfc/rfc4193.html) — RFC Editor / Internet Engineering Task Force" }, "json_ld": { "@context": "https://schema.org", "@graph": [ { "@type": "Organization", "@id": "https://dsesecurity.com/#organization", "name": "Detection Systems & Engineering", "alternateName": "DSE Security", "url": "https://dsesecurity.com/", "logo": { "@type": "ImageObject", "url": "https://update.dsesecurity.com/assets/dse-logo-20260812.png?v=1.8.20" } }, { "@type": "Organization", "@id": "https://update.dsesecurity.com/#editorial-team", "name": "DSE Security Editorial Team", "url": "https://update.dsesecurity.com/", "parentOrganization": { "@id": "https://dsesecurity.com/#organization" } }, { "@type": "WebSite", "@id": "https://update.dsesecurity.com/#website", "name": "DSE Updates", "alternateName": "DSE Security Knowledge Hub", "url": "https://update.dsesecurity.com/", "inLanguage": "en-US", "publisher": { "@id": "https://dsesecurity.com/#organization" }, "potentialAction": { "@type": "SearchAction", "target": { "@type": "EntryPoint", "urlTemplate": "https://update.dsesecurity.com/?q={search_term_string}" }, "query-input": "required name=search_term_string" } }, { "@type": "WebPage", "@id": "https://update.dsesecurity.com/updates/generate-and-route-ulas-without-leaking-them-as-global-ipv6-space/", "url": "https://update.dsesecurity.com/updates/generate-and-route-ulas-without-leaking-them-as-global-ipv6-space/", "isPartOf": { "@id": "https://update.dsesecurity.com/#website" }, "lastReviewed": "2026-08-26" }, { "@type": "BreadcrumbList", "@id": "https://update.dsesecurity.com/updates/generate-and-route-ulas-without-leaking-them-as-global-ipv6-space/#breadcrumbs", "itemListElement": [ { "@type": "ListItem", "position": 1, "name": "DSE Updates", "item": "https://update.dsesecurity.com/" }, { "@type": "ListItem", "position": 2, "name": "Generate and route ULAs without leaking them as global IPv6 space", "item": "https://update.dsesecurity.com/updates/generate-and-route-ulas-without-leaking-them-as-global-ipv6-space/" } ] }, { "@type": [ "Article", "TechArticle" ], "@id": "https://update.dsesecurity.com/updates/generate-and-route-ulas-without-leaking-them-as-global-ipv6-space/#article", "identifier": "https://update.dsesecurity.com/updates/generate-and-route-ulas-without-leaking-them-as-global-ipv6-space/", "url": "https://update.dsesecurity.com/updates/generate-and-route-ulas-without-leaking-them-as-global-ipv6-space/", "headline": "Generate and route ULAs without leaking them as global IPv6 space", "description": "Use RFC 4193 — Unique Local IPv6 Unicast Addresses to review this narrow operational decision without extending the source beyond its stated scope.", "abstract": "Use RFC 4193 — Unique Local IPv6 Unicast Addresses to review this narrow operational decision without extending the source beyond its stated scope.", "articleBody": "Frame this document as a source-led configuration and assurance check: Generate and route ULAs without leaking them as global IPv6 space. Only the official source and traced locations below supply facts. Confirm applicability before acting.\nSource fact:\nThe official RFC 4193 — Unique Local IPv6 Unicast Addresses from RFC Editor / Internet Engineering Task Force supports the following bounded statements:\n\nA unique local IPv6 prefix uses FC00::/7, a local-assignment bit, a 40-bit Global ID, a 16-bit subnet ID, and a 64-bit interface ID. The research record locates this support at Section 3.1 (Format).\nA locally assigned Global ID must be generated with a pseudo-random algorithm to make independent /48 prefix collisions highly unlikely. The research record locates this support at Section 3.2.1 (Locally Assigned Global IDs).\nExterior routing should ignore and not advertise FC00::/7 by default, while site borders should reject local-address packets unless explicitly routed for a specific /48 or longer prefix. The research record locates this support at Section 4.1 (Routing).\n\nDo not import neighboring assumptions into the source record. The supported task is a scoped comparison involving address plans, interfaces, routes, peers, protocol roles, timers, middleboxes, and intended failure domains and the conditions the source actually describes.\nWhat the source does not establish\nThis RFC evidence supports only the named network-protocol decision; it does not select vendor settings, topology, capacity, or an acceptable failure mode. Do not read the source as proof of implementation or permission to change production. Its guidance remains conditional on DNS, Active Directory authentication, PKI, time, routing policy, transport reachability, and monitoring and the environment’s recorded constraints.\nApplicability questions\n\nFor source statement 1 at Section 3.1 (Format), which observable configuration, record, or test can confirm applicability here?\nFor source statement 2 at Section 3.2.1 (Locally Assigned Global IDs), which observable configuration, record, or test can confirm applicability here?\nFor source statement 3 at Section 4.1 (Routing), which observable configuration, record, or test can confirm applicability here?\nWithin address plans, interfaces, routes, peers, protocol roles, timers, middleboxes, and intended failure domains, which versions, roles, and configuration states define the review population?\nCould DNS, Active Directory authentication, PKI, time, routing policy, transport reachability, and monitoring invalidate the test, hide a failure, or change applicability?\nWho owns the decision, and which observation requires stopping, escalation, or rollback?\n\nDSE recommendation:\nDSE recommends using the cited source as the evidence anchor for this decision. Use a two-person review for the source interpretation and the resulting operational decision. 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.\nFor 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.\nVerification and evidence\nTie each conclusion back to Section 3.1 (Format); Section 3.2.1 (Locally Assigned Global IDs); Section 4.1 (Routing) and to observable material such as configuration snapshots, route or neighbor state, packet captures, counters, topology records, and controlled failover results. Preserve provenance and stable identifiers without copying secrets into the evidence set.\nRecord the decision even when no change is made, including uncertainty and the next trigger. Use safe testing conditions for disruptive work, preserve rollback proof, and revisit the conclusion after relevant platform, dependency, vendor, or ownership changes.\nOfficial references\n\nRFC 4193 — Unique Local IPv6 Unicast Addresses — RFC Editor / Internet Engineering Task Force", "datePublished": "2026-08-27T12:16:28+00:00", "dateModified": "2026-08-27T12:36:16+00:00", "mainEntityOfPage": { "@id": "https://update.dsesecurity.com/updates/generate-and-route-ulas-without-leaking-them-as-global-ipv6-space/" }, "inLanguage": "en-US", "isAccessibleForFree": true, "author": { "@type": "Organization", "name": "DSE Security Editorial Team", "url": "https://update.dsesecurity.com/#editorial-team" }, "publisher": { "@id": "https://dsesecurity.com/#organization" }, "image": { "@type": "ImageObject", "@id": "https://update.dsesecurity.com/updates/generate-and-route-ulas-without-leaking-them-as-global-ipv6-space/#primaryimage", "url": "https://update.dsesecurity.com/assets/editorial/network-infrastructure-social-v2.jpg?v=1.8.20", "contentUrl": "https://update.dsesecurity.com/assets/editorial/network-infrastructure-social-v2.jpg?v=1.8.20", "width": 1200, "height": 630, "caption": "Generate and route ULAs without leaking them as global IPv6 space" }, "articleSection": [ "IT", "Networks & Infrastructure" ], "keywords": [ "IT", "Networks & Infrastructure", "Explainer", "Advisory priority" ], "genre": "Explainer", "about": [ { "@type": "Thing", "name": "IT", "url": "https://update.dsesecurity.com/topic/it/" }, { "@type": "Thing", "name": "Networks & Infrastructure", "url": "https://update.dsesecurity.com/topic/networks-infrastructure/" } ], "wordCount": 570, "timeRequired": "PT3M", "publishingPrinciples": "https://update.dsesecurity.com/updates/dse-updates-editorial-methodology/", "usageInfo": "https://update.dsesecurity.com/usage/", "copyrightHolder": { "@id": "https://dsesecurity.com/#organization" }, "copyrightNotice": "Copyright © 2026 Detection Systems & Engineering. All rights reserved.", "citation": { "@type": "CreativeWork", "name": "RFC 4193 — Unique Local IPv6 Unicast Addresses", "url": "https://www.rfc-editor.org/rfc/rfc4193.html" } } ] } }