On Jul 09, 2014, at 16:03 , Bill Woodcock <[email protected]> wrote: > On Jul 9, 2014, at 12:46 PM, Patrick W. Gilmore <[email protected]> wrote:
>> Taking just Seattle IX (since I have a personal interest there :), it says >> "177" under “participants" > > Interesting. We pull automatically from the standard URL, > https://www.seattleix.net/participants/table but have to try to uniq it to > not double-count organizations that are peering under multiple ASNs, who are > peering on multiple subnets, etc. Because we’re doing that 400 times per > day, it’s all automated with rulesets and a whole lot of exceptions (knowing > that AS 701, 702, 703 are the same organization, etc.). > > The SIX is reporting 194 unique ASNs and 195 unique organization names. > Presumably we have some rules that are detecting that AS42 and AS3856, for > instance, are the same organization and consolidating those. I’ll have our > IXPdir maintenance staff take a look at where the differences lie, and > whether any of those rules need to be updated. Is that a good idea? For instance, if I were stupid enough to peer with as3856 and not with as42 (because not peering with either of those is idiotic :), would I get the same data as peering with both? It is absolutely true that if I peer with as702, I do _not_ get the same prefixes as peering with as701. Just because one is a downstream of the other does not mean they are separate (from BGP's PoV). -- TTFN, patrick
signature.asc
Description: Message signed with OpenPGP using GPGMail
