Is it time for this nanog thread again?
http://www.merit.edu/mail.archives/nanog/msg02822.html
srs
On Fri, Feb 29, 2008 at 11:45 PM, Henry Futzenburger
<[EMAIL PROTECTED]> wrote:
> 1. Accept only default and partial routes from upstream.
> a. Accept directly-connected routes, reject everyth
On Feb 29, 2008, at 11:49 AM, David Ulevitch wrote:
Of course... In fact, wouldn't it even providers benefit from having
some logic that says "don't ever accept a more specific of a
customer-announced prefix?"
Sure, that'd suck less, I guess, although then you have to punch
holes for mul
Henry,
In my past experience with the SUP2/MSFC2 combo you are best off with
option 2. Minimize the FIB entry of what you control like BGP route
entries. You never know what can happen to cause the FIB to run up again
and cause the CPU to spike.
Manolo
Henry Futzenburger wrote:
I am hopi
On Fri, 29 Feb 2008, Henry Futzenburger wrote:
> 2. Accept only default and RIR minimum routes from upstream.
> a. Filter based on RIR minimums, rely on default for unaggregated
> routes.
> b. Assume a reduction of about 50,000-100,000 total routes.
>
> Does anyone have any opinions as t
Danny McPherson wrote:
On Feb 29, 2008, at 7:46 AM, David Ulevitch wrote:
It's worth noting that from where I sit, it appears as though none of
Youtube's transit providers accepted this announcement. Only their
peers.
A simple artifact of shortest AS path route selection.
Well, we (yout
On Thu, Feb 28, 2008 at 12:28:39PM -0700, Blake Pfankuch wrote:
> AboveNet is experiencing a network event.
Why does that remind me of "rain event" in
http://youtube.com/watch?v=DagVklB4VHQ
http://youtube.com/watch?v=UjKciefHo38
?
:-)
Sorry for off-topic,
best regards,
Daniel
--
CLUE-RIPE --
I am hoping to help an ISP keep a couple of Cisco 6500's with SUP2's in
production for a while longer. They are currently just about at the FIB
limit of 250,000 entries, mostly composed of BGP routes. I'm considering
two alternatives to reduce the number of entries.
1. Accept only default and pa
On Fri, Feb 29, 2008 at 06:46:15AM -0800, David Ulevitch wrote:
> The point is -- Restrictive customer filtering can also bite you in the
> butt. Trying to require your providers to do a "ge 19 le 25" (or
> whatever your largest supernet is), rather than filters for specific
> prefix sizes see
Hi!
The CIDR Report:
Recent Table History
Date PrefixesCIDR Agg
22-02-08251555 162505
23-02-08251796 163136
24-02-08251963 163643
25-02-08252045 163871
26-02-08252278 159794
27-02-082
On Feb 29, 2008, at 7:46 AM, David Ulevitch wrote:
The report states:
Sunday, 24 February 2008, 20:07 (UTC): AS36561 (YouTube) starts
announcing 208.65.153.0/24. With two identical prefixes in the
routing system, BGP policy rules, such as preferring the shortest
AS path, determine whi
On Thu, Feb 28, 2008 at 07:04:21PM -0500, John Dvorak wrote:
> Anyone aware if this is causing any bleedover to Sprint? Seeing massive
> delays
> (~280+ ms) and drops between Relay, MD (144.232.15.2) and San Jose
> (144.232.8.145).
According to AboveNet, the routing instability has a temporary
As recently suggested, ARIN has made the requested changes to produce a
new histogram. It can be found at:
http://www.arin.net/statistics/index.html#ipv4org.
Note, this is the same link as the old histogram so you may need to
refresh your browser's cache.
Regards,
Leslie Nobile
Director,
The report states:
Sunday, 24 February 2008, 20:07 (UTC): AS36561 (YouTube) starts announcing 208.65.153.0/24. With two identical prefixes in the routing system, BGP policy rules, such as preferring the shortest AS path, determine which route is chosen. This means that AS17557 (Pakistan Telecom
for those interested in the matter
tom
Dear Colleagues,
As you may be aware from recent news reports, traffic to the youtube.com
website was 'hijacked' on a global scale on Sunday, 24 February 2008. The
incident was a result of the unauthorised announcement of the prefix
208.65.153.0/24
This report has been generated at Fri Feb 29 21:14:41 2008 AEST.
The report analyses the BGP Routing Table of AS2.0 router
and generates a report on aggregation potential within the table.
Check http://www.cidr-report.org for a current version of this report.
Recent Table History
Date
BGP Update Report
Interval: 28-Jan-08 -to- 28-Feb-08 (32 days)
Observation Point: BGP Peering with AS2.0
TOP 20 Unstable Origin AS
Rank ASNUpds % Upds/PfxAS-Name
1 - AS949872828 1.3% 59.9 -- BBIL-AP BHARTI BT INTERNET LTD.
2 - AS24731 57987
16 matches
Mail list logo
