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 ]
Pawel Tyll
ptyll at nitronet.pl
Sun Jan 8 00:44:17 CET 2012
> That's a bit different from the initial point... Original point still stands - the fact that it's not a problem anymore to download 200MB over 200KB doesn't make it any less wasteful. > I do not know enough about irrd to comment on this (I just never > runned it here), the things we mirror here are MySQL backed and in > some way our sysadms convinced MySQL to accept that at some moment > some read-only tables get replaced on the fly with new snapshots and > that happens magically and atomically. Operative keyword would be 'magically'. I prefer KISS over magic :) > Maybe RIPE might put in some directory one file per day with the > "daily updates" and that directory can be rsync'd ? I'm not sure why we are still trying to re-invent wheel here. I would really like to hear a sane reason behind non-profit organization expecting a EUR 250 fee for access to, essentially, a whois server with public information that should be mirrored as much as possible, which also is already available for free, but in a form that is only harder to keep updated? I'm trying hard to imagine how running mirror with up to two weeks of serialized updates would be more cost-intensive compared to running FTP server, yet I can't figure this out. I was so perplexed by this that it even made me start this thread on a saturday! ;) > My point was only about the data transfer, I understand that setting > up a "push" update requires a significant administrative/management > overhead, and it is reasonable to ask for a cost compensation; setting > up a public rsync server requires no more effort than setting up a > public ftp site (maybe less...): the big dfference is that (as long as > data is uncompressed and unencrypted) only the "delta" gets actually > transferred. It's already up and running, this point is moot. Another user doesn't require a new set of data - same updates are being sent. It's also running on free and open software. It's also not a push update. From what I learned in short time this saturday, it's just a glorified whois server that allows mirror operation. Besides, others managed to somehow sink their astronomical costs with running such a contraption: http://www.radb.net/resources/databases.php Seriously, maybe I'm missing something here. But what? --Pawel.
- 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 ]