RFC 3704:Ingress Filtering for Multihomed Networks
RFC-Ref

BGP


Click on the red underlined text to get to the source

... ingress filtering, with the exception that the access list is dynamic. This may also be used to avoid duplicate configuration (e.g., maintaining both static routes or BGP prefix- list filters ...
... edge is advertising multiple prefixes using BGP. It makes for a simple, cheap, fast, and dynamic filter. ...
... hot potato" routing. Also, if BGP is carrying prefixes and some legitimate prefixes ...
... Forwarding Information Base. There are operational techniques, especially with BGP but somewhat applicable to other routing protocols as well, to make strict RPF ...
... router, either a vendor-specific "weight" or a protocol distance to prefer the directly received routes. With BGP and sufficient machinery in place, setting the preferences could even be automated, using BGP Communities ...
... BGP and sufficient machinery in place, setting the preferences could even be automated, using BGP Communities [2]. That way, the route will always be the ...
... routing-protocol specific methods, for example by including all or N (where N is less than all) feasible BGP paths in the Routing Information Base (RIB). Sometimes this method ...
... not hold e.g., in the case where a secondary ISP does not propagate the BGP advertisement to the primary ISP e.g., due to route-maps or ...


... RPF check, as described in Section 4.1. 5. Ensure, by BGP or by contract, that each ISP's ingress filter is ...
... prefixes and exchange routes with its ISPs with BGP, to ensure that its prefix is carried upstream ...


... Chandrasekeran, R., Traina, P. and T. Li, "BGP Communities Attribute", RFC 1997prop, August 1996. ...



Google
Web
RFC-Ref