{ "api_version": "1", "kind": "dse_post", "self": "https://update.dsesecurity.com/api/v1/posts/advertise-ospf-maximum-metrics-when-a-router-must-remain-non-transit/", "item": { "id": "https://update.dsesecurity.com/updates/advertise-ospf-maximum-metrics-when-a-router-must-remain-non-transit/", "slug": "advertise-ospf-maximum-metrics-when-a-router-must-remain-non-transit", "url": "https://update.dsesecurity.com/updates/advertise-ospf-maximum-metrics-when-a-router-must-remain-non-transit/", "alternate_urls": { "markdown": "https://update.dsesecurity.com/updates/advertise-ospf-maximum-metrics-when-a-router-must-remain-non-transit.md", "json": "https://update.dsesecurity.com/api/v1/posts/advertise-ospf-maximum-metrics-when-a-router-must-remain-non-transit/" }, "title": "Advertise OSPF maximum metrics when a router must remain non-transit", "summary": "Use RFC 6987 — OSPF Stub Router Advertisement 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:43+00:00", "modified_at": "2026-08-27T12:36:16+00:00", "reviewed_on": "2026-08-26", "reading_minutes": 3, "word_count": 555, "potentially_affected": "Teams, systems, services, or facilities within the stated scope of RFC 6987 — OSPF Stub Router Advertisement", "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 6987 — OSPF Stub Router Advertisement", "url": "https://www.rfc-editor.org/rfc/rfc6987.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: Advertise OSPF maximum metrics when a router must remain non-transit. Only the official source and traced locations below supply facts. Confirm applicability before acting.

\n

Source fact:

\n

The official RFC 6987 — OSPF Stub Router Advertisement from RFC Editor / Internet Engineering Task Force supports the following bounded statements:

\n\n

Only the traced statements above are asserted as source facts. Apply the review to address plans, interfaces, routes, peers, protocol roles, timers, middleboxes, and intended failure domains after confirming that the source and deployed context match.

\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. Begin by recording scope and current state before deciding whether a change is warranted. 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

Build a reproducible chain from Section 2 (Solutions); Section 3 (Maximum Link Metric); Section 4 (Deployment Considerations) to the observed environment. Useful domain evidence includes configuration snapshots, route or neighbor state, packet captures, counters, topology records, and controlled failover results; label every item with scope, timestamp, collector, and stable identifier.

\n

Retain the starting state, authorization, execution record, outcome, deviation, and final state as one review package. Move disruptive checks to an approved test path. Reopen the decision when versions, design, dependencies, ownership, or official guidance changes.

\n

Official references

\n", "content_text": "Frame this document as a source-led configuration and assurance check: Advertise OSPF maximum metrics when a router must remain non-transit. Only the official source and traced locations below supply facts. Confirm applicability before acting.\nSource fact:\nThe official RFC 6987 — OSPF Stub Router Advertisement from RFC Editor / Internet Engineering Task Force supports the following bounded statements:\n\nAn OSPF router that must remain reachable but avoid transit advertises MaxLinkMetric on every non-stub link in its router-LSA. The research record locates this support at Section 2 (Solutions).\nMaxLinkMetric is the 16-bit all-ones value 0xffff and signals that the advertised link should not carry transit traffic. The research record locates this support at Section 3 (Maximum Link Metric).\nUnlike clearing the OSPF R-bit, MaxLinkMetric can leave the router usable as transit when it is the only remaining path. The research record locates this support at Section 4 (Deployment Considerations).\n\nOnly the traced statements above are asserted as source facts. Apply the review to address plans, interfaces, routes, peers, protocol roles, timers, middleboxes, and intended failure domains after confirming that the source and deployed context match.\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 2 (Solutions), which observable configuration, record, or test can confirm applicability here?\nFor source statement 2 at Section 3 (Maximum Link Metric), which observable configuration, record, or test can confirm applicability here?\nFor source statement 3 at Section 4 (Deployment Considerations), 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. Begin by recording scope and current state before deciding whether a change is warranted. 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\nBuild a reproducible chain from Section 2 (Solutions); Section 3 (Maximum Link Metric); Section 4 (Deployment Considerations) to the observed environment. Useful domain evidence includes configuration snapshots, route or neighbor state, packet captures, counters, topology records, and controlled failover results; label every item with scope, timestamp, collector, and stable identifier.\nRetain the starting state, authorization, execution record, outcome, deviation, and final state as one review package. Move disruptive checks to an approved test path. Reopen the decision when versions, design, dependencies, ownership, or official guidance changes.\nOfficial references\n\nRFC 6987 — OSPF Stub Router Advertisement — RFC Editor / Internet Engineering Task Force", "content_markdown": "Frame this document as a source-led configuration and assurance check: Advertise OSPF maximum metrics when a router must remain non-transit. Only the official source and traced locations below supply facts. Confirm applicability before acting.\n\n## Source fact:\n\nThe official [RFC 6987 — OSPF Stub Router Advertisement](https://www.rfc-editor.org/rfc/rfc6987.html) from RFC Editor / Internet Engineering Task Force supports the following bounded statements:\n\n- An OSPF router that must remain reachable but avoid transit advertises MaxLinkMetric on every non-stub link in its router-LSA. The research record locates this support at Section 2 (Solutions).\n\n- MaxLinkMetric is the 16-bit all-ones value 0xffff and signals that the advertised link should not carry transit traffic. The research record locates this support at Section 3 (Maximum Link Metric).\n\n- Unlike clearing the OSPF R-bit, MaxLinkMetric can leave the router usable as transit when it is the only remaining path. The research record locates this support at Section 4 (Deployment Considerations).\n\nOnly the traced statements above are asserted as source facts. Apply the review to address plans, interfaces, routes, peers, protocol roles, timers, middleboxes, and intended failure domains after confirming that the source and deployed context match.\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 2 (Solutions), which observable configuration, record, or test can confirm applicability here?\n\n- For source statement 2 at Section 3 (Maximum Link Metric), which observable configuration, record, or test can confirm applicability here?\n\n- For source statement 3 at Section 4 (Deployment Considerations), 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. Begin by recording scope and current state before deciding whether a change is warranted. 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\nBuild a reproducible chain from Section 2 (Solutions); Section 3 (Maximum Link Metric); Section 4 (Deployment Considerations) to the observed environment. Useful domain evidence includes configuration snapshots, route or neighbor state, packet captures, counters, topology records, and controlled failover results; label every item with scope, timestamp, collector, and stable identifier.\n\nRetain the starting state, authorization, execution record, outcome, deviation, and final state as one review package. Move disruptive checks to an approved test path. Reopen the decision when versions, design, dependencies, ownership, or official guidance changes.\n\n## Official references\n\n- [RFC 6987 — OSPF Stub Router Advertisement](https://www.rfc-editor.org/rfc/rfc6987.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/advertise-ospf-maximum-metrics-when-a-router-must-remain-non-transit/", "url": "https://update.dsesecurity.com/updates/advertise-ospf-maximum-metrics-when-a-router-must-remain-non-transit/", "isPartOf": { "@id": "https://update.dsesecurity.com/#website" }, "lastReviewed": "2026-08-26" }, { "@type": "BreadcrumbList", "@id": "https://update.dsesecurity.com/updates/advertise-ospf-maximum-metrics-when-a-router-must-remain-non-transit/#breadcrumbs", "itemListElement": [ { "@type": "ListItem", "position": 1, "name": "DSE Updates", "item": "https://update.dsesecurity.com/" }, { "@type": "ListItem", "position": 2, "name": "Advertise OSPF maximum metrics when a router must remain non-transit", "item": "https://update.dsesecurity.com/updates/advertise-ospf-maximum-metrics-when-a-router-must-remain-non-transit/" } ] }, { "@type": [ "Article", "TechArticle" ], "@id": "https://update.dsesecurity.com/updates/advertise-ospf-maximum-metrics-when-a-router-must-remain-non-transit/#article", "identifier": "https://update.dsesecurity.com/updates/advertise-ospf-maximum-metrics-when-a-router-must-remain-non-transit/", "url": "https://update.dsesecurity.com/updates/advertise-ospf-maximum-metrics-when-a-router-must-remain-non-transit/", "headline": "Advertise OSPF maximum metrics when a router must remain non-transit", "description": "Use RFC 6987 — OSPF Stub Router Advertisement to review this narrow operational decision without extending the source beyond its stated scope.", "abstract": "Use RFC 6987 — OSPF Stub Router Advertisement 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: Advertise OSPF maximum metrics when a router must remain non-transit. Only the official source and traced locations below supply facts. Confirm applicability before acting.\nSource fact:\nThe official RFC 6987 — OSPF Stub Router Advertisement from RFC Editor / Internet Engineering Task Force supports the following bounded statements:\n\nAn OSPF router that must remain reachable but avoid transit advertises MaxLinkMetric on every non-stub link in its router-LSA. The research record locates this support at Section 2 (Solutions).\nMaxLinkMetric is the 16-bit all-ones value 0xffff and signals that the advertised link should not carry transit traffic. The research record locates this support at Section 3 (Maximum Link Metric).\nUnlike clearing the OSPF R-bit, MaxLinkMetric can leave the router usable as transit when it is the only remaining path. The research record locates this support at Section 4 (Deployment Considerations).\n\nOnly the traced statements above are asserted as source facts. Apply the review to address plans, interfaces, routes, peers, protocol roles, timers, middleboxes, and intended failure domains after confirming that the source and deployed context match.\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 2 (Solutions), which observable configuration, record, or test can confirm applicability here?\nFor source statement 2 at Section 3 (Maximum Link Metric), which observable configuration, record, or test can confirm applicability here?\nFor source statement 3 at Section 4 (Deployment Considerations), 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. Begin by recording scope and current state before deciding whether a change is warranted. 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\nBuild a reproducible chain from Section 2 (Solutions); Section 3 (Maximum Link Metric); Section 4 (Deployment Considerations) to the observed environment. Useful domain evidence includes configuration snapshots, route or neighbor state, packet captures, counters, topology records, and controlled failover results; label every item with scope, timestamp, collector, and stable identifier.\nRetain the starting state, authorization, execution record, outcome, deviation, and final state as one review package. Move disruptive checks to an approved test path. Reopen the decision when versions, design, dependencies, ownership, or official guidance changes.\nOfficial references\n\nRFC 6987 — OSPF Stub Router Advertisement — RFC Editor / Internet Engineering Task Force", "datePublished": "2026-08-27T12:16:43+00:00", "dateModified": "2026-08-27T12:36:16+00:00", "mainEntityOfPage": { "@id": "https://update.dsesecurity.com/updates/advertise-ospf-maximum-metrics-when-a-router-must-remain-non-transit/" }, "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/advertise-ospf-maximum-metrics-when-a-router-must-remain-non-transit/#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": "Advertise OSPF maximum metrics when a router must remain non-transit" }, "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": 555, "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 6987 — OSPF Stub Router Advertisement", "url": "https://www.rfc-editor.org/rfc/rfc6987.html" } } ] } }