Alternative to NetFlow for Measuring Traffic flows
K. Scott Bethke
kbethke at thruport.com
Tue Dec 17 02:16:55 UTC 2002
Impressive numbers but of course, slackers aside, if it was your connection
and resources wouldnt you want more accurate information than just a guess?
This may be effective for an IX decision if you created some sort of a map
based on ALL the ASN's of the people on the peering switch.. but in most
cases anyone pushing any real traffic will probably not have fine grained
samples enough to determine a peering relationship based on a single AS
with this method. Maybe Im wrong but hey if you are taking 200megs from any
one ASN I would hope you knew about it.
> Interesting idea. Comments?
Again it seems to iffy. What if you get a short DOS when you shift an ASN..
how much of a chump will you look like when you need that peer to be 1gbps
and you hook up and its only pulling 2mpbs ?
> The other approach some ISPs use is to set up a "trial" peering session,
> usually using a private cross connect to measure the traffic volume and
> relative traffic ratios. Then both side can get an idea of the traffic
> before engaging in a contractual Settlement-Free Peering relationship.
I like this one the best if I didnt have Netflow stat's... however I doubt
everyone will allow this because of time, money, resources, security, etc.
I tend to look at peering as something you need to know when to do because
the data tells you so. In this industry as it stands now why would you NOT
run netflow stats to give you this information? all you are doing is
wasting more money paying for transit that could be offloaded to peering.
And the flipside is also true.. why even worry about peering if you cant
get more than a meg or two max to each AS?
More information about the NANOG