Re: Peering Policies and Route Servers
Actually, only changes to the RADB and ANS DB will be caught by _every_ 4 hr update; the other databases (RIPE, MCI DB, CA*Net DB) are currently obtained 1x/day (usually in the morning, Brian Renaud says). Work re: synchronization and distribution of IRR data is, as they say, ongoing. Steve Richardson/Merit
From nanog-owner@merit.edu Tue Apr 30 13:16:30 1996 Message-Id: <199604301712.KAA03518@lint.cisco.com> X-Sender: pferguso@lint.cisco.com Date: Tue, 30 Apr 1996 13:13:36 -0400 To: Cengiz Alaettinoglu <cengiz@isi.edu> From: Paul Ferguson <pferguso@cisco.com> Subject: Re: Peering Policies and Route Servers Cc: Ali Marashi <amarashi@interglobe.com>, bmanning@isi.edu, nanog@merit.edu Sender: owner-nanog@merit.edu
At 10:12 AM 4/30/96 -0700, Cengiz Alaettinoglu wrote:
Route Servers are dynamic, they process upto 6000 routing updates a minute (see http://compute.merit.edu/stats/mae-east/instability).
Route Servers are reconfigured with up to date policy 6 times a day, i.e. every four hours. Hence, a brand new route registered in IRR may not be announced by the route servers to the NSPs whose policies are prefix based for up to at most 4 hours. I think this is what you are referring to.
Cengiz, thanks for the clarification.
- paul
Dear Steven,
Steven J. Richardson writes :
Actually, only changes to the RADB and ANS DB will be caught by _every_ 4 hr update; the other databases (RIPE, MCI DB, CA*Net DB) are currently obtained 1x/day (usually in the morning, Brian Renaud says). Work re: synchronization and distribution of IRR data is, as they say, ongoing.
Actually nearly real time distribution (not older then 10 minutes) of IRR data is already available since November last year (I wrote the code myself ;-)). The software has certainly still some rough edges and was published at the same time. It works now quite reliable for some time. You can contact me at <ripe-dbm@ripe.net> if you need more information or want to have such a mirror running at your site. Kind regards, David Kessens ----
Steve Richardson/Merit
From nanog-owner@merit.edu Tue Apr 30 13:16:30 1996 Message-Id: <199604301712.KAA03518@lint.cisco.com> X-Sender: pferguso@lint.cisco.com Date: Tue, 30 Apr 1996 13:13:36 -0400 To: Cengiz Alaettinoglu <cengiz@isi.edu> From: Paul Ferguson <pferguso@cisco.com> Subject: Re: Peering Policies and Route Servers Cc: Ali Marashi <amarashi@interglobe.com>, bmanning@isi.edu, nanog@merit.edu Sender: owner-nanog@merit.edu
At 10:12 AM 4/30/96 -0700, Cengiz Alaettinoglu wrote:
Route Servers are dynamic, they process upto 6000 routing updates a minute (see http://compute.merit.edu/stats/mae-east/instability).
Route Servers are reconfigured with up to date policy 6 times a day, i.e. every four hours. Hence, a brand new route registered in IRR may not be announced by the route servers to the NSPs whose policies are prefix based for up to at most 4 hours. I think this is what you are referring to.
Cengiz, thanks for the clarification.
- paul
participants (2)
-
David.Kessens＠ripe.net -
Steven J. Richardson