Mods to ripe181?
Cengiz Alaettinoglu
Sat Feb 4 00:04:10 CET 1995
Jessica Yu (jyy at merit.edu) on February 3: > I'd like to hear what's in peval. Will it help people to regist the policy > described in my example? It is nice to be able to config it but what also > needed is to allow people to regist this thing in the format of ripe181. > > --Jessica Peval recognizes and evaluates policy expressions that contain limited as path expressions. That is all. The part that is missing is how one can register policies with such expressions. Earlier we have aggreed on the following: Have four new policy lines: extended-as-in extended-as-out extended-interas-in extended-interas-out that have the same syntax as the corresponding non-extended ones except that they allow general as path expressions (some of which is not recognized by peval yet) in them. Eg. extended-as-in: AS1 100 accept AS2 OR {1.1.1.1/32} OR <AS1 . *> AND COMM_NSF_AUP (peval can actually evaluate the above line). If a domain registers an aut-num object that has at least one extended policy line, the non-extended policy lines are ignored by the tools that know about the extended stuff, otherwise they work with the non-extended lines. For the benefit of the older tools, we would reccomend administrators to register both extended and non-extended policies where possible. When all the tools are upgraded and we reach a concensus, we might remove the non-extended policy lines. Oh, by the way, as-exclude becomes extended-as-in: ... AND NOT <.* AS1 .*> Regarding the issue of dangerous, topology dependent as paths, we will reccomend administrators not to use such expression unless necessary. I will probably work on this after nanog and send the document to the group for review. Initial feedback is welcome. Cengiz -- Cengiz Alaettinoglu Information Sciences Institute Voice: (310) 822-1511 University of Southern California -------- Logged at Sun Feb 5 17:58:54 MET 1995 ---------
[ rr-impl Archive ]