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/ipv6-wg@ripe.net/
[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 ]
Mark Prior
mrp at mrp.net
Mon Oct 11 12:54:07 CEST 2004
Iljitsch van Beijnum wrote: > On 9-okt-04, at 21:57, Daniel Roesen 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. Not a huge ISP but I certainly build my access list and route-maps (and the equivalent Procket policy stuff) using RtConfig with no other magic involved. In my previous job at one of Australia's tier ones we did it that way too. See AS7575 (current policy) and/or AS2764 (previous one) for outrageous aut-num objects. I don't use inet-rtr objects though. Personally I don't think driving RtConfig is all that difficult. Mark.
- 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 ]
[ ipv6-wg Archives ]