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 ]
Joao Damas
Joao_Damas at isc.org
Mon Oct 11 15:38:42 CEST 2004
On 9 Oct, 2004, at 23:14, Daniel Roesen wrote: > 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. > Hmm, that's interesting. Last time I checked the RIPE server provided the same features (except for route-set expansion, mainly due to the fact that when rpsl was defined it was not entirely clear how the expansion was to be performed). To the best of my recollection no one has ever manifested interest in having the RIPE server do that. Joao
- 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 ]