nanog mailing list archives
Re: Trying to Make Sense of the Comcast/Level 3 Dispute
From: christian koch <ck () sandcastl es>
Date: Fri, 3 Dec 2010 10:34:06 -0800
my guess is the info for that was pulled off comcast's route server, where only tata is seen BGP routing table entry for 98.137.128.0/19, version 681406320 Paths: (8 available, best #8, table Default-IP-Routing-Table) Not advertised to any peer 6453 10310 36752 36752, (received & used) 68.86.1.43 (metric 72251) from 68.86.80.5 (68.86.1.5) Origin IGP, metric 0, localpref 250, valid, internal Community: 7922:43 7922:3050 7922:3120 Originator: 68.86.1.43, Cluster list: 68.86.1.5 6453 10310 36752 36752, (received & used) 68.86.1.40 (metric 78885) from 68.86.80.15 (68.86.1.15) Origin IGP, metric 0, localpref 250, valid, internal Community: 7922:40 7922:3050 7922:3120 Originator: 68.86.1.40, Cluster list: 68.86.1.15 6453 10310 36752 36752, (received & used) 68.86.1.41 (metric 85042) from 68.86.80.7 (68.86.1.7) Origin IGP, metric 0, localpref 250, valid, internal Community: 7922:41 7922:3050 7922:3120 Originator: 68.86.1.41, Cluster list: 68.86.1.7, 68.86.1.13 6453 10310 36752 36752, (received & used) 68.86.1.44 (metric 101555) from 68.86.80.10 (68.86.1.10) Origin IGP, metric 0, localpref 250, valid, internal Community: 7922:44 7922:3050 7922:3120 Originator: 68.86.1.44, Cluster list: 68.86.1.10 6453 10310 36752 36752, (received & used) 68.86.1.42 (metric 70822) from 68.86.80.0 (68.86.1.0) Origin IGP, metric 0, localpref 250, valid, internal Community: 7922:42 7922:3050 7922:3120 Originator: 68.86.1.42, Cluster list: 68.86.1.0 6453 10310 36752 36752, (received & used) 68.86.1.41 (metric 85042) from 68.86.80.13 (68.86.1.13) Origin IGP, metric 0, localpref 250, valid, internal Community: 7922:41 7922:3050 7922:3120 Originator: 68.86.1.41, Cluster list: 68.86.1.13 6453 10310 36752 36752, (received & used) 68.86.80.11 (metric 92374) from 68.86.80.11 (68.86.1.11) Origin IGP, metric 0, localpref 250, valid, internal Community: 7922:11 7922:3050 7922:3120 6453 10310 36752 36752, (received & used) 68.86.1.46 (metric 65585) from 68.86.80.2 (68.86.1.2) Origin IGP, metric 0, localpref 250, valid, internal, best Community: 7922:46 7922:3050 7922:3120 Originator: 68.86.1.46, Cluster list: 68.86.1.2 On Fri, Dec 3, 2010 at 9:30 AM, Matthew Petach <mpetach () netflight com>wrote:
On Fri, Dec 3, 2010 at 6:49 AM, Leo Bicknell <bicknell () ufp org> wrote:In a message written on Wed, Dec 01, 2010 at 09:40:01PM -0800, PaulFerguson wrote:Interesting article:http://www.freedom-to-tinker.com/blog/sjs/trying-make-sense-comcast-level-3- -disputeHere's an excellent summary, complete with some pictures:http://www.voxel.net/blog/2010/12/peering-disputes-comcast-level-3-and-you-- Leo Bicknell - bicknell () ufp org - CCIE 3440 PGP keys at http://www.ufp.org/~bicknell/Unfortunately, they got at least part of the diagram wrong; Yahoo uses Global Crossing to reach Comcast, not TATA. Matt
Current thread:
- Trying to Make Sense of the Comcast/Level 3 Dispute Paul Ferguson (Dec 01)
- Re: Trying to Make Sense of the Comcast/Level 3 Dispute Christopher Morrow (Dec 01)
- Re: Trying to Make Sense of the Comcast/Level 3 Dispute Leo Bicknell (Dec 02)
- Re: Trying to Make Sense of the Comcast/Level 3 Dispute Leo Bicknell (Dec 03)
- RE: Trying to Make Sense of the Comcast/Level 3 Dispute Dennis Burgess (Dec 03)
- Re: Trying to Make Sense of the Comcast/Level 3 Dispute Matthew Petach (Dec 03)
- Re: Trying to Make Sense of the Comcast/Level 3 Dispute christian koch (Dec 03)
- Re: Trying to Make Sense of the Comcast/Level 3 Dispute Patrick W. Gilmore (Dec 03)
- Re: Trying to Make Sense of the Comcast/Level 3 Dispute Matthew Petach (Dec 03)