Marco, My responses Marked with [Sriram] below:
[Marco] But it also goes further and suggest to amend the usual behavior by advertising via BGP the source addresses of the traffic you want to drop so that the routers can null route and trigger uRPF. This is where i see problems. [Sriram] This is not at all what our proposed enhanced feasible path uRPF does. To clarify, the proposal does not require/recommend making any BGP advertisements. A good description of the proposal was just mentioned in a response to Nick, which is copied here: The ISP's AS creates a union of all announced prefixes that have a common origin AS. Those announcements have potentially been received on various customer/ peer/ provider interfaces. Take that union of prefixes and include it in Reverse Path Filter (RPF) tables on all interfaces on which one or more of the prefixes in the union were announced. [Sriram] We are adding prefixes in the RPF table (with some more additional intelligence built-in as compared to the current feasible-path uRPF), and source addresses belonging in these are prefixes are permitted (not null routed). Sriram _______________________________________________ GROW mailing list [email protected] https://www.ietf.org/mailman/listinfo/grow
