On Feb 17, 2016, at 5:04 PM, Owen DeLong <owen@delong.com> wrote:
The premise above therefore devolves to: Since most of the traffic is to those networks, then most of the bits flow over contracted peerings.
Perhaps “most” can be argued, but obviously a significant portion of all peering bits flow over contracted sessions. Hopefully we can all agree on that.
There’s greater complexity here, however…
Many of the bits that flow flow over several networks between their source and destination. Likely the vast majority of bits traverse at least 3 autonomous systems in the process.
So when you want to count traffic that went over a non-contract peering session vs. traffic that went over a contract peering session, how do you count traffic that traverses some of each?
Lower in my post: On Feb 16, 2016, at 10:31 AM, Patrick W. Gilmore <patrick@ianai.net> wrote:
I guess you could say the bits sent over transit will eventually hit a contracted peering session, since the people in the core contract their sessions. But does that matter to the small guys?
-- TTFN, patrick