Validate BGP egress against the effective origin AS after outbound policy

Treat this document as a focused evidence review: Validate BGP egress against the effective origin AS after outbound policy. Only the official source and traced locations below supply facts. Confirm applicability before acting.

Source fact:

The official RFC 8893 — Resource Public Key Infrastructure (RPKI) Origin Validation for BGP Export from RFC Editor / Internet Engineering Task Force supports the following bounded statements:

• A validating BGP speaker must determine egress origin-validation state from the effective origin AS after outbound configuration and policy have been applied. The research record locates this support at Sections 1 (Introduction) and 3 (Egress Processing).
• Implementations supporting RPKI origin validation must expose validation-state policy primitives for ingress, redistribution, and egress decisions. The research record locates this support at Section 3 (Egress Processing).
• RFC 8893 recommends that implementations be able to list announcements not sent to a peer, including those withheld because they were Invalid. The research record locates this support at Section 4 (Operational Considerations).

Do not import neighboring assumptions into the source record. The supported task is a scoped comparison involving address plans, interfaces, routes, peers, protocol roles, timers, middleboxes, and intended failure domains and the conditions the source actually describes.

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

Applicability questions

• For source statement 1 at Sections 1 (Introduction) and 3 (Egress Processing), which observable configuration, record, or test can confirm applicability here?
• For source statement 2 at Section 3 (Egress Processing), which observable configuration, record, or test can confirm applicability here?
• For source statement 3 at Section 4 (Operational Considerations), 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. Use a two-person review for the source interpretation and the resulting operational decision. 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.

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.

Verification and evidence

Tie each conclusion back to Sections 1 (Introduction) and 3 (Egress Processing); Section 3 (Egress Processing); Section 4 (Operational Considerations) and to observable material such as configuration snapshots, route or neighbor state, packet captures, counters, topology records, and controlled failover results. Preserve provenance and stable identifiers without copying secrets into the evidence set.

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 8893 — Resource Public Key Infrastructure (RPKI) Origin Validation for BGP Export — RFC Editor / Internet Engineering Task Force