<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
<title></title>
</head>
<body text="#000000" bgcolor="#ffffff">
On 2/6/2011 9:47 PM, George Bonser wrote:
<blockquote
cite="mid:5A6D953473350C4B9995546AFE9939EE0BC138AC@RWC-EX1.corp.seven.com"
type="cite">
<meta http-equiv="Context-Type" content="text/html;
charset=us-ascii">
<title>RE: [arin-ppml] "Leasing" of space via non-connectivity
providers</title>
<p><span lang="en-us"></span></p>
<span lang="en-us"></span><span lang="en-us">It's funny, though,
because in some cases I got a /24, </span><span lang="en-us">
the /25's, all of the /26's, /27's, /28's, /29's, and some /30's
and then all of the /32's for all of the IPs in the /24! </span>
<p><span lang="en-us"></span></p>
<p><span lang="en-us"> It was just nuts. </span><span
lang="en-us"> </span></p>
<br>
</blockquote>
<br>
That's what I said of a sister company's network when their engineer
left and I took it over. /32's for every ppp session advertised via
3 IGPs!<br>
<br>
I did a little bit more work. I tried to make sure my scripts pulled
the correct information, and it does look accurate, though I won't
attest to complete accuracy. ;)<br>
<br>
Taking the data from the overall ASN report,<br>
<br>
28,579 ASNs were at 0.00% or 78% of the ASNs recorded. Granted, they
only advertised 55,788 combined routes which would be 27% of the
report's Annce total.<br>
<br>
However, I would still stand on the premise that if the market
starts transferring networks at the /24 level, routing table bloat
would increase. Operators only have the choice to aggregate as much
as their allocations allow. Networks grow over the years and IPv4
required multiple non-contiguous allocations. The 55,788 routes most
likely will be a much smaller number for those 28,579 ASNs in IPv6.
However, if RIRs had given out smaller allocations, the number would
likely be much larger.<br>
<br>
<br>
Jack<br>
</body>
</html>