This is a proven maneuver and Cogent is not the first to do it.
i guess that without knowing who else these de-peered networks are customers
of, it's hard for an outsider to guess which ratios into cogent's network by
other peers will improve as a result of de-peering these networks. had you
at http://www.e-gerbil.net/cogent-t1r there is a plain text document with
the following HTTP headers:
Date: Fri, 28 Sep 2007 21:56:34 GMT
Server: Apache/2.2.3 (Unix) PHP/5.2.3
Last-Modified: Fri, 28 Sep 2007 19:15:53 GMT
ETag: 92c1e1-a85-43b36ea5bcc40
at http://www.e-gerbil.net/cogent-t1r there is a plain text document
with
the following HTTP headers:
Date: Fri, 28 Sep 2007 21:56:34 GMT
Server: Apache/2.2.3 (Unix) PHP/5.2.3
Last-Modified: Fri, 28 Sep 2007 19:15:53 GMT
ETag: 92c1e1-a85-43b36ea5bcc40
On Fri, Sep 28, 2007 at 10:00:41PM +, Paul Vixie wrote:
[snip]
the second plain text assertion which caught my eye was:
Why is this happening? There are a few possibilities. First, Cogent
may simply want revenue from the networks it has de-peered, in the
form of
Randy Epstein [EMAIL PROTECTED] wrote:
Clearly you can see the article was published by T1R in their Daily T1R
report: http://www.t1r.com/
(listed under The Daily T1R Headlines)
If you subscribe to the Daily T1R, you can find Dan's report issued today.
Sorry, T1R.com requires Flash 8 or
Paul,
This is the scenario. Peer B is send lots of outbound to Peer A.
Peer A depeers Peer (well former Peer) B. Why? Well, Peer A is having
ratio problems with other Peers C-F. Keep reading...
After depeering, some of (now former) Peer B's outbound traffic to
Peer A will now flow over
I don't know that NLayer was depeered yesteray for a fact, although
someone I trust did report that to me. I do know for a fact that
Limelight was. No offense to the good folk at nLayer, but most of the
people who I work for care a good bit more about Limelight
Didn't know about VW