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 <b...@herrin.us> wrote:
> 
> On Wed, Jun 19, 2019 at 9:50 AM Prasun Dey <pra...@nevada.unr.edu 
> <mailto:pra...@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
> b...@herrin.us <mailto:b...@herrin.us>
> https://bill.herrin.us/ <https://bill.herrin.us/>

Reply via email to