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]/
[db-wg] Re: [ipv6-wg at ripe.net] RPSLng database deployment?
- Previous message (by thread): [db-wg] Re: [ipv6-wg at ripe.net] RPSLng database deployment?
- Next message (by thread): [db-wg] Re: [ipv6-wg at ripe.net] RPSLng database deployment?
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Daniel Roesen
dr at cluenet.de
Sat Oct 9 23:14:03 CEST 2004
On Sat, Oct 09, 2004 at 10:54:05PM +0200, Iljitsch van Beijnum wrote: > >I've never seen anyone actually using RtConfig output for anything > >else then destilling prefix/aspath lists from them in order to use > >those in own generator tools. Given my own very basic and short > >playing with RtConfig, I can somewhat understand why. > > It would make countless lives much easier if it were possible to submit > a query to the db that gives back the desired output rather than having > to use these very complex tools. Agreed, IRRd actually offers that. > That doesn't solve the problem that many people don't register their > stuff in the db very well, if at all, though. Well... my main gripe about all this is the lack of authorization control over route objects. For RIPE it's fine as you normally cannot register a route object without having the authorization of the IP space holder, but this doesn't hold true for all other IRR registries. Best regards, Daniel -- CLUE-RIPE -- Jabber: dr at cluenet.de -- dr at IRCnet -- PGP: 0xA85C8AA0
- Previous message (by thread): [db-wg] Re: [ipv6-wg at ripe.net] RPSLng database deployment?
- Next message (by thread): [db-wg] Re: [ipv6-wg at ripe.net] RPSLng database deployment?
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ db-wg Archives ]