Implementation of RIPE-181++

 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}
  * > 
  * > You must always apply rule 1 above. First make sure 10.0.0.0/8  and
  * > 15.0.0.0/8 are in AS2, otherwise they are not accepted. If they are
  * > then make list such that 15 is best a-b anf 10 best c-d and the rest
  * > of AS2 is equal through both links.
  * 
  * 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.

  * (You used "15 is best a-b" which does not explicitly say it is not
  * accepted on c-d).
  * 
  * 2)
  * If there was a third link (e, f) for which there is no interas-in
  * line. The policies for that link is:
  * 	networks in AS2 setminus {15.0.0.0/8} setminus {10.0.0.0/8}
  *
Nope - would be all AS2 but with adjusted prefs for 10 and 15.
 
  * Just wanted to make sure. I think this complicated interaction of
  * as-in and interas-in will be confused by a lot of people. Luckily only
  * few and hopefully more knowledgable people will actually specify
  * these.
  * 
I concur a little on the cofusion but for those who will use it it
will not be a big problem I would say.

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



-------- Logged at  Thu Sep 22 19:41:19 MET DST 1994  ---------