This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/[email protected]/
[members-discuss] RIPE DB NRTM access.
- Previous message (by thread): [members-discuss] RIPE DB NRTM access.
- Next message (by thread): [members-discuss] RIPE DB NRTM access.
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Jørgen Hovland
jorgen at ssc.net
Sat Jan 7 20:42:08 CET 2012
Den 1/7/12 6:12 PM, skrev Pawel Tyll: > Hello people (and ticket bots :>), > > I wanted to do some BGP filtering automation today, learned some > interesting things in the process. I decided on setting up a local > mirror of RIPE IRR and was quite puzzled with reasoning behind this: > > http://www.ripe.net/data-tools/db/nrtm-mirroring > > So, I can download the whole database snapshot for free from > ftp.ripe.net, wasting bandwidth and other resources, or on the > other hand I can pay for doing things the right and efficient way, > which in the process is effectively cheaper for all involved parties. > > So the question is - what gives? :) - why does RIPE insist that I > download>200MB of compressed data instead of catching up probably few > hundred KB of daily changes? > > --Pawel. I'm quite sure it is more expensive to administrate and receive a stream of changes than downloading a static file with no administration:) Bandwidth is cheap and static content scales extremely well.
- Previous message (by thread): [members-discuss] RIPE DB NRTM access.
- Next message (by thread): [members-discuss] RIPE DB NRTM access.
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]