Mods to ripe181?

>Peval recognizes and evaluates policy expressions that contain limited
>as path expressions. That is all.

This is useful for generating configuration based on such policy registed in
the RADB.  Great that this done.  But it won't help to regist the policy to 
the RADB at first which is what Peval will be based on and is I needed.  

>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.

That is the same as what suggested in my previous message.  Except that
I suggest to use cisco's aspath notation which is widely understood by 
providers.  As I mentioned in my first message, we may talked about this
before but it has not been done to change the express syntax to allow
people regist their policy.  I brought this up now again because I am not
able to regist people's policy.  I got routing policy from Alternet and
Sprint and really had difficulty to regist them in the RADB.

So can we agree on the extended syntax and implement them?

						--Jessica




-------- Logged at  Mon Feb 6 18:55:01 MET 1995  ---------