Implementation of RIPE-181++

Sorry for a late feedback. I was out sick yesterday.
I have three comments:

Tony Bates (Tony.Bates at ripe.net) on October  4:
> 
>  Daniel Karrenberg <Daniel.Karrenberg at ripe.net> writes:
>   * 
> Okay, thanks for your changes. I have incorperated them and added a
> small note on the slitting ASes. Find below he revised text. 
> 
> 	
> 		--Tony.
> 
> P.S. Today is really the last day to comment before we send this
> document out as ripe-181.


1. It is clear from the yesterday's discussion that the interaction of
   interas-in/out and as-in/out is still not clear. Ripe-181 would
   hang itself with this document:-(

> as-in  or  as-out  policy.  When a sub-set is described remember the
> remaining routes are implicitly shared across all connections. It is

2. I agree with Jessica. See the example below:

as-in: AS1 100 AS100 AS200
interas-in: AS1 L1-R1 (pref=100) NOT AS100

assume there is also another connection called L2-R2.

In this case:
Global policy: AS100 AS200
Combined local policy: NOT AS100 = ANY setminus AS100 
difference: {AS100 AS200} setminus {ANY setminus AS100} = AS100

SURPRISE 1
	AS100 is accepted with equal preference on both links. 
SURPRISE 2
	AS200 is not accepted on neither of the links.

If this is what is intended, the document is correct, no need for
corrections. 

If this is not what is intended, the document is VERY WRONG. I am
afraid this is the case.

> The implicit rule that all routes not mentioned in interas  policies
> are  accepted on all links with equal preference ensures the desired
> result.

3. What is this preference value. A random number? The value in as-in
   line? 

If it is not a random number, document needs to say that.

Cengiz

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




-------- Logged at  Wed Oct 5 19:52:53 MET 1994  ---------