nanog mailing list archives
Re: Partial vs Full tables
From: Saku Ytti <saku () ytti fi>
Date: Mon, 15 Jun 2020 15:54:25 +0300
Hey Drew,
The only time we have ever noticed any sort of operational downside of using uRPF loose was when NTTs router in NYC thought a full table was only 500,000 routes a few years back.
If NTT is 2914 this can no longer happen and it is difficult to see 2914 would ever go back to uRPF. In typical implementation today ACL is much cheaper than uRPF, so we've migrated to ACL. uRPF value proposition is mostly on CLI Jockey networks, if configuration are generated for most use-cases ACL is superior solution anyhow. In your particular defect, it doesn't seem to matter if uRPF was or was not enabled, was it dropped by uRPF/loose failure or lookup failure seems uninteresting (We do not default route). -- ++ytti
Current thread:
- Re: Partial vs Full tables, (continued)
- Re: Partial vs Full tables Brian Johnson (Jun 10)
- Re: Partial vs Full tables William Herrin (Jun 10)
- Re: Partial vs Full tables Baldur Norddahl (Jun 10)
- Re: Partial vs Full tables William Herrin (Jun 10)
- Re: Partial vs Full tables Chris Adams (Jun 10)
- Re: Partial vs Full tables Robert Blayzor (Jun 11)
- RE: Partial vs Full tables Brian Turnbow via NANOG (Jun 12)
- Re: Partial vs Full tables brad dreisbach (Jun 11)
- Re: Partial vs Full tables William Herrin (Jun 11)
- RE: Partial vs Full tables Drew Weaver (Jun 15)
- Re: Partial vs Full tables Saku Ytti (Jun 15)
- RE: Partial vs Full tables Drew Weaver (Jun 15)
- Re: Partial vs Full tables Brian Johnson (Jun 11)
- Re: Partial vs Full tables Brian Johnson (Jun 11)
- Re: Partial vs Full tables William Herrin (Jun 11)
- Re: Partial vs Full tables Brian Johnson (Jun 11)
- Re: Partial vs Full tables William Herrin (Jun 11)
- Re: Partial vs Full tables Brian Johnson (Jun 11)
- Re: Partial vs Full tables Mark Tinka (Jun 11)
- RE: Partial vs Full tables Michael Hare via NANOG (Jun 11)
- Re: Partial vs Full tables Mark Tinka (Jun 11)