ntacpeering - Akamai Routes on TR-CPS
Subject: NTAC Peering Working Group
List archive
- From: Michael H Lambert <>
- To:
- Subject: Akamai Routes on TR-CPS
- Date: Wed, 19 Sep 2012 17:26:51 -0400
In looking at the TR-CPS routing table, I see a number of routes with 20940
(Akamai) in the AS path. The vast majority of these are NOT "^11164 20940
.*". I can't imagine that these other destinations would serve content to
random sources in our community, so is there any reason that they should be
accepted into the routing table? I could imagine their presence leading to
some weird return paths. I'm assuming that "^11164 20940$" would work as
expected.
Michael
- Akamai Routes on TR-CPS, Michael H Lambert, 09/19/2012
- Re: Akamai Routes on TR-CPS, John Hernandez, 09/19/2012
- Re: Akamai Routes on TR-CPS, Darrell Newcomb, 09/19/2012
- Re: Akamai Routes on TR-CPS, David Farmer, 09/19/2012
- Re: Akamai Routes on TR-CPS, Darrell Newcomb, 09/19/2012
- Re: Akamai Routes on TR-CPS, Michael H Lambert, 09/19/2012
- Re: Akamai Routes on TR-CPS, David Farmer, 09/19/2012
Archive powered by MHonArc 2.6.16.