Contain malformed BGP UPDATE attributes with the specified recovery action

Use this document to connect an official requirement or behavior to observable evidence: Contain malformed BGP UPDATE attributes with the specified recovery action. Only the official source and traced locations below supply facts. Confirm applicability before acting.

Source fact:

The official RFC 7606 — Revised Error Handling for BGP UPDATE Messages from RFC Editor / Internet Engineering Task Force supports the following bounded statements:

• The four ordered BGP UPDATE recovery actions are session reset, AFI/SAFI disable, treat-as-withdraw, and attribute discard; discard is restricted to attributes that cannot affect route selection or installation. The research record locates this support at Section 2 (Error-Handling Approaches).
• Conflicting Optional or Transitive flags and missing well-known mandatory attributes use treat-as-withdraw, while malformed ATOMIC_AGGREGATE or AGGREGATOR cases specified here use attribute discard. The research record locates this support at Section 3 (Revision to BGP UPDATE Message Error Handling), items c, d, and f.
• When one UPDATE has multiple attribute errors that prescribe different recoveries, the speaker must apply the strongest specified action. The research record locates this support at Section 3 (Revision to BGP UPDATE Message Error Handling), item h.

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.

What the source does not establish

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.

Applicability questions

• For source statement 1 at Section 2 (Error-Handling Approaches), which observable configuration, record, or test can confirm applicability here?
• For source statement 2 at Section 3 (Revision to BGP UPDATE Message Error Handling), items c, d, and f, which observable configuration, record, or test can confirm applicability here?
• For source statement 3 at Section 3 (Revision to BGP UPDATE Message Error Handling), item h, which observable configuration, record, or test can confirm applicability here?
• Within address plans, interfaces, routes, peers, protocol roles, timers, middleboxes, and intended failure domains, which versions, roles, and configuration states define the review population?
• Could DNS, Active Directory authentication, PKI, time, routing policy, transport reachability, and monitoring invalidate the test, hide a failure, or change applicability?
• Who owns the decision, and which observation requires stopping, escalation, or rollback?

DSE recommendation:

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.

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.

Verification and evidence

A reviewer should be able to retrace the decision from Section 2 (Error-Handling Approaches); Section 3 (Revision to BGP UPDATE Message Error Handling), items c, d, and f; Section 3 (Revision to BGP UPDATE Message Error Handling), item h 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.

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

Official references

• RFC 7606 — Revised Error Handling for BGP UPDATE Messages — RFC Editor / Internet Engineering Task Force