Not this thread, again. Again? Seriously, why not mention this? This is extremely relevant if you look at some of the NZ ASs and apparent lack of aggregation (I assume you have plenty of nice views of NZ by now, if not holler and I'll find one or two more). The other thing I used to see a fair bit of was inconsistent origin ASs advertisements, I'm not so sure if this is still the case (some of it could be explained as transients because at one pont companies were swallowing other companies as fast as, ummm... like, really fast, man). <pause> I just checked, it's not really that bad anymore, but I have to wonder about some of the stuff I see there. for some of these, its a little hard to always figure out who is in error as not all of these records are in the APNIC-DB or RADDB. Any suggestions on where else I might look? There is a requirement for some networks to propagate edge policy through long-prefix advertisements. There are few reliable alternatives mechanisms known. If you know a better way, please share. Donning my best asbestos suit and bow-tie... I assume we are talking about aggregation by origin AS, not transit or peer-intermediary? Aggregation of adjacent prefixes who's attributes are otherwise completely identical. External to the AS I can't see why you would want or need to know about these longer prefixes (edge policy or otherwise). The draft (which you wrote) states: There is a requirement for some multi-homed sites to influence the path selected by autonomous systems beyond those that are immediately adjacent. If all attributes are equal external to the AS (to most or all external ASs), then how does this help? A quick cursory view on route-views shows that there may indeed be benefits from aggregating from 1221 (and also that they are bleeding RFC1918 stuff to the route-server). I won't pretend I've check it thoroughly recently, I assume those who claim to aren't lying to me :) I'm not saying Telstra doesn't have a need for this huge lack of aggregation, but it does strike be as somewhat unusual that they are top of the list --- especially when _much_ larger networks are further down. Getting back to the NZ situation, NZ is terribly fragmented in some places. It seems a common trend that people move providers and expect they can take the address space with them indefinitely. Renumbering isn't necessarily difficult or painful for most people, if it is, you are doing something wrong. If anybody is interested, I'm happy to figure out and post a list of advertisements and aggregatable savings and advertisement densities[1] against known New Zealand AS. I had code to do this (partially, it didn't really consider all paths and attributes, but manual inspection of the worst offended seems to indicate everything is the same) and Geoff's code looks interesting, so its a good excuse to play with that. Of course, to do this properly, you really need to get feeds from as many ASs as possible... so I wonder if you can assist Joe? (I just need you to run a pre-supplied binary as root, it will do the rest). --cw [1] I made that phrase up, maybe someone else has a better one. Basically, its the total number of addresses advertised divided by the number or advertisements. If you advertise lots of non-adjacent blocks then this will have a relatively low value compared to someone who advertises a few large super-nets or a carrier with several older institutions with legacy class B space. Since I made this up, it may not have any useful meaning to anyone but me :) --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog