{ "api_version": "1", "kind": "dse_post", "self": "https://update.dsesecurity.com/api/v1/posts/negotiate-each-bgp-address-family-before-exchanging-reachability/", "item": { "id": "https://update.dsesecurity.com/updates/negotiate-each-bgp-address-family-before-exchanging-reachability/", "slug": "negotiate-each-bgp-address-family-before-exchanging-reachability", "url": "https://update.dsesecurity.com/updates/negotiate-each-bgp-address-family-before-exchanging-reachability/", "alternate_urls": { "markdown": "https://update.dsesecurity.com/updates/negotiate-each-bgp-address-family-before-exchanging-reachability.md", "json": "https://update.dsesecurity.com/api/v1/posts/negotiate-each-bgp-address-family-before-exchanging-reachability/" }, "title": "Negotiate each BGP address family before exchanging reachability", "summary": "Use RFC 4760 — Multiprotocol Extensions for BGP-4 to review this narrow operational decision without extending the source beyond its stated scope.", "format": { "slug": "playbook", "name": "Playbook" }, "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:21+00:00", "modified_at": "2026-08-27T12:53:57+00:00", "reviewed_on": "2026-08-26", "reading_minutes": 3, "word_count": 581, "potentially_affected": "Teams, systems, services, or facilities within the stated scope of RFC 4760 — Multiprotocol Extensions for BGP-4", "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 4760 — Multiprotocol Extensions for BGP-4", "url": "https://www.rfc-editor.org/rfc/rfc4760.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": "

Keep this document to one review outcome: Negotiate each BGP address family before exchanging reachability. Only the official source and traced locations below supply facts. Confirm applicability before acting.

\n

Source fact:

\n

The official RFC 4760 — Multiprotocol Extensions for BGP-4 from RFC Editor / Internet Engineering Task Force supports the following bounded statements:

\n\n

These statements are the factual basis for this document. Do not extend them into a broader assurance. Review address plans, interfaces, routes, peers, protocol roles, timers, middleboxes, and intended failure domains only where the source and recorded environment align.

\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. Start with applicability, then compare the observed state with the cited source. 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

An implementation decision needs an owner, approved window, prechecks, observable outcome, stop authority, and rollback path. Validate DNS, Active Directory authentication, PKI, time, routing policy, transport reachability, and monitoring before and after the test, and store only sanitized operational evidence.

\n

Verification and evidence

\n

Evidence should let another reviewer reproduce this decision. Retain observations beside the traced locations Section 3 (Multiprotocol Reachable NLRI – MP_REACH_NLRI); Section 4 (Multiprotocol Unreachable NLRI – MP_UNREACH_NLRI); Section 8 (Use of BGP Capability Advertisement). Favor configuration snapshots, route or neighbor state, packet captures, counters, topology records, and controlled failover results, linked to stable identifiers, time, and operator.

\n

Close the review only when the evidence, exception handling, resulting action, and after-state are linked. Schedule a new review after material technical, organizational, incident, or source changes; today’s observation is not a continuing guarantee.

\n

Official references

\n", "content_text": "Keep this document to one review outcome: Negotiate each BGP address family before exchanging reachability. Only the official source and traced locations below supply facts. Confirm applicability before acting.\nSource fact:\nThe official RFC 4760 — Multiprotocol Extensions for BGP-4 from RFC Editor / Internet Engineering Task Force supports the following bounded statements:\n\nMP_REACH_NLRI advertises reachable prefixes and their next hop, with AFI and SAFI identifying the address-family semantics. The research record locates this support at Section 3 (Multiprotocol Reachable NLRI – MP_REACH_NLRI).\nMP_UNREACH_NLRI withdraws multiple routes for the AFI and SAFI carried in that attribute. The research record locates this support at Section 4 (Multiprotocol Unreachable NLRI – MP_UNREACH_NLRI).\nBidirectional route exchange for an AFI/SAFI requires both peers to advertise support for that exact tuple through BGP Capability Advertisement. The research record locates this support at Section 8 (Use of BGP Capability Advertisement).\n\nThese statements are the factual basis for this document. Do not extend them into a broader assurance. Review address plans, interfaces, routes, peers, protocol roles, timers, middleboxes, and intended failure domains only where the source and recorded environment align.\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 3 (Multiprotocol Reachable NLRI – MP_REACH_NLRI), which observable configuration, record, or test can confirm applicability here?\nFor source statement 2 at Section 4 (Multiprotocol Unreachable NLRI – MP_UNREACH_NLRI), which observable configuration, record, or test can confirm applicability here?\nFor source statement 3 at Section 8 (Use of BGP Capability Advertisement), 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. Start with applicability, then compare the observed state with the cited source. 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.\nAn implementation decision needs an owner, approved window, prechecks, observable outcome, stop authority, and rollback path. Validate DNS, Active Directory authentication, PKI, time, routing policy, transport reachability, and monitoring before and after the test, and store only sanitized operational evidence.\nVerification and evidence\nEvidence should let another reviewer reproduce this decision. Retain observations beside the traced locations Section 3 (Multiprotocol Reachable NLRI – MP_REACH_NLRI); Section 4 (Multiprotocol Unreachable NLRI – MP_UNREACH_NLRI); Section 8 (Use of BGP Capability Advertisement). Favor configuration snapshots, route or neighbor state, packet captures, counters, topology records, and controlled failover results, linked to stable identifiers, time, and operator.\nClose the review only when the evidence, exception handling, resulting action, and after-state are linked. Schedule a new review after material technical, organizational, incident, or source changes; today’s observation is not a continuing guarantee.\nOfficial references\n\nRFC 4760 — Multiprotocol Extensions for BGP-4 — RFC Editor / Internet Engineering Task Force", "content_markdown": "Keep this document to one review outcome: Negotiate each BGP address family before exchanging reachability. Only the official source and traced locations below supply facts. Confirm applicability before acting.\n\n## Source fact:\n\nThe official [RFC 4760 — Multiprotocol Extensions for BGP-4](https://www.rfc-editor.org/rfc/rfc4760.html) from RFC Editor / Internet Engineering Task Force supports the following bounded statements:\n\n- MP_REACH_NLRI advertises reachable prefixes and their next hop, with AFI and SAFI identifying the address-family semantics. The research record locates this support at Section 3 (Multiprotocol Reachable NLRI – MP_REACH_NLRI).\n\n- MP_UNREACH_NLRI withdraws multiple routes for the AFI and SAFI carried in that attribute. The research record locates this support at Section 4 (Multiprotocol Unreachable NLRI – MP_UNREACH_NLRI).\n\n- Bidirectional route exchange for an AFI/SAFI requires both peers to advertise support for that exact tuple through BGP Capability Advertisement. The research record locates this support at Section 8 (Use of BGP Capability Advertisement).\n\nThese statements are the factual basis for this document. Do not extend them into a broader assurance. Review address plans, interfaces, routes, peers, protocol roles, timers, middleboxes, and intended failure domains only where the source and recorded environment align.\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 3 (Multiprotocol Reachable NLRI – MP_REACH_NLRI), which observable configuration, record, or test can confirm applicability here?\n\n- For source statement 2 at Section 4 (Multiprotocol Unreachable NLRI – MP_UNREACH_NLRI), which observable configuration, record, or test can confirm applicability here?\n\n- For source statement 3 at Section 8 (Use of BGP Capability Advertisement), 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. Start with applicability, then compare the observed state with the cited source. 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\nAn implementation decision needs an owner, approved window, prechecks, observable outcome, stop authority, and rollback path. Validate DNS, Active Directory authentication, PKI, time, routing policy, transport reachability, and monitoring before and after the test, and store only sanitized operational evidence.\n\n## Verification and evidence\n\nEvidence should let another reviewer reproduce this decision. Retain observations beside the traced locations Section 3 (Multiprotocol Reachable NLRI – MP_REACH_NLRI); Section 4 (Multiprotocol Unreachable NLRI – MP_UNREACH_NLRI); Section 8 (Use of BGP Capability Advertisement). Favor configuration snapshots, route or neighbor state, packet captures, counters, topology records, and controlled failover results, linked to stable identifiers, time, and operator.\n\nClose the review only when the evidence, exception handling, resulting action, and after-state are linked. Schedule a new review after material technical, organizational, incident, or source changes; today’s observation is not a continuing guarantee.\n\n## Official references\n\n- [RFC 4760 — Multiprotocol Extensions for BGP-4](https://www.rfc-editor.org/rfc/rfc4760.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/negotiate-each-bgp-address-family-before-exchanging-reachability/", "url": "https://update.dsesecurity.com/updates/negotiate-each-bgp-address-family-before-exchanging-reachability/", "isPartOf": { "@id": "https://update.dsesecurity.com/#website" }, "lastReviewed": "2026-08-26" }, { "@type": "BreadcrumbList", "@id": "https://update.dsesecurity.com/updates/negotiate-each-bgp-address-family-before-exchanging-reachability/#breadcrumbs", "itemListElement": [ { "@type": "ListItem", "position": 1, "name": "DSE Updates", "item": "https://update.dsesecurity.com/" }, { "@type": "ListItem", "position": 2, "name": "Negotiate each BGP address family before exchanging reachability", "item": "https://update.dsesecurity.com/updates/negotiate-each-bgp-address-family-before-exchanging-reachability/" } ] }, { "@type": [ "Article", "TechArticle" ], "@id": "https://update.dsesecurity.com/updates/negotiate-each-bgp-address-family-before-exchanging-reachability/#article", "identifier": "https://update.dsesecurity.com/updates/negotiate-each-bgp-address-family-before-exchanging-reachability/", "url": "https://update.dsesecurity.com/updates/negotiate-each-bgp-address-family-before-exchanging-reachability/", "headline": "Negotiate each BGP address family before exchanging reachability", "description": "Use RFC 4760 — Multiprotocol Extensions for BGP-4 to review this narrow operational decision without extending the source beyond its stated scope.", "abstract": "Use RFC 4760 — Multiprotocol Extensions for BGP-4 to review this narrow operational decision without extending the source beyond its stated scope.", "articleBody": "Keep this document to one review outcome: Negotiate each BGP address family before exchanging reachability. Only the official source and traced locations below supply facts. Confirm applicability before acting.\nSource fact:\nThe official RFC 4760 — Multiprotocol Extensions for BGP-4 from RFC Editor / Internet Engineering Task Force supports the following bounded statements:\n\nMP_REACH_NLRI advertises reachable prefixes and their next hop, with AFI and SAFI identifying the address-family semantics. The research record locates this support at Section 3 (Multiprotocol Reachable NLRI – MP_REACH_NLRI).\nMP_UNREACH_NLRI withdraws multiple routes for the AFI and SAFI carried in that attribute. The research record locates this support at Section 4 (Multiprotocol Unreachable NLRI – MP_UNREACH_NLRI).\nBidirectional route exchange for an AFI/SAFI requires both peers to advertise support for that exact tuple through BGP Capability Advertisement. The research record locates this support at Section 8 (Use of BGP Capability Advertisement).\n\nThese statements are the factual basis for this document. Do not extend them into a broader assurance. Review address plans, interfaces, routes, peers, protocol roles, timers, middleboxes, and intended failure domains only where the source and recorded environment align.\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 3 (Multiprotocol Reachable NLRI – MP_REACH_NLRI), which observable configuration, record, or test can confirm applicability here?\nFor source statement 2 at Section 4 (Multiprotocol Unreachable NLRI – MP_UNREACH_NLRI), which observable configuration, record, or test can confirm applicability here?\nFor source statement 3 at Section 8 (Use of BGP Capability Advertisement), 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. Start with applicability, then compare the observed state with the cited source. 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.\nAn implementation decision needs an owner, approved window, prechecks, observable outcome, stop authority, and rollback path. Validate DNS, Active Directory authentication, PKI, time, routing policy, transport reachability, and monitoring before and after the test, and store only sanitized operational evidence.\nVerification and evidence\nEvidence should let another reviewer reproduce this decision. Retain observations beside the traced locations Section 3 (Multiprotocol Reachable NLRI – MP_REACH_NLRI); Section 4 (Multiprotocol Unreachable NLRI – MP_UNREACH_NLRI); Section 8 (Use of BGP Capability Advertisement). Favor configuration snapshots, route or neighbor state, packet captures, counters, topology records, and controlled failover results, linked to stable identifiers, time, and operator.\nClose the review only when the evidence, exception handling, resulting action, and after-state are linked. Schedule a new review after material technical, organizational, incident, or source changes; today’s observation is not a continuing guarantee.\nOfficial references\n\nRFC 4760 — Multiprotocol Extensions for BGP-4 — RFC Editor / Internet Engineering Task Force", "datePublished": "2026-08-27T12:16:21+00:00", "dateModified": "2026-08-27T12:53:57+00:00", "mainEntityOfPage": { "@id": "https://update.dsesecurity.com/updates/negotiate-each-bgp-address-family-before-exchanging-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/negotiate-each-bgp-address-family-before-exchanging-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": "Negotiate each BGP address family before exchanging reachability" }, "articleSection": [ "IT", "Networks & Infrastructure" ], "keywords": [ "IT", "Networks & Infrastructure", "Playbook", "Advisory priority" ], "genre": "Playbook", "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": 581, "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 4760 — Multiprotocol Extensions for BGP-4", "url": "https://www.rfc-editor.org/rfc/rfc4760.html" } } ] } }