Traffic ratio of an ISP

[prasun at nevada.unr.edu (Prasun Dey)]

Hi William, 
Ha ha! Thanks for pointing that out. Iâ??m not related to any ISP at all, so this is something new. I understand, PeeringDB is just a basic guideline and ISPs put their own information about their traffic ratios. Iâ??m interested to know whether ISPs check their own accumulated traffic and then set their own outbound:inbound traffic ratios threshold to declare themselves as Heavy Outbound/ Inbound or Balanced. Or, is there some kind of rough understanding among networking community to treat certain ratios as Heavy/ Mostly Inbound/ Outbound. 
Thank you.

-
Prasun

Regards,
Prasun Kanti Dey
Ph.D. Candidate,
Dept of Electrical and Computer Engineering,
University of Central Florida
web: https://prasunkantidey.github.io/portfolio/






> On Jun 19, 2019, at 2:14 PM, William Herrin <bill at herrin.us> wrote:
> 
> On Wed, Jun 19, 2019 at 9:50 AM Prasun Dey <prasun at nevada.unr.edu <mailto:prasun at nevada.unr.edu>> wrote:
> > Iâ??m a Ph.D. candidate from University of Central Florida. I have a query, I hope you can help me with it or at least point me to the right direction.
> > Iâ??ve seen from PeeringDB that every ISP reveals its traffic ratio as Heavy/ Mostly Inbound or Balanced or Heavy/ Mostly Outbound. 
> > Iâ??m wondering if there is any specific ratio numbers for them. In Nortonâ??s Internet Peering Playbook or some other literary work, they mention the outbound:inbound traffic ratio as 1:1.2 to up to 1:3 for Balanced. But, I couldnâ??t find the other values.
> 
> Hi Prasun,
> 
> Ratio only masquerades as a technical term. It's whatever it takes to convince the other guy to set up settlement-free peering and you'll tweak your routing adjusting reality to match. The information in peeringdb is just a rough guide to help you figure out who to talk to as you try to adjust your traffic profile so that you can go after the big fish as "balanced."
> 
> Regards,
> Bill Herrin
> 
> 
> -- 
> William Herrin
> bill at herrin.us <mailto:bill at herrin.us>
> https://bill.herrin.us/ <https://bill.herrin.us/>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.nanog.org/pipermail/nanog/attachments/20190619/f2349a0d/attachment.html>