Skip to main content

Maintain consistency of inter-domain routing and forwarding

Document Type Replaced Internet-Draft (individual)
Expired & archived
Authors Weiqiang Cheng , Mingxing Liu , Mingqing(Michael) Huang , Shengnan Yue
Last updated 2023-10-23
Replaced by draft-cheng-idr-conformance-forwarding
RFC stream (None)
Intended RFC status (None)
Stream Stream state (No stream defined)
Consensus boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Replaced by draft-cheng-idr-conformance-forwarding
Telechat date (None)
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:


The AS_PATH attribute of BGP UPDATE records the AS number that it has passed through. Ideally, the traffic to the destination IP prefixes in NLRI of BGP UPDATE should be reversely forwarded along the AS path recorded in the AS_PATH. However, due to other factors such traffic redirection, traffic engineering, and route aggregation, the actual forwarding AS path of the packet is usually different from the propagation path of BGP UPDATE. In other words, inter-domain routing and forwarding are usually inconsistent, which results in that inter- domain forwarding has security risks such as traffic black hole, loop, detour and the malicious AS, etc. Consistent inter-domain routing and forwarding greatly contributes to enhanced inter-domain forwarding security and visibility, which facilitates the long-term evolution of the Internet


Weiqiang Cheng
Mingxing Liu
Mingqing(Michael) Huang
Shengnan Yue

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)