Hi, I'd like to ask your view on this request. At the moment there are no available beacon prefixes that can be used for this experiment. So, we need to decide if we wish to support this user in his research and if so, we need to submit a request to RS for a new RIS beacon IP range. What do you think? I informed the user that we are discussing this case internally and will let them know when we have a solution (or not). Thanks, Vasco Asturiano -------------------------- Software Engineering Dept. RIPE-NCC ----- Begin forwarded message ----- Date: Thu, 9 Feb 2006 15:20:21 +0000 (UTC) From: RIS Beacon Request User <risops@ripe.net> To: ris@ripe.net Subject: NCC#2006021124 RIS Lease-A-Beacon Request Message-Id: <20060209152021.D7D724B959@lama.ripe.net> name : Samantha Sau Man Lo contact : cssmlo@comp.polyu.edu.hk org : The Hong Kong Polytechnic University comments : We are studying properties of AS Path Prepending which is a popular inbound traffic engineering method. We propose an active measurement method to measure the impact of ASPP method under different prepending lengths and strategies. We applied it on a dual-homed, stub AS. We announce a prefix(/21) to both upstream ASes. But the announcement to one of the upstream AS, we applied different prepending length. After prepended once, we observe the route changes from different looking glasses (we have the script to collect the route changes from different looking glasses). However, we would like to perform the active measurement from other sites to see the effect. Here is the extended abstract appeared in ICNP2005: http://csr.bu.edu/icnp2005/Posters/Lo.pdf beacons : 2 RRC : RRC00 RRC : RRC01 RRC : RRC02 RRC : RRC03 RRC : RRC04 RRC : RRC05 RRC : RRC06 RRC : RRC07 RRC : RRC08 RRC : RRC10 RRC : RRC11 pattern : We would like prefix to have the following A/W pattern: Set1 (prepending on the link to AS20483) Day1 A: 00:00 : prepending length =0 W: 02:00 A: 04:00 : prepending length=1 W: 06:00 A: 08:00 : prepending length=2 W: 10:00 A: 12:00 : prepending length=3 W: 14:00 A: 16:00 : prepending length=4 W: 18:00 A: 20:00 : prepending length=5 W: 22:00 Day2 A: 00:00 : prepending length=6 W: 02:00 A: 04:00 : prepending length=7 W: 06:00 A: 08:00 : prepending length=8 W: 10:00 A: 12:00 : prepending length=9 W: 14:00 A: 16:00 : prepending length=10 W: 18:00 A: 20:00 : prepending length=11 W: 22:00 Day3 A: 00:00 : prepending length=10 W: 02:00 A: 04:00 : prepending length=9 W: 06:00 A: 08:00 : prepending length=8 W: 10:00 A: 12:00 : prepending length=7 W: 14:00 A: 16:00 : prepending length=6 W: 18:00 A: 20:00 : prepending length=5 W: 22:00 Day4 A: 00:00 : prepending length=4 W: 02:00 A: 04:00 : prepending length=3 W: 06:00 A: 08:00 : prepending length=2 W: 10:00 A: 12:00 : prepending length=1 W: 14:00 A: 16:00 : prepending length=0 W: 18:00 ------ Set2 (prepending on the link to AS3277) Day1 A: 00:00 : prepending length =0 W: 02:00 A: 04:00 : prepending length=1 W: 06:00 A: 08:00 : prepending length=2 W: 10:00 A: 12:00 : prepending length=3 W: 14:00 A: 16:00 : prepending length=4 W: 18:00 A: 20:00 : prepending length=5 W: 22:00 Day2 A: 00:00 : prepending length=6 W: 02:00 A: 04:00 : prepending length=7 W: 06:00 A: 08:00 : prepending length=8 W: 10:00 A: 12:00 : prepending length=9 W: 14:00 A: 16:00 : prepending length=10 W: 18:00 A: 20:00 : prepending length=11 W: 22:00 Day3 A: 00:00 : prepending length=10 W: 02:00 A: 04:00 : prepending length=9 W: 06:00 A: 08:00 : prepending length=8 W: 10:00 A: 12:00 : prepending length=7 W: 14:00 A: 16:00 : prepending length=6 W: 18:00 A: 20:00 : prepending length=5 W: 22:00 Day4 A: 00:00 : prepending length=4 W: 02:00 A: 04:00 : prepending length=3 W: 06:00 A: 08:00 : prepending length=2 W: 10:00 A: 12:00 : prepending length=1 W: 14:00 A: 16:00 : prepending length=0 W: 18:00 They are subjected to change. Sending host [158.132.12.81]. Agent Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1; .NET CLR 1.1.4322; InfoPath.1; .NET CLR 1.0.3705). ------ End forwarded message ------ --