[ris-int] RIS Beacons

All,

At SIGCOMM 2004, it became clear that the current beacon prefixes suffer
from 2 problems:

 a) They have more peers giving transit than any other AS on the Internet.

 b) When a prefix is invisible, it is not clear if this is caused by
    an experimental problem or by the prefix being filtered.  The
    anchor prefix does not solve this problem, there should be one anchor
    per beacon.

So, people suggested that for the next period (1/10/2004-30/9/2005), we
make the following changes:

1. A new /19 is requested from the RIPE NCC.  This /19 is split into
   /24's.

2. Each RRC annouces 2 /24's.  Assuming A.B.Z is the base address

    A.B.(Z+2*Y).0/24
    A.B.(Z+2*Y+1).0/24

   For Y=0 to 13 for the (up to 16) RRC's.

   The first prefix is announced permanently.  The second one is a flapping
   prefix: up at 0 GMT, down at 2 GMT, up at 4 GMT etc.  The pattern may
   be changed at a later stage.

3. Inside each /24, a pingable address will be established.

4. We ask only 2 or 3 peers at each IX to provide transit for these
   prefixes.  (In other words, we do not ask everybody).

5. Other experiments that we do are:

   - An overflow prefix (prefix announced at 1 RRC, flapping at the next).
   - Hitesh's experiment.

6. The current 195.80.224.0/20 is returned to the RIPE NCC



Comments?

Henk




------------------------------------------------------------------------------
Henk Uijterwaal                           Email: henk.uijterwaal(at)ripe.net
RIPE Network Coordination Centre          http://www.amsterdamned.org/~henk
P.O.Box 10096          Singel 258         Phone: +31.20.5354414
1001 EB Amsterdam      1016 AB Amsterdam  Fax: +31.20.5354445
The Netherlands        The Netherlands    Mobile: +31.6.55861746
------------------------------------------------------------------------------

In a room with a window in the corner, I found truth.            (Ian Curtis)