RFC 3704:Ingress Filtering for Multihomed Networks
RFC-Ref

router


Click on the red underlined text to get to the source

... lack of a route in the filtering router's Forwarding Information Base. ...
... ISP assigns a better metric which is not propagated outside of the router, either a vendor-specific "weight" or a protocol distance to prefer the directly received routes. With BGP ...
... RPF filtering between the primary and secondary edge routers; in particular, when applied to multihoming to different ISPs ...
... (i.e., the same prefix(es), through all the paths) propagating to all the routers performing Feasible RPF checking. For example, this may not hold e.g., in the case where a secondary ISP ...
... default routes, i.e., an "explicit route presence check". In this approach, the router looks up the source address in the route table, and preserves the packet if a route ...


... ingress filtering at the edges of ISPs where appropriate, at the routers connecting LANs to an enterprise network ...
... deployment of ingress filtering may not be readily apparent. The routers and other ISP infrastructure are vulnerable to several kinds of attacks ...


... ISP [4][5]. This way the edge routers are configured to first inspect the source address of a packet destined to an ISP ...
... ISP. If such a scenario is applied exhaustively, so that an exit router is chosen in the edge network ...


... The closer to the actual source ingress filtering is performed, the more effective it is. One could wish that the first hop router would ensure that traffic being sourced from its neighboring end system was ...
... ensure that traffic being sourced from its neighboring end system was correctly addressed; a router further away can only ensure that it is possible that there is such a system within the indicated prefix. ...


... Hagino, J. and H. Snyder, "IPv6 Multihoming Support at Site Exit Routers", RFC 3178, October 2001. ...



Google
Web
RFC-Ref