> What do you mean “in your table at all”? The RIB normally only includes the > best path for each RIB client. RPF is normally only on the best path.
http://www.cisco.com/c/en/us/td/docs/ios-xml/ios/sec_data_urpf/configuration/15-s/sec-data-urpf-15-s-book/sec-unicast-rpf-loose.html This is implemented in virtually every OS I know of in some way -- and it's different from -- http://www.cisco.com/c/en/us/td/docs/ios/12_0s/feature/guide/srpf_gsr.html > > There is one more that could be tied to BGP security, and there are > >potentially others that could be tied to overlay networks, and > >potential solutions for load balancing in the future. It just seems to > >me this is a broader space than a single flag can cover, and it's > >possible more solutions could be used in this space beyond the two we > >have already, so it probably makes sense to make this extensible. > > There are NO implementations that query BGP for a path in any acceptable > Adj-RIB-In for the RPF check. I’m not sure what you are envisioning. Not right now -- I'm just saying there are other possibilities here beyond the two I already know about, so it might be wise to allow for more in the future with something other than a single bit flag. :-) Russ _______________________________________________ i2rs mailing list [email protected] https://www.ietf.org/mailman/listinfo/i2rs
