From henk at ripe.net Mon Aug 13 11:29:55 2007 From: henk at ripe.net (Henk Uijterwaal) Date: Mon, 13 Aug 2007 11:29:55 +0200 Subject: [ris-int] [Fwd: request for BGP Beacon] Message-ID: <46C02493.3040105@ripe.net> Hi, Setting up special beacon configs is something we used to do in the past. Morley's group does good work, so if at all possible, we should do this for her. Henk -------- Original Message -------- Subject: request for BGP Beacon Date: Wed, 08 Aug 2007 09:35:34 -0400 From: wingying at umich.edu To: henk at ripe.net CC: Z. Morley Mao , Y. Charlie Hu , Zheng Zhang Dear Henk, We are networking researchers in the University of Michigan and Purdue University. We are interested in doing experiments to emulate IP anycast which requires announcing the RIPE beacon prefix at more than one location at any given time. Would it be possible that you allow us to perform these experiments using one of the RIPE beacon prefixes for a limited time? We will certainly provide any software and operational support required to carry out these experiments. Can you help us set up this experiment testbed? Thanks very much for your help! Best, Ying -- ------------------------------------------------------------------------------ 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 ------------------------------------------------------------------------------ # Lawyer: "Now sir, I'm sure you are an intelligent and honest man--" # Witness: "Thank you. If I weren't under oath, I'd return the compliment." From vasco at ripe.net Mon Aug 13 12:30:09 2007 From: vasco at ripe.net (Vasco Asturiano) Date: Mon, 13 Aug 2007 12:30:09 +0200 Subject: [ris-int] [Fwd: request for BGP Beacon] In-Reply-To: <46C02493.3040105@ripe.net> References: <46C02493.3040105@ripe.net> Message-ID: <46C032B1.8000808@ripe.net> Hello Henk, Yes, they wrote to us last week with this beacon request. >From their e-mail we understood that they wanted to announce themselves one of the prefixes from the RIS beacons range. This would not be possible, as it would be against the RIPE assignment policies. So, we have mentioned to them that they would need to request a prefix from ARIN for this experiment. Perhaps we misunderstood and they were asking us to implement a special beacon config on our side, so they could conduct the experiment. That should be no problem (if there is enough beacon prefixes left, currently only one /24). I will reply and ask them to clarify on this. Thanks for signalling. :) Vasco Henk Uijterwaal wrote: > Hi, > > Setting up special beacon configs is something we used to do in the > past. Morley's group does good work, so if at all possible, we should > do this for her. > > Henk > > > > -------- Original Message -------- > Subject: request for BGP Beacon > Date: Wed, 08 Aug 2007 09:35:34 -0400 > From: wingying at umich.edu > To: henk at ripe.net > CC: Z. Morley Mao , Y. Charlie Hu > , Zheng Zhang > > Dear Henk, > We are networking researchers in the University of Michigan and Purdue > University. We are interested in doing experiments to emulate > IP anycast which requires announcing the RIPE beacon prefix > at more than one location at any given time. > Would it be possible that you allow us to perform these experiments > using one of the RIPE beacon prefixes for a limited time? > We will certainly provide any software and operational support required > to carry out these experiments. > Can you help us set up this experiment testbed? > > Thanks very much for your help! > Best, > Ying > > > -- Vasco Asturiano ------------------------- Information Services Dept. RIPE NCC http://www.ripe.net From eromijn at ripe.net Thu Aug 30 14:58:03 2007 From: eromijn at ripe.net (Erik Romijn) Date: Thu, 30 Aug 2007 14:58:03 +0200 Subject: [ris-int] RIS anycast beacon changes: Monday, 3 September 2007 Message-ID: <207295E0-E42B-468E-A280-310E9A9E9E8F@ripe.net> [Apologies for duplicates] Dear Colleagues, On Monday, 3 September 2007, we will modify the configuration of the anycast routing beacon (84.205.72.0/24) of the Routing Information Service (RIS). This will improve the usefulness of this beacon. The current configuration is that this beacon is announced and withdrawn every two hours (for example, announced at 00:00 and withdrawn at 02:00) on our collector connected to AMS-IX and NL-IX, and that it is announced permanently from our collector connected to LINX. As these locations are very close to each other, the usefulness of this beacon will increase by moving it to a different collector. Therefore, we will move its permanent announcement to our collector connected to PAIX. The RIS tools will not be affected by this work. For more information about the RIS routing beacons, please see: http://www.ripe.net/projects/ris/docs/beacon.html If you have any questions about this work, please send an e-mail to . Regards, Erik Romijn Information Services RIPE NCC