{
    "api_version": "1",
    "kind": "dse_post",
    "self": "https://update.dsesecurity.com/api/v1/posts/prevent-route-reflector-loops-with-cluster-and-originator-attributes/",
    "item": {
        "id": "https://update.dsesecurity.com/updates/prevent-route-reflector-loops-with-cluster-and-originator-attributes/",
        "slug": "prevent-route-reflector-loops-with-cluster-and-originator-attributes",
        "url": "https://update.dsesecurity.com/updates/prevent-route-reflector-loops-with-cluster-and-originator-attributes/",
        "alternate_urls": {
            "markdown": "https://update.dsesecurity.com/updates/prevent-route-reflector-loops-with-cluster-and-originator-attributes.md",
            "json": "https://update.dsesecurity.com/api/v1/posts/prevent-route-reflector-loops-with-cluster-and-originator-attributes/"
        },
        "title": "Prevent route-reflector loops with cluster and originator attributes",
        "summary": "Use RFC 4456 — BGP Route Reflection: An Alternative to Full Mesh Internal BGP (IBGP) 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:18+00:00",
        "modified_at": "2026-08-27T12:53:57+00:00",
        "reviewed_on": "2026-08-26",
        "reading_minutes": 3,
        "word_count": 603,
        "potentially_affected": "Teams, systems, services, or facilities within the stated scope of RFC 4456 — BGP Route Reflection: An Alternative to Full Mesh Internal BGP (IBGP)",
        "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 4456 — BGP Route Reflection: An Alternative to Full Mesh Internal BGP (IBGP)",
            "url": "https://www.rfc-editor.org/rfc/rfc4456.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": "<p>Frame this document as a source-led configuration and assurance check: Prevent route-reflector loops with cluster and originator attributes. Only the official source and traced locations below supply facts. Confirm applicability before acting.</p>\n<h2>Source fact:</h2>\n<p>The official <a href=\"https://www.rfc-editor.org/rfc/rfc4456.html\" target=\"_blank\" rel=\"noopener noreferrer\">RFC 4456 — BGP Route Reflection: An Alternative to Full Mesh Internal BGP (IBGP)</a> from RFC Editor / Internet Engineering Task Force supports the following bounded statements:</p>\n<ul>\n<li>A route reflector creates ORIGINATOR_ID from the original speaker&#8217;s BGP Identifier, and a router should ignore a route whose ORIGINATOR_ID equals its own identifier. The research record locates this support at <strong>Section 8 (Avoiding Routing Information Loops), ORIGINATOR_ID</strong>.</li>\n<li>Each reflector must prepend its local cluster ID to CLUSTER_LIST and should ignore an advertisement whose list already contains that local ID. The research record locates this support at <strong>Section 8 (Avoiding Routing Information Loops), CLUSTER_LIST</strong>.</li>\n<li>Route selection treats ORIGINATOR_ID as the advertising speaker&#8217;s identifier and should prefer the shorter CLUSTER_LIST before the next tie-break step. The research record locates this support at <strong>Section 9 (Impact on Route Selection)</strong>.</li>\n</ul>\n<p>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.</p>\n<h2>What the source does not establish</h2>\n<p>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.</p>\n<h2>Applicability questions</h2>\n<ul>\n<li>For source statement 1 at <strong>Section 8 (Avoiding Routing Information Loops), ORIGINATOR_ID</strong>, which observable configuration, record, or test can confirm applicability here?</li>\n<li>For source statement 2 at <strong>Section 8 (Avoiding Routing Information Loops), CLUSTER_LIST</strong>, which observable configuration, record, or test can confirm applicability here?</li>\n<li>For source statement 3 at <strong>Section 9 (Impact on Route Selection)</strong>, which observable configuration, record, or test can confirm applicability here?</li>\n<li>Within address plans, interfaces, routes, peers, protocol roles, timers, middleboxes, and intended failure domains, which versions, roles, and configuration states define the review population?</li>\n<li>Could DNS, Active Directory authentication, PKI, time, routing policy, transport reachability, and monitoring invalidate the test, hide a failure, or change applicability?</li>\n<li>Who owns the decision, and which observation requires stopping, escalation, or rollback?</li>\n</ul>\n<h2>DSE recommendation:</h2>\n<p>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.</p>\n<p>If the review warrants change, use a bounded implementation with prerequisites, test population, monitoring, abort criteria, and a rehearsed reversal. Sequence checks for DNS, Active Directory authentication, PKI, time, routing policy, transport reachability, and monitoring and sanitize protected material before retention.</p>\n<h2>Verification and evidence</h2>\n<p>Build a reproducible chain from <strong>Section 8 (Avoiding Routing Information Loops), ORIGINATOR_ID</strong>; <strong>Section 8 (Avoiding Routing Information Loops), CLUSTER_LIST</strong>; <strong>Section 9 (Impact on Route Selection)</strong> 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.</p>\n<p>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.</p>\n<h2>Official references</h2>\n<ul>\n<li><a href=\"https://www.rfc-editor.org/rfc/rfc4456.html\" target=\"_blank\" rel=\"noopener noreferrer\">RFC 4456 — BGP Route Reflection: An Alternative to Full Mesh Internal BGP (IBGP)</a> — RFC Editor / Internet Engineering Task Force</li>\n</ul>",
        "content_text": "Frame this document as a source-led configuration and assurance check: Prevent route-reflector loops with cluster and originator attributes. Only the official source and traced locations below supply facts. Confirm applicability before acting.\nSource fact:\nThe official RFC 4456 — BGP Route Reflection: An Alternative to Full Mesh Internal BGP (IBGP) from RFC Editor / Internet Engineering Task Force supports the following bounded statements:\n\nA route reflector creates ORIGINATOR_ID from the original speaker’s BGP Identifier, and a router should ignore a route whose ORIGINATOR_ID equals its own identifier. The research record locates this support at Section 8 (Avoiding Routing Information Loops), ORIGINATOR_ID.\nEach reflector must prepend its local cluster ID to CLUSTER_LIST and should ignore an advertisement whose list already contains that local ID. The research record locates this support at Section 8 (Avoiding Routing Information Loops), CLUSTER_LIST.\nRoute selection treats ORIGINATOR_ID as the advertising speaker’s identifier and should prefer the shorter CLUSTER_LIST before the next tie-break step. The research record locates this support at Section 9 (Impact on Route Selection).\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. 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 8 (Avoiding Routing Information Loops), ORIGINATOR_ID, which observable configuration, record, or test can confirm applicability here?\nFor source statement 2 at Section 8 (Avoiding Routing Information Loops), CLUSTER_LIST, which observable configuration, record, or test can confirm applicability here?\nFor source statement 3 at Section 9 (Impact on Route Selection), 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.\nIf the review warrants change, use a bounded implementation with prerequisites, test population, monitoring, abort criteria, and a rehearsed reversal. Sequence checks for DNS, Active Directory authentication, PKI, time, routing policy, transport reachability, and monitoring and sanitize protected material before retention.\nVerification and evidence\nBuild a reproducible chain from Section 8 (Avoiding Routing Information Loops), ORIGINATOR_ID; Section 8 (Avoiding Routing Information Loops), CLUSTER_LIST; Section 9 (Impact on Route Selection) 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.\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 4456 — BGP Route Reflection: An Alternative to Full Mesh Internal BGP (IBGP) — RFC Editor / Internet Engineering Task Force",
        "content_markdown": "Frame this document as a source-led configuration and assurance check: Prevent route-reflector loops with cluster and originator attributes. Only the official source and traced locations below supply facts. Confirm applicability before acting.\n\n## Source fact:\n\nThe official [RFC 4456 — BGP Route Reflection: An Alternative to Full Mesh Internal BGP (IBGP)](https://www.rfc-editor.org/rfc/rfc4456.html) from RFC Editor / Internet Engineering Task Force supports the following bounded statements:\n\n- A route reflector creates ORIGINATOR_ID from the original speaker’s BGP Identifier, and a router should ignore a route whose ORIGINATOR_ID equals its own identifier. The research record locates this support at Section 8 (Avoiding Routing Information Loops), ORIGINATOR_ID.\n\n- Each reflector must prepend its local cluster ID to CLUSTER_LIST and should ignore an advertisement whose list already contains that local ID. The research record locates this support at Section 8 (Avoiding Routing Information Loops), CLUSTER_LIST.\n\n- Route selection treats ORIGINATOR_ID as the advertising speaker’s identifier and should prefer the shorter CLUSTER_LIST before the next tie-break step. The research record locates this support at Section 9 (Impact on Route Selection).\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. 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 8 (Avoiding Routing Information Loops), ORIGINATOR_ID, which observable configuration, record, or test can confirm applicability here?\n\n- For source statement 2 at Section 8 (Avoiding Routing Information Loops), CLUSTER_LIST, which observable configuration, record, or test can confirm applicability here?\n\n- For source statement 3 at Section 9 (Impact on Route Selection), 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\nIf the review warrants change, use a bounded implementation with prerequisites, test population, monitoring, abort criteria, and a rehearsed reversal. Sequence checks for DNS, Active Directory authentication, PKI, time, routing policy, transport reachability, and monitoring and sanitize protected material before retention.\n\n## Verification and evidence\n\nBuild a reproducible chain from Section 8 (Avoiding Routing Information Loops), ORIGINATOR_ID; Section 8 (Avoiding Routing Information Loops), CLUSTER_LIST; Section 9 (Impact on Route Selection) 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\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 4456 — BGP Route Reflection: An Alternative to Full Mesh Internal BGP (IBGP)](https://www.rfc-editor.org/rfc/rfc4456.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/prevent-route-reflector-loops-with-cluster-and-originator-attributes/",
                "url": "https://update.dsesecurity.com/updates/prevent-route-reflector-loops-with-cluster-and-originator-attributes/",
                "isPartOf": {
                    "@id": "https://update.dsesecurity.com/#website"
                },
                "lastReviewed": "2026-08-26"
            },
            {
                "@type": "BreadcrumbList",
                "@id": "https://update.dsesecurity.com/updates/prevent-route-reflector-loops-with-cluster-and-originator-attributes/#breadcrumbs",
                "itemListElement": [
                    {
                        "@type": "ListItem",
                        "position": 1,
                        "name": "DSE Updates",
                        "item": "https://update.dsesecurity.com/"
                    },
                    {
                        "@type": "ListItem",
                        "position": 2,
                        "name": "Prevent route-reflector loops with cluster and originator attributes",
                        "item": "https://update.dsesecurity.com/updates/prevent-route-reflector-loops-with-cluster-and-originator-attributes/"
                    }
                ]
            },
            {
                "@type": [
                    "Article",
                    "TechArticle"
                ],
                "@id": "https://update.dsesecurity.com/updates/prevent-route-reflector-loops-with-cluster-and-originator-attributes/#article",
                "identifier": "https://update.dsesecurity.com/updates/prevent-route-reflector-loops-with-cluster-and-originator-attributes/",
                "url": "https://update.dsesecurity.com/updates/prevent-route-reflector-loops-with-cluster-and-originator-attributes/",
                "headline": "Prevent route-reflector loops with cluster and originator attributes",
                "description": "Use RFC 4456 — BGP Route Reflection: An Alternative to Full Mesh Internal BGP (IBGP) to review this narrow operational decision without extending the…",
                "abstract": "Use RFC 4456 — BGP Route Reflection: An Alternative to Full Mesh Internal BGP (IBGP) 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: Prevent route-reflector loops with cluster and originator attributes. Only the official source and traced locations below supply facts. Confirm applicability before acting.\nSource fact:\nThe official RFC 4456 — BGP Route Reflection: An Alternative to Full Mesh Internal BGP (IBGP) from RFC Editor / Internet Engineering Task Force supports the following bounded statements:\n\nA route reflector creates ORIGINATOR_ID from the original speaker’s BGP Identifier, and a router should ignore a route whose ORIGINATOR_ID equals its own identifier. The research record locates this support at Section 8 (Avoiding Routing Information Loops), ORIGINATOR_ID.\nEach reflector must prepend its local cluster ID to CLUSTER_LIST and should ignore an advertisement whose list already contains that local ID. The research record locates this support at Section 8 (Avoiding Routing Information Loops), CLUSTER_LIST.\nRoute selection treats ORIGINATOR_ID as the advertising speaker’s identifier and should prefer the shorter CLUSTER_LIST before the next tie-break step. The research record locates this support at Section 9 (Impact on Route Selection).\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. 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 8 (Avoiding Routing Information Loops), ORIGINATOR_ID, which observable configuration, record, or test can confirm applicability here?\nFor source statement 2 at Section 8 (Avoiding Routing Information Loops), CLUSTER_LIST, which observable configuration, record, or test can confirm applicability here?\nFor source statement 3 at Section 9 (Impact on Route Selection), 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.\nIf the review warrants change, use a bounded implementation with prerequisites, test population, monitoring, abort criteria, and a rehearsed reversal. Sequence checks for DNS, Active Directory authentication, PKI, time, routing policy, transport reachability, and monitoring and sanitize protected material before retention.\nVerification and evidence\nBuild a reproducible chain from Section 8 (Avoiding Routing Information Loops), ORIGINATOR_ID; Section 8 (Avoiding Routing Information Loops), CLUSTER_LIST; Section 9 (Impact on Route Selection) 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.\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 4456 — BGP Route Reflection: An Alternative to Full Mesh Internal BGP (IBGP) — RFC Editor / Internet Engineering Task Force",
                "datePublished": "2026-08-27T12:16:18+00:00",
                "dateModified": "2026-08-27T12:53:57+00:00",
                "mainEntityOfPage": {
                    "@id": "https://update.dsesecurity.com/updates/prevent-route-reflector-loops-with-cluster-and-originator-attributes/"
                },
                "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/prevent-route-reflector-loops-with-cluster-and-originator-attributes/#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": "Prevent route-reflector loops with cluster and originator attributes"
                },
                "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": 603,
                "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 4456 — BGP Route Reflection: An Alternative to Full Mesh Internal BGP (IBGP)",
                    "url": "https://www.rfc-editor.org/rfc/rfc4456.html"
                }
            }
        ]
    }
}