Hi, at the RIS meeting a couple of months ago I asked if it would make sense to reserve one or more IPv4 beacon prefixes for my fancy beacon ("as-set stuffing") experiments. However, there are very few prefixes left out of the new /19 that has been assigned to beacons. The new scheme envisages a /24 beacon prefix and a /24 anchor prefix for each RRC. So for the 13 currently active RRCs we use 26 prefixes out of the 32. But the current list of beacon prefix assignments ( http://www.ripe.net/projects/ris/docs/beaconlist.html ) lists two more beacons, one for K-root anycast failover, and one for anycast server research (requested by hitesh@cs.cornell.edu). If these were to need an anchor prefix each, we would be up to 30 prefixes out of the 32 we have. Therefore: - If possible, I would like to reserve two prefixes for as-set stuffing experiments - I think we should consider requesting more address space for beacons. With this arrangement, the address space we have would be completely maxed out from the start. So if, for example, the Dubai RRC were ever to come online, we wouldn't have a prefix to announce there. Or if another researcher were to request a custom beacon, we wouldn't have one to give them. Thoughts? Cheers, Lorenzo