{ "api_version": "1", "kind": "dse_post", "self": "https://update.dsesecurity.com/api/v1/posts/separate-ipv6-router-discovery-address-resolution-and-reachability/", "item": { "id": "https://update.dsesecurity.com/updates/separate-ipv6-router-discovery-address-resolution-and-reachability/", "slug": "separate-ipv6-router-discovery-address-resolution-and-reachability", "url": "https://update.dsesecurity.com/updates/separate-ipv6-router-discovery-address-resolution-and-reachability/", "alternate_urls": { "markdown": "https://update.dsesecurity.com/updates/separate-ipv6-router-discovery-address-resolution-and-reachability.md", "json": "https://update.dsesecurity.com/api/v1/posts/separate-ipv6-router-discovery-address-resolution-and-reachability/" }, "title": "Separate IPv6 router discovery, address resolution, and reachability", "summary": "Use RFC 4861 — Neighbor Discovery for IP version 6 (IPv6) to review this narrow operational decision without extending the source beyond its stated scope.", "format": { "slug": "briefing", "name": "Briefing" }, "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:10+00:00", "modified_at": "2026-08-27T12:53:57+00:00", "reviewed_on": "2026-08-26", "reading_minutes": 3, "word_count": 575, "potentially_affected": "Teams, systems, services, or facilities within the stated scope of RFC 4861 — Neighbor Discovery for IP version 6 (IPv6)", "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 4861 — Neighbor Discovery for IP version 6 (IPv6)", "url": "https://www.rfc-editor.org/rfc/rfc4861.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": "

Use this document to resolve one bounded operational decision: Separate IPv6 router discovery, address resolution, and reachability. Only the official source and traced locations below supply facts. Confirm applicability before acting.

\n

Source fact:

\n

The official RFC 4861 — Neighbor Discovery for IP version 6 (IPv6) from RFC Editor / Internet Engineering Task Force supports the following bounded statements:

\n\n

The source support ends with the statements listed above. Use them to examine address plans, interfaces, routes, peers, protocol roles, timers, middleboxes, and intended failure domains in the applicable environment, not to imply a wider guarantee.

\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. 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.

\n

Applicability questions

\n\n

DSE recommendation:

\n

DSE recommends using the cited source as the evidence anchor for this decision. Make the source, asset scope, owner, and expected outcome explicit in the review record. 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

Do not move from citation to production in one step. Pilot the decision where practical, observe agreed signals, retain a reversal point, and verify DNS, Active Directory authentication, PKI, time, routing policy, transport reachability, and monitoring. Handle credentials, keys, recovery data, and personal information through approved secure channels.

\n

Verification and evidence

\n

A reviewer should be able to retrace the decision from Section 6.3.4 (Processing Received Router Advertisements); Section 7.2.2 (Sending Neighbor Solicitations); Section 7.3.1 (Reachability Confirmation) through configuration snapshots, route or neighbor state, packet captures, counters, topology records, and controlled failover results. Record what was collected, where, when, by whom, and which system or role it represents.

\n

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.

\n

Official references

\n", "content_text": "Use this document to resolve one bounded operational decision: Separate IPv6 router discovery, address resolution, and reachability. Only the official source and traced locations below supply facts. Confirm applicability before acting.\nSource fact:\nThe official RFC 4861 — Neighbor Discovery for IP version 6 (IPv6) from RFC Editor / Internet Engineering Task Force supports the following bounded statements:\n\nA valid Router Advertisement adds, refreshes, or immediately expires its source in the Default Router List according to the advertised Router Lifetime. The research record locates this support at Section 6.3.4 (Processing Received Router Advertisements).\nAddress resolution creates an INCOMPLETE neighbor-cache entry and sends a Neighbor Solicitation to the target’s solicited-node multicast address while queueing at least one packet. The research record locates this support at Section 7.2.2 (Sending Neighbor Solicitations).\nOnly upper-layer forward progress or a solicited Neighbor Advertisement confirms forward-path reachability; unsolicited advertisements and Router Advertisements do not. The research record locates this support at Section 7.3.1 (Reachability Confirmation).\n\nThe source support ends with the statements listed above. Use them to examine address plans, interfaces, routes, peers, protocol roles, timers, middleboxes, and intended failure domains in the applicable environment, not to imply a wider guarantee.\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. 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.\nApplicability questions\n\nFor source statement 1 at Section 6.3.4 (Processing Received Router Advertisements), which observable configuration, record, or test can confirm applicability here?\nFor source statement 2 at Section 7.2.2 (Sending Neighbor Solicitations), which observable configuration, record, or test can confirm applicability here?\nFor source statement 3 at Section 7.3.1 (Reachability Confirmation), 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. Make the source, asset scope, owner, and expected outcome explicit in the review record. 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.\nDo not move from citation to production in one step. Pilot the decision where practical, observe agreed signals, retain a reversal point, and verify DNS, Active Directory authentication, PKI, time, routing policy, transport reachability, and monitoring. Handle credentials, keys, recovery data, and personal information through approved secure channels.\nVerification and evidence\nA reviewer should be able to retrace the decision from Section 6.3.4 (Processing Received Router Advertisements); Section 7.2.2 (Sending Neighbor Solicitations); Section 7.3.1 (Reachability Confirmation) through configuration snapshots, route or neighbor state, packet captures, counters, topology records, and controlled failover results. Record what was collected, where, when, by whom, and which system or role it represents.\nPreserve 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.\nOfficial references\n\nRFC 4861 — Neighbor Discovery for IP version 6 (IPv6) — RFC Editor / Internet Engineering Task Force", "content_markdown": "Use this document to resolve one bounded operational decision: Separate IPv6 router discovery, address resolution, and reachability. Only the official source and traced locations below supply facts. Confirm applicability before acting.\n\n## Source fact:\n\nThe official [RFC 4861 — Neighbor Discovery for IP version 6 (IPv6)](https://www.rfc-editor.org/rfc/rfc4861.html) from RFC Editor / Internet Engineering Task Force supports the following bounded statements:\n\n- A valid Router Advertisement adds, refreshes, or immediately expires its source in the Default Router List according to the advertised Router Lifetime. The research record locates this support at Section 6.3.4 (Processing Received Router Advertisements).\n\n- Address resolution creates an INCOMPLETE neighbor-cache entry and sends a Neighbor Solicitation to the target’s solicited-node multicast address while queueing at least one packet. The research record locates this support at Section 7.2.2 (Sending Neighbor Solicitations).\n\n- Only upper-layer forward progress or a solicited Neighbor Advertisement confirms forward-path reachability; unsolicited advertisements and Router Advertisements do not. The research record locates this support at Section 7.3.1 (Reachability Confirmation).\n\nThe source support ends with the statements listed above. Use them to examine address plans, interfaces, routes, peers, protocol roles, timers, middleboxes, and intended failure domains in the applicable environment, not to imply a wider guarantee.\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. 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.\n\n## Applicability questions\n\n- For source statement 1 at Section 6.3.4 (Processing Received Router Advertisements), which observable configuration, record, or test can confirm applicability here?\n\n- For source statement 2 at Section 7.2.2 (Sending Neighbor Solicitations), which observable configuration, record, or test can confirm applicability here?\n\n- For source statement 3 at Section 7.3.1 (Reachability Confirmation), 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. Make the source, asset scope, owner, and expected outcome explicit in the review record. 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\nDo not move from citation to production in one step. Pilot the decision where practical, observe agreed signals, retain a reversal point, and verify DNS, Active Directory authentication, PKI, time, routing policy, transport reachability, and monitoring. Handle credentials, keys, recovery data, and personal information through approved secure channels.\n\n## Verification and evidence\n\nA reviewer should be able to retrace the decision from Section 6.3.4 (Processing Received Router Advertisements); Section 7.2.2 (Sending Neighbor Solicitations); Section 7.3.1 (Reachability Confirmation) through configuration snapshots, route or neighbor state, packet captures, counters, topology records, and controlled failover results. Record what was collected, where, when, by whom, and which system or role it represents.\n\nPreserve 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.\n\n## Official references\n\n- [RFC 4861 — Neighbor Discovery for IP version 6 (IPv6)](https://www.rfc-editor.org/rfc/rfc4861.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/separate-ipv6-router-discovery-address-resolution-and-reachability/", "url": "https://update.dsesecurity.com/updates/separate-ipv6-router-discovery-address-resolution-and-reachability/", "isPartOf": { "@id": "https://update.dsesecurity.com/#website" }, "lastReviewed": "2026-08-26" }, { "@type": "BreadcrumbList", "@id": "https://update.dsesecurity.com/updates/separate-ipv6-router-discovery-address-resolution-and-reachability/#breadcrumbs", "itemListElement": [ { "@type": "ListItem", "position": 1, "name": "DSE Updates", "item": "https://update.dsesecurity.com/" }, { "@type": "ListItem", "position": 2, "name": "Separate IPv6 router discovery, address resolution, and reachability", "item": "https://update.dsesecurity.com/updates/separate-ipv6-router-discovery-address-resolution-and-reachability/" } ] }, { "@type": [ "Article", "TechArticle" ], "@id": "https://update.dsesecurity.com/updates/separate-ipv6-router-discovery-address-resolution-and-reachability/#article", "identifier": "https://update.dsesecurity.com/updates/separate-ipv6-router-discovery-address-resolution-and-reachability/", "url": "https://update.dsesecurity.com/updates/separate-ipv6-router-discovery-address-resolution-and-reachability/", "headline": "Separate IPv6 router discovery, address resolution, and reachability", "description": "Use RFC 4861 — Neighbor Discovery for IP version 6 (IPv6) to review this narrow operational decision without extending the source beyond its stated scope.", "abstract": "Use RFC 4861 — Neighbor Discovery for IP version 6 (IPv6) to review this narrow operational decision without extending the source beyond its stated scope.", "articleBody": "Use this document to resolve one bounded operational decision: Separate IPv6 router discovery, address resolution, and reachability. Only the official source and traced locations below supply facts. Confirm applicability before acting.\nSource fact:\nThe official RFC 4861 — Neighbor Discovery for IP version 6 (IPv6) from RFC Editor / Internet Engineering Task Force supports the following bounded statements:\n\nA valid Router Advertisement adds, refreshes, or immediately expires its source in the Default Router List according to the advertised Router Lifetime. The research record locates this support at Section 6.3.4 (Processing Received Router Advertisements).\nAddress resolution creates an INCOMPLETE neighbor-cache entry and sends a Neighbor Solicitation to the target’s solicited-node multicast address while queueing at least one packet. The research record locates this support at Section 7.2.2 (Sending Neighbor Solicitations).\nOnly upper-layer forward progress or a solicited Neighbor Advertisement confirms forward-path reachability; unsolicited advertisements and Router Advertisements do not. The research record locates this support at Section 7.3.1 (Reachability Confirmation).\n\nThe source support ends with the statements listed above. Use them to examine address plans, interfaces, routes, peers, protocol roles, timers, middleboxes, and intended failure domains in the applicable environment, not to imply a wider guarantee.\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. 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.\nApplicability questions\n\nFor source statement 1 at Section 6.3.4 (Processing Received Router Advertisements), which observable configuration, record, or test can confirm applicability here?\nFor source statement 2 at Section 7.2.2 (Sending Neighbor Solicitations), which observable configuration, record, or test can confirm applicability here?\nFor source statement 3 at Section 7.3.1 (Reachability Confirmation), 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. Make the source, asset scope, owner, and expected outcome explicit in the review record. 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.\nDo not move from citation to production in one step. Pilot the decision where practical, observe agreed signals, retain a reversal point, and verify DNS, Active Directory authentication, PKI, time, routing policy, transport reachability, and monitoring. Handle credentials, keys, recovery data, and personal information through approved secure channels.\nVerification and evidence\nA reviewer should be able to retrace the decision from Section 6.3.4 (Processing Received Router Advertisements); Section 7.2.2 (Sending Neighbor Solicitations); Section 7.3.1 (Reachability Confirmation) through configuration snapshots, route or neighbor state, packet captures, counters, topology records, and controlled failover results. Record what was collected, where, when, by whom, and which system or role it represents.\nPreserve 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.\nOfficial references\n\nRFC 4861 — Neighbor Discovery for IP version 6 (IPv6) — RFC Editor / Internet Engineering Task Force", "datePublished": "2026-08-27T12:16:10+00:00", "dateModified": "2026-08-27T12:53:57+00:00", "mainEntityOfPage": { "@id": "https://update.dsesecurity.com/updates/separate-ipv6-router-discovery-address-resolution-and-reachability/" }, "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/separate-ipv6-router-discovery-address-resolution-and-reachability/#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": "Separate IPv6 router discovery, address resolution, and reachability" }, "articleSection": [ "IT", "Networks & Infrastructure" ], "keywords": [ "IT", "Networks & Infrastructure", "Briefing", "Advisory priority" ], "genre": "Briefing", "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": 575, "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 4861 — Neighbor Discovery for IP version 6 (IPv6)", "url": "https://www.rfc-editor.org/rfc/rfc4861.html" } } ] } }