Mark Prior wrote:
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.
I have the same feeling. RPSL (and its ng variant) tend to become more complex (but hay life in terms of policy is complex too). So you need to invest almost 2 man months to have everything expressed in RPSL. Inet-rtr is too much for ISP operations and to be frank I do not beleive that irtr can be realistic in terms of description of a real life situation. I do not beleive that router configuration is terms of interface configurartion needs automatic tools. I beleive that the routing policy automatic configuration sould be our mission. I do not want to boast over what we have succeeded in GRNET. We have managed to describe our real life but yet complex policy in RPSL. All of our clients have either private or public AS. The route-maps and ACL are generated by RTConfig. Dimitrios,
Mark.
-- -- Dimitrios K. Kalogeras Electrical Engineer Ph.D. Network Manager NTUA/GR-Net Network Management Center _____________________________________ icq: 11887484 voice: +30-210-772 1863 fax: +30-210-772 1866 e-mail: D.Kalogeras@noc.ntua.gr pub 1024D/F2A69A72 2002-12-13 Dimitrios Kalogeras <D.Kalogeras@noc.ntua.gr> Key fingerprint = 64C5 646D 8D33 A3FF 14D1 66C6 5127 54CC F2A6 9A72