Implementation of RIPE-181++

Couldn't you express this with the interas-in attribute?

Say that the following addresses<->router mappsings are valid.
NAP
----
NAP1     AS1  192.141.10.1
NAP1     AS2  192.141.10.2
NAP2     AS1  192.142.10.1
NAP2     AS2  192.142.10.2
NAP3     AS1  192.143.10.1
NAP3     AS2  192.143.10.2



Then wouldn't the policy be...

aut-num: AS1
interas-in: from AS2 192.141.10.1 192.141.10.2 accept <metric> AS2
interas-in: from AS2 192.142.10.1 192.142.10.2 accept <metric> AS2
interas-in: from AS2 192.143.10.1 192.143.10.2 accept <metric> AS2 AND {10/8}


-Andy 

>	Just a question about the policy syntax and its implementation:
>
>o AS1 peers with AS2 at nap1, nap2, nap3
>o AS1 accept from AS2 the networks in AS100 at nap1, nap2, nap3
>o AS1 accept from AS2 the network {10/8} at nap3 *only*
>
>	- How do you express this policy with the RIPE-81++ syntax (as-in/
>	interas-in stuff...)
>	- What's the algorithm used to generate the filter list (list of nets
>	accepted) of AS1 at nap1, nap2, nap3
>
>		Laurent
>
>PS: A beer for the first one who gives me a good answer :)
>PS/2: I do not know the solution
-Andy 

>	(a revised version)
>	Just a question about the policy syntax and its implementation:
>
>o AS1 peers with AS2 at nap1, nap2, nap3
>o AS1 accept from AS2 the networks in AS100 at nap1, nap2, nap3
>o AS1 accept from AS2 the network {10/8} at nap3 *only*
>o 10/8 is not in AS100
>
>	- How do you express this policy with the RIPE-81++ syntax (as-in/
>	interas-in stuff...)
>	- What's the algorithm used to generate the filter list (list of nets
>	accepted) of AS1 at nap1, nap2, nap3
>
>		Laurent
>
>PS: A beer for the first one who gives me a good answer :)
>PS/2: I do not know the solution
>
>-- 
>Laurent



-------- Logged at  Tue Sep 20 16:26:40 MET DST 1994  ---------