<instructions>Your goal is to analyze the following comment and estimate how highly it will be upvoted by the Hacker News community.</instructions><comment><author>rwg</author><text>The default partitioning of CAM space on Cisco gear is the obvious issue, but the root cause is the massive deaggregation of announced IPv4 routes on the Internet.  You can see various statistics about this problem at &lt;a href=&quot;http://www.cidr-report.org/&quot; rel=&quot;nofollow&quot;&gt;http:&amp;#x2F;&amp;#x2F;www.cidr-report.org&amp;#x2F;&lt;/a&gt;, but the short of it is that if the top 30 networks (based on announced route savings) completely aggregated their announcements as much as possible, ~41,000 routes (~8% of the routing table) would be eliminated.&lt;p&gt;And that&amp;#x27;s just the top 30 networks — if every network cleaned up their announcements, it would eliminate ~232,000 routes (~45% of the table).&lt;p&gt;Adding to the deaggregation problem is the inability to easily filter out route announcements based on RIR minimum allocations without having to add tons of exceptions for CDNs that operate as islands of connectivity and carve out IP space for each island from a single address space allocation.  (There&amp;#x27;s no covering route for the islands of connectivity since these CDNs have no &amp;quot;backbone&amp;quot; connecting the islands, so if you filter out those smaller announcements, you lose connectivity to those islands.)&lt;p&gt;There are many people who think this problem will just magically go away as IPv6 adoption increases, but all increased IPv6 adoption will do is make limited CAM space even more limited as network engineers have to balance dividing precious CAM space between a ballooning-quickly IPv4 route table and a ballooning-slightly-less-quickly IPv6 route table.&lt;p&gt;(To be clear: I think ubiquitous, functioning, end-to-end native IPv6 connectivity needs to happen sooner than later, but it&amp;#x27;s not a magic bullet for the Internet&amp;#x27;s technical problems.)</text><parent_chain></parent_chain></comment><story><title>Something is amiss with the Interwebs: BGP is a flapping</title><url>https://isc.sans.edu/forums/diary/Something+is+amiss+with+the+Interwebs+BGP+is+a+flapping+/18523</url><text></text></story>
<instructions>Your goal is to analyze the following comment and estimate how highly it will be upvoted by the Hacker News community.</instructions><comment><author>oasisbob</author><text>As discussed on NANOG from a few months ago:&lt;p&gt;&lt;a href=&quot;http://markmail.org/message/n32fmeb2dmtnbsff&quot; rel=&quot;nofollow&quot;&gt;http:&amp;#x2F;&amp;#x2F;markmail.org&amp;#x2F;message&amp;#x2F;n32fmeb2dmtnbsff&lt;/a&gt;&lt;p&gt;I find the economics of the routing table to be fascinating. When someone announces a route, it makes use of a constrained (and often expensive, TCAM-based) resource on routers all over the world. More discussion:&lt;p&gt;&lt;a href=&quot;http://markmail.org/message/6sunzqtffav5jmfb&quot; rel=&quot;nofollow&quot;&gt;http:&amp;#x2F;&amp;#x2F;markmail.org&amp;#x2F;message&amp;#x2F;6sunzqtffav5jmfb&lt;/a&gt;</text><parent_chain></parent_chain></comment><story><title>Something is amiss with the Interwebs: BGP is a flapping</title><url>https://isc.sans.edu/forums/diary/Something+is+amiss+with+the+Interwebs+BGP+is+a+flapping+/18523</url><text></text></story>