Partial vs Full tables

Mike Hammett nanog at
Fri Jun 5 13:17:26 UTC 2020

Maybe instead of transit + 1, you use communities to just allow all customer prefixes, regardless of how deep they are. Obviously that community would need to be supported by that provider. 

I've been wondering a similar thing for how to take advantage of the 150k - 250k hardware routes the CRS317 now has in v7 beta. That many routes should cover the peering tables for most operators, maybe even transit's customers. 

Mike Hammett 
Intelligent Computing Solutions 


----- Original Message -----

From: "James Breeden" <James at> 
To: nanog at 
Sent: Thursday, June 4, 2020 10:00:51 PM 
Subject: Partial vs Full tables 

I have been doing a lot of research recently on operating networks with partial tables and a default to the rest of the world. Seems like an easy enough approach for regional networks where you have maybe only 1 upstream transit and some peering. 

I come to NANOG to get feedback from others who may be doing this. We have 3 upstream transit providers and PNI and public peers in 2 locations. It'd obviously be easy to transition to doing partial routes for just the peers, etc, but I'm not sure where to draw the line on the transit providers. I've thought of straight preferencing one over another. I've thought of using BGP filtering and community magic to basically allow Transit AS + 1 additional AS (Transit direct customer) as specific routes, with summarization to default for the rest. I'm sure there are other thoughts that I haven't had about this as well.... 

And before I get asked why not just run full tables, I'm looking at regional approaches to being able to use smaller, less powerful routers (or even layer3 switches) to run some areas of the network where we can benefit from summarization and full tables are really overkill. 

James W. Breeden 
Managing Partner 

Arenal Group: Arenal Consulting Group | Acilis Telecom | Pines Media 
PO Box 1063 | Smithville, TX 78957 
Email: james at | office 512.360.0000 | 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <>

More information about the NANOG mailing list