Hi Russ, On 2/2/16, 7:33 PM, "i2rs on behalf of Russ White" <[email protected] on behalf of [email protected]> wrote:
> >> Can you expand on the 2 sorts of RPF checks already out there. And >>then >> we can figure out which ones we need to include for now. If need be, >>then >> we can make RPF check into an object as you are suggesting. > >Sure -- There is loose (just check to see if you have it in your table at >all) and strict (check to make certain this destination's best path is >through this interface). 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. > 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. Thanks, Acee > >:-) > >Russ > > >_______________________________________________ >i2rs mailing list >[email protected] >https://www.ietf.org/mailman/listinfo/i2rs _______________________________________________ i2rs mailing list [email protected] https://www.ietf.org/mailman/listinfo/i2rs
