Implementation of RIPE-181++

Tony Bates (Tony.Bates at ripe.net) on September 22:
> 2) You have more policy in as-in than described in interas-in.
> 
>    The polices not specifically defined in interas-in but mentioned in
> as-in are deemed equal across all interas-in peers/links. TO WORK IT
> IS THE DIFFERENCE OF THE AS-IN MINUS THE SET OF INTERAS-INS AND WHAT IS
> LEFT IS SHARED ACROSS THE LINKS/PEERS. This implies adding to basic
> list generated for interas-in lines.

Tony Bates (Tony.Bates at ripe.net) on September 22:
> 
>  cengiz at ISI.EDU (Cengiz Alaettinoglu) writes:
>   * 
>   * Tony Bates (Tony.Bates at ripe.net) on September 22:
>   * > 3) You have something like AS granularity in as-in and some network
>   * > granularity in interas-in. i.e.
>   * > 
>   * > as-in: ASX 100 AS2
>   * > interas-in: ASX a b blah {15.0.0.0/8}
>   * > interas-in: ASX c d blah {10.0.0.0/8}

THE DIFFERENCE OF AS-IN MINUS THE SET OF INTERAS-INS
AS2 minus ({15.0.0.0/8} or {10.0.0.0/8})

so both {15.0.0.0/8} and {10.0.0.0/8} are not shared.
this is consistent with what Marten said the other day.
Right Marten? 

Perhaps the above algorithm is wrong.

>   * Wanted to clarify two points:
>   * 1)
>   * {15.0.0.0/8} is not accepted at all on (c d).
>   * {10.0.0.0/8} is not accepted at all on (a b).
>   * 
> No - it is accepted but with pref as noted. Global policy means we
> cannot make this assumption. You can easily write it down more
> explicitly if you wanted the above effect.

Please do so.

Please also specify the following policy. 
AS1 accepts AS100,AS200 from AS2. 
On link (a,b), it only accepts AS100 
(i.e. it does NOT accept AS200 on this link). 
On link (c,d), it only accepts AS200 
(i.e. it does NOT accept AS100 on this link). 
This is the revisited barnet example of Elise.

Cengiz

-- 
Cengiz Alaettinoglu       Information Sciences Institute
cengiz at isi.edu            University of Southern California




-------- Logged at  Fri Sep 23 16:24:00 MET DST 1994  ---------