From henk at ripe.net Fri Oct 1 11:25:14 2004 From: henk at ripe.net (Henk Uijterwaal (RIPE NCC)) Date: Fri, 1 Oct 2004 11:25:14 +0200 (CEST) Subject: [ris-int] some notes regarding myasn... In-Reply-To: <20040930133016.GA32375@virgin.ww.net> References: <20040930133016.GA32375@virgin.ww.net> Message-ID: On Thu, 30 Sep 2004, Alexis Yushin wrote: > Hi, > > Yesterday, in the brewery, I understood from Henk that you guys are > going to have a myasn meeting somewhere in the near future. I thought it > might be usefull if I send in some ideas of what needs to be > done/implemented. I'm also looking for a new contract right now and I > would be quite willing to work on myasn again :) Either way I hope that > my input helps. Thanks! Henk > > Cheers, > Alexis > > > Prio 1. > > - bugfixes/feature implementation (obvious) > > - proper authentication module (with logout option) > > - optimization/clean-up myasn-scan/myasn-send/myasn-admin > move the functionality of these programs into respective > RIPE::NCC::myASn::Scan RIPE::NCC::myASn::Send > (this will untie lots of knots and make myasn much more > extendable) > > - reimplement XML import with XML::DOM > and use as DTD > > - enable retromatch (will be trivial after myasn-scan reimplemented as perl > interface; retromatch is already in there but requires a rather resource > inefficient invokation of myasn-scan) > > - handle notification mail bounces/errors with some inteligence > > - graphical (.png) summary on the start page > > > Prio 2. > > - prefix independent alarms with complex (multi-part) regular expressions > (this is one most important and powerfull feature that will make myasn usefull > for much larger range of applications) > > - site global alarm groups with possibility to subscribe to them > (martians system/default route) > > - visibility alarms > > - churn based alarms > > - snmp alarm notifications > > - pgp signing of notification messages (usefull?) > > Prio 3. > > - auto sync with IRR and LIR portal (for prefixes and as numbers) > > - self tuning alarms > ------------------------------------------------------------------------------ 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) From henk at ripe.net Fri Oct 1 11:26:03 2004 From: henk at ripe.net (Henk Uijterwaal (RIPE NCC)) Date: Fri, 1 Oct 2004 11:26:03 +0200 (CEST) Subject: [ris-int] some notes regarding myasn... In-Reply-To: <20040930133016.GA32375@virgin.ww.net> References: <20040930133016.GA32375@virgin.ww.net> Message-ID: Matthew, Can you set up a meeting with Shane, Ziya et.al. to discuss this list plus any other feedback we got @ R49? Henk On Thu, 30 Sep 2004, Alexis Yushin wrote: > Hi, > > Yesterday, in the brewery, I understood from Henk that you guys are > going to have a myasn meeting somewhere in the near future. I thought it > might be usefull if I send in some ideas of what needs to be > done/implemented. I'm also looking for a new contract right now and I > would be quite willing to work on myasn again :) Either way I hope that > my input helps. > > Cheers, > Alexis > > > Prio 1. > > - bugfixes/feature implementation (obvious) > > - proper authentication module (with logout option) > > - optimization/clean-up myasn-scan/myasn-send/myasn-admin > move the functionality of these programs into respective > RIPE::NCC::myASn::Scan RIPE::NCC::myASn::Send > (this will untie lots of knots and make myasn much more > extendable) > > - reimplement XML import with XML::DOM > and use as DTD > > - enable retromatch (will be trivial after myasn-scan reimplemented as perl > interface; retromatch is already in there but requires a rather resource > inefficient invokation of myasn-scan) > > - handle notification mail bounces/errors with some inteligence > > - graphical (.png) summary on the start page > > > Prio 2. > > - prefix independent alarms with complex (multi-part) regular expressions > (this is one most important and powerfull feature that will make myasn usefull > for much larger range of applications) > > - site global alarm groups with possibility to subscribe to them > (martians system/default route) > > - visibility alarms > > - churn based alarms > > - snmp alarm notifications > > - pgp signing of notification messages (usefull?) > > Prio 3. > > - auto sync with IRR and LIR portal (for prefixes and as numbers) > > - self tuning alarms > ------------------------------------------------------------------------------ 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) From ziya at ripe.net Fri Oct 1 15:38:23 2004 From: ziya at ripe.net (Ziya Suzen) Date: Fri, 1 Oct 2004 15:38:23 +0200 Subject: [ris-int] Re: FW: myASN code walk-through In-Reply-To: <00ff01c4a70a$946bc9a0$1f0200c1@rockstar> References: <00ff01c4a70a$946bc9a0$1f0200c1@rockstar> Message-ID: <20041001133823.GU10616@x33.ripe.net> On 2004-09-30 18:28:55 +0000, Matthew Williams wrote: > Hi Ziya, > > Olaf Maennel at the Technical University of Munich is helping us out with ideas for future myASn alarms. I know this is short > notice, but when would you have time for a conf call with Olaf and a student of his? 3.30 is fine with me. -- Ziya > > Olaf Maennel wrote: > > do you have some time for a conf call on Tuesday, Oct 05 at 3pm or > > 3:30pm? > > I'm meeting Florian Hauer, the student working on myASN. If > > time permits > > on your side for a quick(*) walk through the latest version of the > > myASN code that would be very helpful, because Florian could > > participate. What do you think? > > Cheers, > Matthew From matthew at ripe.net Fri Oct 1 16:25:46 2004 From: matthew at ripe.net (Matthew Williams) Date: Fri, 1 Oct 2004 16:25:46 +0200 Subject: [ris-int] RE: FW: myASN code walk-through In-Reply-To: <20041001133823.GU10616@x33.ripe.net> Message-ID: <006201c4a7c2$8a675ba0$1f0200c1@rockstar> Ziya wrote: > > with ideas for future myASn alarms. I know this is short > notice, but > > when would you have time for a conf call with Olaf and a student of > > his? > > 3.30 is fine with me. Cool :) Olaf, so conf call on Tuesday, Oct 05 at 3:30pm, then? Cheers, Matthew From matthew at ripe.net Fri Oct 1 16:48:58 2004 From: matthew at ripe.net (Matthew Williams) Date: Fri, 1 Oct 2004 16:48:58 +0200 Subject: [ris-int] RE: FW: myASN code walk-through In-Reply-To: <006201c4a7c2$8a675ba0$1f0200c1@rockstar> Message-ID: <007101c4a7c5$c847c880$1f0200c1@rockstar> Facilities with analogue line are booked then :( Other alternatives? Cheers, Matthew > -----Original Message----- > From: ris-int-admin at ripe.net [mailto:ris-int-admin at ripe.net] > On Behalf Of Matthew Williams > Sent: 01 October 2004 16:26 > To: 'Ziya Suzen'; 'Olaf Maennel' > Cc: ris-int at ripe.net > Subject: [ris-int] RE: FW: myASN code walk-through > > > Ziya wrote: > > > with ideas for future myASn alarms. I know this is short > > notice, but > > > when would you have time for a conf call with Olaf and a > student of > > > his? > > > > 3.30 is fine with me. > > Cool :) > > Olaf, so conf call on Tuesday, Oct 05 at 3:30pm, then? > > Cheers, > Matthew > > From olaf at maennel.net Fri Oct 1 22:30:13 2004 From: olaf at maennel.net (Olaf Maennel) Date: Fri, 1 Oct 2004 22:30:13 +0200 Subject: [ris-int] Re: FW: myASN code walk-through In-Reply-To: <006201c4a7c2$8a675ba0$1f0200c1@rockstar> References: <20041001133823.GU10616@x33.ripe.net> <006201c4a7c2$8a675ba0$1f0200c1@rockstar> Message-ID: <20041001203013.GA5266@net.informatik.tu-muenchen.de> Hi Matthew, yes, that's perfect! Thanks! We have time until 16:00 (so we should not waste too much time to setup the conf call :-)). We can call you (number?) or you can all us (+49 89 289 18037). olaf On Fri, Oct 01, 2004 at 04:25:46PM +0200, Matthew Williams wrote: > Ziya wrote: > > > with ideas for future myASn alarms. I know this is short > > notice, but > > > when would you have time for a conf call with Olaf and a student of > > > his? > > > > 3.30 is fine with me. > > Cool :) > > Olaf, so conf call on Tuesday, Oct 05 at 3:30pm, then? > > Cheers, > Matthew > > -- From matthew at ripe.net Sun Oct 3 22:16:47 2004 From: matthew at ripe.net (Matthew Williams) Date: Sun, 3 Oct 2004 22:16:47 +0200 Subject: [ris-int] Re: FW: myASN code walk-through In-Reply-To: <20041001203013.GA5266@net.informatik.tu-muenchen.de> Message-ID: <00fa01c4a985$e8f1ed10$aba8a8c0@rockstar> I'm sorry, Olaf. The equipment and room are taken during Tue afternoon for interviews. We'll have to reschedule... :( Cheers, Matthew > -----Original Message----- > From: ris-int-admin at ripe.net [mailto:ris-int-admin at ripe.net] > On Behalf Of Olaf Maennel > Sent: 01 October 2004 22:30 > To: Matthew Williams > Cc: 'Ziya Suzen'; ris-int at ripe.net > Subject: [ris-int] Re: FW: myASN code walk-through > > > Hi Matthew, > > yes, that's perfect! Thanks! > > We have time until 16:00 (so we should not waste too much > time to setup the conf call :-)). We can call you (number?) > or you can all us (+49 89 289 18037). > > olaf > > > On Fri, Oct 01, 2004 at 04:25:46PM +0200, Matthew Williams wrote: > > Ziya wrote: > > > > with ideas for future myASn alarms. I know this is short > > > notice, but > > > > when would you have time for a conf call with Olaf and > a student > > > > of > > > > his? > > > > > > 3.30 is fine with me. > > > > Cool :) > > > > Olaf, so conf call on Tuesday, Oct 05 at 3:30pm, then? > > > > Cheers, > > Matthew > > > > > > -- > From olaf at maennel.net Tue Oct 5 14:01:55 2004 From: olaf at maennel.net (Olaf Maennel) Date: Tue, 5 Oct 2004 14:01:55 +0200 Subject: [ris-int] Re: FW: myASN code walk-through In-Reply-To: <00fa01c4a985$e8f1ed10$aba8a8c0@rockstar> References: <00fa01c4a985$e8f1ed10$aba8a8c0@rockstar> Message-ID: <200410051401.55850.olaf@maennel.net> Hi Matthew, okay, let's fix another date.... olaf On Sunday 03 October 2004 22:16, Matthew Williams wrote: > I'm sorry, Olaf. The equipment and room are taken during Tue > afternoon for interviews. We'll have to reschedule... :( > > Cheers, > Matthew > > > -----Original Message----- > > From: ris-int-admin at ripe.net [mailto:ris-int-admin at ripe.net] > > On Behalf Of Olaf Maennel > > Sent: 01 October 2004 22:30 > > To: Matthew Williams > > Cc: 'Ziya Suzen'; ris-int at ripe.net > > Subject: [ris-int] Re: FW: myASN code walk-through > > > > > > Hi Matthew, > > > > yes, that's perfect! Thanks! > > > > We have time until 16:00 (so we should not waste too much > > time to setup the conf call :-)). We can call you (number?) > > or you can all us (+49 89 289 18037). > > > > olaf > > > > On Fri, Oct 01, 2004 at 04:25:46PM +0200, Matthew Williams wrote: > > > Ziya wrote: > > > > > with ideas for future myASn alarms. I know this is short > > > > > > > > notice, but > > > > > > > > > when would you have time for a conf call with Olaf and > > > > a student > > > > > > > of > > > > > his? > > > > > > > > 3.30 is fine with me. > > > > > > Cool :) > > > > > > Olaf, so conf call on Tuesday, Oct 05 at 3:30pm, then? > > > > > > Cheers, > > > Matthew > > > > -- From henk at ripe.net Thu Oct 7 12:30:12 2004 From: henk at ripe.net (Henk Uijterwaal (RIPE NCC)) Date: Thu, 7 Oct 2004 12:30:12 +0200 (CEST) Subject: [ris-int] suggestions for beacons (fwd) Message-ID: Hi, Mainly FYI. I like the idea but I'm not sure about all the consequences. Will talk to Morley, 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) ---------- Forwarded message ---------- Date: Mon, 4 Oct 2004 14:36:52 -0400 (EDT) From: Z. Morley Mao To: "Henk Uijterwaal (RIPE NCC)" Subject: suggestions for beacons Hi Henk, Paul Francis, Ramesh Govindan, and I wrote this draft for setting up a BGP Lab combining the RIPE beacons with other beacons. Please see the attachment for more details. Basically, we would like to allow programmable access to the beacons for researchers, so that it is easier to perform experiments. We plan to provide the software to enable such access. We would love to hear any comments you may have. Thank you very much! --Morley -------------- next part -------------- BGP Lab Vision Statement -------------------------- Goal: ===== The goal of the BGP Lab is to allow interested BGP researchers to perform BGP experiments with unassigned prefixes and observe the routing and data plane behavior from multiple vantage points. BGP Lab will provide "virtual BGP speakers" to individual researchers, allowing them to independently control the operation of the virtual BGP speaker and its associated set of prefixes. In essence, BGP Lab will be the PlanetLab equivalent for BGP research. Like PlanetLab, BGP Lab will motivate growth in the size of the experimental infrastructure, because researchers will see benefit in donating resources. Specifically, BGPLab will consolidate the two largest beacon projects (PSG and RIPE) into a single project to share resources and promote novel BGP research. Background: ========== Both the PSG BGP Beacons project (http://psg.com/~zmao/BGPBeacon.html) and RIPE Beacons project (http://psg.com/~zmao/BGPBeacon.html) currently do not allow researchers direct control of their operation. Rather, each researcher must ask the beacon controllers to do whatever setup is necessary to run an experiment. This is a serious bottleneck, and has resulted in multiple independent beacon projects. Since many BGP experiments (see below) benefit from having multiple BGP speakers working together, or from having BGP speakers in different regions of the globe, this partitioning of beacon projects detracts from the type and scope of BGP experiments. The BGP beacons are hosted by various parties primarily in the USA, while RIPE becaons are hosted at RIPE RIS exchange points, primarily in Europe. Most of the RIPE beacons are connected to multiple upstream providers and simultaneously advertised by all these providers. Requirements: ============ Software: Current BGP Beacon software is available here: http://psg.com/~zmao/Software/ The software needs to accommodate flexible control of the prefix advertisement schedule, type of the update, and update attributes on a per-peer basis. To allow multiple users to control different prefixes advertised from the same location, the software can be configured to control individual prefixes separately. The software will provide separation of authority between virtual BGP speakers, e.g., one researcher may not influence the advertisements of another researcher's prefixes. The software must also impose limitations on each virtual BGP speakers operation, for instance the frequency of advertisements and the correctness of the BGP messages. Towards these ends, BGP Lab software will follow the model of PlanetLab. That is, the local administrator will have root access for the machines themselves. A BGP Lab administrator will have access to the global parameters of the BGP Lab software itself, and have the ability to add and delete individual BGP Lab user accounts and set parameters for each user (i.e. which address prefixes they may use). The individual BGP Lab users will have control over a "slice" of the BGP Lab software. Specifically, they will be able to control BGP parameters associated with the address prefixes that they have been assigned. Support from ISPs: First, immediate upstream providers must support this effort by propagating the routing announcements of the Beacon prefixes, which cannot be aggregated. Ideally, the immediate providers would provide information on the route flap damping parameter setting on the internal routers, so that the schedule of the Beacon prefixes are adjusted accordingly to minimize the probability of route suppression by flap damping. It would be very helpful to adjust the import filter policies of the ISPs as well, so that the attributes of the Beacon prefix are preserved as much as possible. For example, oftentimes, ISPs filter community attributes, which can be used to signal selective advertisement of the prefixes, especially if the prefix is connected to multiple upstream providers. Beyond the first hop immediate ISP, other ISPs also need to accept the Beacon prefix update and not aggregate the prefixes, so that the advertisement are globally visible. Support to allow selective advertisement is very useful by agreeing on the community attributes used. Support from Address Registries: One or more Address Registries (AR) must agree to allocate blocks of unused prefixes and an AS number to BGP Lab. The idea is that the Address Registry would officially still own the addresses and AS number, and could take them back on very short notice. An AS number may not strictly necessary for the Beacon experiments, as the AS numbers from the sites hosting the beacon prefixes can be used as origin AS. Resources: ========== Address blocks: unused address blocks are needed for contructing Beacon prefixes. Prefixes need to be at least of size /24, otherwise, they run the risk of being filtered. Machine with remote log in: at the Beacon hosting site, there needs to be a machine allowing remote access to control advertisement schedule and update format. Machine in the address space of the Beacon prefix: ideally, there should be a machine within the address space of the Beacon prefix. This is useful for both debugging purposes (to check if the route to the prefix is available) and for experiment purposes (e.g., to study the data plane performance during routing changes). BGPLab Experiments: ================== Route Dynamics: The existing beacons are used to study the propagation of routing updates through the infrastructure. BGPLab would allow larger scale studies over longer periods of time. Validating Fault Isolation: Root-cause analysis is an active area of research, and BGPLab would greatly facilitate the validation of schemes for proposed techniques. IP anycast: In order to determine the effects of large scale IP anycast deployment (for instance to scale and protect root DNS servers), it must be necessary to dynamically control and coordinate the IP address blocks advertised from BGP speakers situated in many locations around the globe. Quality of aggregation: By inserting controlled combinations of aggregatable and non-aggregatable prefixes into BGP from various locations around the globe, we can measure the quality of effect of BGP aggregation. BGP operational validation: beacons can be used to understand various BGP operational behavior. For instance, both operators and researchers would be interested in understanding the operational effect of setting various BGP-related parameters (e.g., MinRouteAdvertisementInterval Timer, Route flap Damping parameters), From henk at ripe.net Thu Oct 7 15:49:10 2004 From: henk at ripe.net (Henk Uijterwaal (RIPE NCC)) Date: Thu, 7 Oct 2004 15:49:10 +0200 (CEST) Subject: [ris-int] Re: suggestions for beacons In-Reply-To: References: Message-ID: Hi Morley, > Paul Francis, Ramesh Govindan, and I wrote this draft for setting up a > BGP Lab combining the RIPE beacons with other beacons. Please see the > attachment for more details. Basically, we would like to allow > programmable access to the beacons for researchers, so that it is easier > to perform experiments. We plan to provide the software to enable such > access. 1) How many users do you expect for this facility: 1, 10, 100, 1000? O(1) is fine, O(10) doable, O(100) will require a major administrative effort from somebody. 2) Our route collectors are there to collect routes, in order to get the data for the tools that our users use (myASn, BGPlay, all the queries). That's the number 1 priority for them, everything else (including the beacons) is a by-product. The problem with giving out accounts and have people configure their own prefix, is that people can misconfigure things. If this results in a lot of BGP activity, then this will cause people to loose confidence in the RIS project and perhaps even dropping peering sessions. That is a bad thing. So-far, we have never given any account to anybody, except for own operations, so we can control what is running on the box. This proposal would change that completely. 3) We have quagga running on the box to collect and announce routes, you have your own software. I'm not sure if they can coexist (but we can find out). 4) Address blocks: the RIR's all have a policy for temporary address assignments. I'm not sure, but I don't think that they allow us to have a large number of used /24's on the shelf. As far as I can see, these policies do not allow for temporary AS# assignments, this might be an oversight, but fixing it will take time. Bottom line: I like the concept but it will need a lot of thought regarding the practical implications. (Cc'ing some of my colleagues, who may want to add something). 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) From ris-request at ripe.net Fri Oct 8 16:42:50 2004 From: ris-request at ripe.net (RIPE NCC RIS) Date: Fri, 08 Oct 2004 16:42:50 +0200 Subject: [ris-int] NCC#2004093307 [195.80.224.0/24 not flapping?] Message-ID: <200410081442.i98EgrKh018274@x45.ripe.net> Hi all, I'd like to ask an advice on this case. This is about a peering session at RRC0 with AS7018 (12.0.1.63). They're saying that they recently do not receive the announcements/withdrawals of the beacon prefix 195.80.224.0/24. Apparently, the last time they noticed the flapping of this prefix was in the beginning of June 2004. In fact, looking at the RIS database, we can see the daily updates of the other RRC0 peers for 195.80.224.0/24, but none from AS7018. The peering session with them has been up for about 3 weeks. How can we check whether the BGP updates are being sent to them or not? Thanks, Vasco ----- Begin forwarded message ----- Date: Wed, 29 Sep 2004 18:18:40 -0400 From: Jay Borkenhagen To: rispeering at ripe.net Subject: NCC#2004093307 195.80.224.0/24 not flapping? Cc: Aman Shaikh Message-Id: <16731.13504.826194.244753 at oz.mt.att.com> Hi, We've got a BGP session from our 12.0.1.63 to your 193.0.4.28. I thought that 195.80.224.0/24 was supposed to oscillate based on the schedule at http://www.ripe.net/ris/beaconlist.html, but I haven't seen that prefix flap since sometime in early June 2004. Below I'll include what I've got now. Jay B. route-spews#show ip bgp sum [...] 193.0.4.28 4 12654 16 2163875 45600521 0 0 1w6d 2 [...] route-spews#show ip bgp nei 193.0.4.28 routes BGP table version is 45601230, local router ID is 12.0.1.63 Status codes: s suppressed, d damped, h history, * valid, > best, i - internal, S Stale Origin codes: i - IGP, e - EGP, ? - incomplete Network Next Hop Metric LocPrf Weight Path *> 195.80.224.0 193.0.4.28 0 100 0 12654 i *> 195.80.239.0 193.0.4.28 0 100 0 12654 i Total number of prefixes 2 route-spews#show ip bgp 195.80.224.0/24 BGP routing table entry for 195.80.224.0/24, version 32179320 Paths: (2 available, best #1) Advertised to update-groups: 1 3 4 12654, (aggregated by 64536 10.34.183.128) 193.0.4.28 from 193.0.4.28 (193.0.4.28) Origin IGP, metric 0, localpref 100, valid, external, best Community: 7018:2000 12654, (aggregated by 64536 10.34.183.128), (received-only) 193.0.4.28 from 193.0.4.28 (193.0.4.28) Origin IGP, metric 0, localpref 100, valid, external route-spews#show ip bgp 195.80.239.0/24 BGP routing table entry for 195.80.239.0/24, version 32179323 Paths: (2 available, best #1) Advertised to update-groups: 1 3 4 12654, (aggregated by 64512 10.255.255.255) 193.0.4.28 from 193.0.4.28 (193.0.4.28) Origin IGP, metric 0, localpref 100, valid, external, best Community: 7018:2000 12654, (aggregated by 64512 10.255.255.255), (received-only) 193.0.4.28 from 193.0.4.28 (193.0.4.28) Origin IGP, metric 0, localpref 100, valid, external route-spews# -- Jay Borkenhagen jayb at att.com AT&T Internet Services ------ End forwarded message ------ -- -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 206 bytes Desc: not available URL: From info at proauction.ltd.uk Mon Oct 11 08:23:07 2004 From: info at proauction.ltd.uk (Minola Smoked Products) Date: Mon, 11 Oct 2004 07:23:07 +0100 Subject: [ris-int] Attn: Factory Manager Message-ID: <8xtypozksvcu1awyntbvjd8yi5cpsu> An HTML attachment was scrubbed... URL: From matthew at ripe.net Tue Oct 12 20:12:43 2004 From: matthew at ripe.net (Matthew Williams) Date: Tue, 12 Oct 2004 20:12:43 +0200 Subject: [ris-int] Web Access Report for the Routing Information Service - August, 2004 Message-ID: <000801c4b087$11659500$1f0200c1@rockstar> Hi All, The monthly RIS Web Access Report is available at the following URL: http://iii.ripe.net/np/WWW082004_RIS.pdf Please comment on oddities. Cheers, Matthew Ps. The report will later be moved to: http://iii.ripe.net/sed/ris/reports/www/ --- > Matthew Williams (MW243-RIPE) > Customer Liaison Engineer > RIPE NCC - http://www.ripe.net/np/ -------------- next part -------------- A non-text attachment was scrubbed... Name: WWW082004_RIS.pdf Type: application/pdf Size: 182537 bytes Desc: not available URL: From matthew at ripe.net Fri Oct 15 19:47:13 2004 From: matthew at ripe.net (Matthew Williams) Date: Fri, 15 Oct 2004 19:47:13 +0200 Subject: [ris-int] Web Access Report for the Routing Information Service - September, 2004 Message-ID: <00a401c4b2df$00ef4b30$aba8a8c0@rockstar> Hi All, We have another monthly RIS Web Access Report available at the following URL: http://iii.ripe.net/np/WWW092004_RIS.pdf Please comment on oddities. Cheers, Matthew Ps. Future location: http://iii.ripe.net/sed/ris/reports/www/ --- > Matthew Williams (MW243-RIPE) > Customer Liaison Engineer > RIPE NCC - http://www.ripe.net/np/ -------------- next part -------------- A non-text attachment was scrubbed... Name: WWW092004_RIS.pdf Type: application/pdf Size: 342991 bytes Desc: not available URL: From henk at ripe.net Mon Oct 18 09:53:20 2004 From: henk at ripe.net (Henk Uijterwaal (RIPE NCC)) Date: Mon, 18 Oct 2004 09:53:20 +0200 (CEST) Subject: [ris-int] Meeting? Message-ID: Do we have/need a meeting this morning? 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) From shane at ripe.net Mon Oct 18 09:59:03 2004 From: shane at ripe.net (Shane Kerr) Date: Mon, 18 Oct 2004 09:59:03 +0200 Subject: [ris-int] Meeting? In-Reply-To: References: Message-ID: <417377C7.3060609@ripe.net> Henk Uijterwaal (RIPE NCC) wrote: > Do we have/need a meeting this morning? The only issue that I want to know about it the under-spec Moscow RRC, but if there's no more information then there's no reason to meet. -- Shane Kerr RIPE NCC From henk at ripe.net Mon Oct 18 09:59:59 2004 From: henk at ripe.net (Henk Uijterwaal (RIPE NCC)) Date: Mon, 18 Oct 2004 09:59:59 +0200 (CEST) Subject: [ris-int] Meeting? In-Reply-To: <417377C7.3060609@ripe.net> References: <417377C7.3060609@ripe.net> Message-ID: On Mon, 18 Oct 2004, Shane Kerr wrote: > Henk Uijterwaal (RIPE NCC) wrote: > > Do we have/need a meeting this morning? > > The only issue that I want to know about it the under-spec Moscow RRC, but > if there's no more information then there's no reason to meet. I haven't seen anything since the last email exchange. 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) From matthew at ripe.net Mon Oct 18 10:46:28 2004 From: matthew at ripe.net (Matthew Williams) Date: Mon, 18 Oct 2004 10:46:28 +0200 Subject: [ris-int] Meeting? In-Reply-To: Message-ID: <010501c4b4ee$f5a1e320$1f0200c1@rockstar> Called Elena. She's just back from hols and has a lot of catching up to do. I was promised an email by the end of the day. FYI: she also mentioned visiting Amsterdam in Nov. Cheers, Matthew > -----Original Message----- > From: ris-int-admin at ripe.net [mailto:ris-int-admin at ripe.net] > On Behalf Of Henk Uijterwaal (RIPE NCC) > Sent: 18 October 2004 10:00 > To: Shane Kerr > Cc: ris-int at ripe.net > Subject: Re: [ris-int] Meeting? > > > On Mon, 18 Oct 2004, Shane Kerr wrote: > > > Henk Uijterwaal (RIPE NCC) wrote: > > > Do we have/need a meeting this morning? > > > > The only issue that I want to know about it the under-spec > Moscow RRC, > > but if there's no more information then there's no reason to meet. > > I haven't seen anything since the last email exchange. > > 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) > From wilhelm at ripe.net Mon Oct 18 18:02:56 2004 From: wilhelm at ripe.net (Rene Wilhelm) Date: Mon, 18 Oct 2004 18:02:56 +0200 Subject: Request: keep ris-int in Cc [was Re: [ris-int] NCC#2004093307 [195.80.224.0/24 not flapping?] In-Reply-To: Message from RIPE NCC RIS of "Fri, 08 Oct 2004 16:42:50 +0200." <200410081442.i98EgrKh018274@x45.ripe.net> Message-ID: <200410181602.i9IG2ux1012166@birch.ripe.net> Hi, Just a request: when a thread is started on ris-int could all who reply please keep ris-int in Cc: ? Cleaning up my inbox, I was wondering myself what the status was, not having seen any reply to Vasco's request for advice. Now going through the xrtt ticketing system, I see messages with headers like To: RIPE NCC RIS Cc: james at ripe.net, matthew at ripe.net, arife at ripe.net shouldn't that have been "Cc:ris-int" instead of personal e-mails? wasn't the ris-int list created for exactly that purpose? Cheers, -- Rene From zmao at eecs.umich.edu Tue Oct 19 08:04:51 2004 From: zmao at eecs.umich.edu (Z. Morley Mao) Date: Tue, 19 Oct 2004 02:04:51 -0400 (EDT) Subject: [ris-int] Re: suggestions for beacons In-Reply-To: References: Message-ID: Hi Henk, Sorry for the delayed reply on this. > > Paul Francis, Ramesh Govindan, and I wrote this draft for setting up a > > BGP Lab combining the RIPE beacons with other beacons. Please see the > > attachment for more details. Basically, we would like to allow > > programmable access to the beacons for researchers, so that it is > > easier to perform experiments. We plan to provide the software to > > enable such access. > > 1) How many users do you expect for this facility: 1, 10, 100, 1000? > O(1) is fine, O(10) doable, O(100) will require a major administrative > effort from somebody. I think O(10) is our initial goal. I understand your concern of scaling it to O(100). But for now, if we can have five or six researchers able to share the BGP lab infrastructure, that would be great! > 2) Our route collectors are there to collect routes, in order to get the > data for the tools that our users use (myASn, BGPlay, all the queries). > That's the number 1 priority for them, everything else (including the > beacons) is a by-product. The problem with giving out accounts and have > people configure their own prefix, is that people can misconfigure > things. If this results in a lot of BGP activity, then this will cause > people to loose confidence in the RIS project and perhaps even dropping > peering sessions. That is a bad thing. > > So-far, we have never given any account to anybody, except for own > operations, so we can control what is running on the box. This proposal > would change that completely. I understand your concern. One way to ensure that the beacon experiments will not affect the collection of routes and other important operations is by restricting the software that controls the route injection. We can impose the control by rate-limiting how often the beacon prefix can be changed, what type of announcement is allowed. I believe we can accommodate all your concerns by restricting the type and frequency of the operations performed by the users of the bgp lab. > 3) We have quagga running on the box to collect and announce routes, > you have your own software. I'm not sure if they can coexist (but we can > find out). I believe we can develop the software to ensure that it does not affect the operation of Quagga. > 4) Address blocks: the RIR's all have a policy for temporary address > assignments. I'm not sure, but I don't think that they allow us to have a > large number of used /24's on the shelf. As far as I can see, these > policies do not allow for temporary AS# assignments, this might be an > oversight, but fixing it will take time. > > Bottom line: I like the concept but it will need a lot of thought > regarding the practical implications. Yes, I agree. Perhaps the best way to move forward is to have a conference call to discuss these concerns? Paul and Ramesh, would you be interested in joining the call? Thanks! --Morley > (Cc'ing some of my colleagues, who may want to add something). > > > 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) > From shane at ripe.net Tue Oct 19 10:19:27 2004 From: shane at ripe.net (Shane Kerr) Date: Tue, 19 Oct 2004 10:19:27 +0200 Subject: Request: keep ris-int in Cc [was Re: [ris-int] NCC#2004093307 [195.80.224.0/24 not flapping?] In-Reply-To: <200410181602.i9IG2ux1012166@birch.ripe.net> References: <200410181602.i9IG2ux1012166@birch.ripe.net> Message-ID: <4174CE0F.8030606@ripe.net> Rene Wilhelm wrote: > Hi, > > Just a request: when a thread is started on ris-int could all who > reply please keep ris-int in Cc: ? > > Cleaning up my inbox, I was wondering myself what the status was, > not having seen any reply to Vasco's request for advice. Now going > through the xrtt ticketing system, I see messages with headers like > > To: RIPE NCC RIS > Cc: james at ripe.net, matthew at ripe.net, arife at ripe.net > > shouldn't that have been "Cc:ris-int" instead of personal e-mails? > wasn't the ris-int list created for exactly that purpose? I don't know. The ris-int list was around before I was. The reason that people were e-mailed directly is that nobody responded to requests for help, IIRC. This is typical for group lists - nothing bad, but it actually was necessary to get some feedback here. -- Shane Kerr RIPE NCC From matthew at ripe.net Tue Oct 19 14:19:20 2004 From: matthew at ripe.net (Matthew Williams) Date: Tue, 19 Oct 2004 14:19:20 +0200 Subject: [ris-int] Installation CD for RRC13 Message-ID: <001701c4b5d5$dcd589e0$1f0200c1@rockstar> Hi there, Thanks for getting the RRC in place. BTW, did receive the installation cd that Bruce Campbell sent you a while ago? Kind regards, Matthew From henk at ripe.net Tue Oct 19 16:15:48 2004 From: henk at ripe.net (Henk Uijterwaal (RIPE NCC)) Date: Tue, 19 Oct 2004 16:15:48 +0200 (CEST) Subject: [ris-int] Re: suggestions for beacons In-Reply-To: References: Message-ID: Hi Morley, > Yes, I agree. Perhaps the best way to move forward is to have a > conference call to discuss these concerns? Let me discuss this internally here first, 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) From zmao at eecs.umich.edu Tue Oct 19 16:20:54 2004 From: zmao at eecs.umich.edu (Z. Morley Mao) Date: Tue, 19 Oct 2004 10:20:54 -0400 (EDT) Subject: [ris-int] Re: suggestions for beacons In-Reply-To: References: Message-ID: Sounds good. If you could come up with a list of concerete requirements and concerns we should address with our beacon management software, that would be great. Thanks again! -Morley On Tue, 19 Oct 2004, Henk Uijterwaal (RIPE NCC) wrote: > Hi Morley, > > > Yes, I agree. Perhaps the best way to move forward is to have a > > conference call to discuss these concerns? > > Let me discuss this internally here first, > > 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) > From elin at ripn.net Thu Oct 21 10:08:11 2004 From: elin at ripn.net (Elena P. Voronina) Date: Thu, 21 Oct 2004 12:08:11 +0400 (MSD) Subject: [ris-int] Re: Installation CD for RRC13 In-Reply-To: <001701c4b5d5$dcd589e0$1f0200c1@rockstar> References: <001701c4b5d5$dcd589e0$1f0200c1@rockstar> Message-ID: <20041021120518.J48195@argo.ripn.net> Hello, i'm very sorry, but we din't receive CD. Sincerely, Elena On Tue, 19 Oct 2004, Matthew Williams wrote: > Hi there, > > Thanks for getting the RRC in place. > > BTW, did receive the installation cd that Bruce Campbell sent you a while ago? > > Kind regards, > Matthew > > From matthew at ripe.net Thu Oct 21 14:24:48 2004 From: matthew at ripe.net (Matthew Williams) Date: Thu, 21 Oct 2004 14:24:48 +0200 Subject: [ris-int] RE: Installation CD for RRC13 In-Reply-To: <20041021120518.J48195@argo.ripn.net> Message-ID: <000301c4b768$f5260d50$1f0200c1@rockstar> Hi Elena, It seems that Bruce sent you the CD with express mail from NL shortly after the RIPE meeting. I could ask our OPS department to make an ISO image available via ftp, or alternatively, have a new one sent to your attention via DHL this time ;) What suites you? Kind regards, Matthew > -----Original Message----- > From: Elena P. Voronina [mailto:elin at ripn.net] > Sent: 21 October 2004 10:08 > To: Matthew Williams > Cc: 'Timakin Vladimir'; ris-int at ripe.net; 'Bruce Campbell' > Subject: Re: Installation CD for RRC13 > > > > Hello, > > i'm very sorry, but we din't receive CD. > > Sincerely, Elena > > > On Tue, 19 Oct 2004, Matthew Williams wrote: > > > Hi there, > > > > Thanks for getting the RRC in place. > > > > BTW, did receive the installation cd that Bruce Campbell sent you a > > while ago? > > > > Kind regards, > > Matthew > > > > > From elin at ripn.net Thu Oct 21 14:38:22 2004 From: elin at ripn.net (Elena P. Voronina) Date: Thu, 21 Oct 2004 16:38:22 +0400 (MSD) Subject: [ris-int] RE: Installation CD for RRC13 In-Reply-To: <000301c4b768$f5260d50$1f0200c1@rockstar> References: <000301c4b768$f5260d50$1f0200c1@rockstar> Message-ID: <20041021163009.Y97610@argo.ripn.net> Hello, On Thu, 21 Oct 2004, Matthew Williams wrote: > Hi Elena, > > It seems that Bruce sent you the CD with express mail from NL shortly after the RIPE meeting. I could ask our OPS department to make unfortunately, we didn't receive this mail. > an ISO image available via ftp, or alternatively, have a new one sent to your attention via DHL this time ;) It doesn't matter. We can take file via ftp, if it is convenient for you. Elena > > What suites you? > > Kind regards, > Matthew > > > -----Original Message----- > > From: Elena P. Voronina [mailto:elin at ripn.net] > > Sent: 21 October 2004 10:08 > > To: Matthew Williams > > Cc: 'Timakin Vladimir'; ris-int at ripe.net; 'Bruce Campbell' > > Subject: Re: Installation CD for RRC13 > > > > > > > > Hello, > > > > i'm very sorry, but we din't receive CD. > > > > Sincerely, Elena > > > > > > On Tue, 19 Oct 2004, Matthew Williams wrote: > > > > > Hi there, > > > > > > Thanks for getting the RRC in place. > > > > > > BTW, did receive the installation cd that Bruce Campbell sent you a > > > while ago? > > > > > > Kind regards, > > > Matthew > > > > > > > > > > From matthew at ripe.net Thu Oct 21 14:47:55 2004 From: matthew at ripe.net (Matthew Williams) Date: Thu, 21 Oct 2004 14:47:55 +0200 Subject: [ris-int] R: rrc13 installation CD briefly publicly available as ISO image via ftp Message-ID: <200410211247.i9LCltx1015324@birch.ripe.net> Hereby I wish to request a service from Operations. Detailed description: --------------------- [ Please provide us with all relevant information ] installation CD lost in mail. can we provide ISO via ftp? Cheers, Matthew Regards, Matthew Williams From engin at ripe.net Thu Oct 21 17:12:47 2004 From: engin at ripe.net (Engin Gunduz) Date: Thu, 21 Oct 2004 17:12:47 +0200 Subject: [ris-int] new url for ris pages? Message-ID: <20041021151245.GE15838@x47.ripe.net> Hi Webmaster, What is the new URL for, for example http://www.ripe.net/ripencc/pub-services/np/ris/rrc01.html ? There are broken links from http://www.ris.ripe.net/cgi-bin/rrcstatus.cgi Thanks, -engin From matthew at ripe.net Thu Oct 21 17:50:56 2004 From: matthew at ripe.net (Matthew Williams) Date: Thu, 21 Oct 2004 17:50:56 +0200 Subject: [ris-int] RE: [ripe.net #105795] R: rrc13 installation CD briefly publicly available as ISO image via ftp In-Reply-To: Message-ID: <002c01c4b785$c0e47eb0$1f0200c1@rockstar> Hi there, > At ops everyone presumed these were shipped together with the > machines. No, this request concerns a customised installation CD for a Remote Route Collector that's already in Moscow. James, who has been working on this deployment, should know the details. Cheers, Matthew > -----Original Message----- > From: Miriam Schoon via RT [mailto:ops at ripe.net] > Sent: 21 October 2004 16:54 > To: matthew at ripe.net > Subject: Re: [ripe.net #105795] R: rrc13 installation CD > briefly publicly available as ISO image via ftp > > > On Thu, Oct 21, 2004 at 02:47:55PM +0200, Matthew Williams wrote: > > > installation CD lost in mail. can we provide ISO via ftp? > > Hi Matthew, > > Are these cd's shipped seperately? > At ops everyone presumed these were shipped together with the > machines. > > Thanks, > > -- > Miriam Schoon | miriam at ripe.net > RIPE NCC | Support Technician > From webmaster at ripe.net Fri Oct 22 13:59:00 2004 From: webmaster at ripe.net (RIPE NCC Webmaster) Date: Fri, 22 Oct 2004 13:59:00 +0200 Subject: [ris-int] Re: new url for ris pages? In-Reply-To: Your message of Thu, 21 Oct 2004 17:12:47 +0200. <20041021151245.GE15838@x47.ripe.net> References: <20041021151245.GE15838@x47.ripe.net> Message-ID: <200410221159.i9MBx0x1030993@birch.ripe.net> Hi, Engin Gunduz writes: * * Hi Webmaster, * What is the new URL for, for example * * http://www.ripe.net/ripencc/pub-services/np/ris/rrc01.html ? * * There are broken links from http://www.ris.ripe.net/cgi-bin/rrcstatus.cgi All these should point to: http://www.ripe.net/ris/docs/~ as in: http://www.ripe.net/ris/docs/rrc01.html Cheers, Jeroen * * Thanks, * -engin * From matthew at ripe.net Fri Oct 22 15:28:31 2004 From: matthew at ripe.net (Matthew Williams) Date: Fri, 22 Oct 2004 15:28:31 +0200 Subject: [ris-int] RE: [ripe.net #105795] R: rrc13 installation CD briefly publicly available as ISO image via ftp In-Reply-To: Message-ID: <015301c4b83b$06387100$aba8a8c0@rockstar> Hi there, > Unfortunately, James is out of the country. Yes, I know. He is at FICIX, but won't he be back on Monday? > Could you give me some more details? This bootable cd will install a plain vanilla Debian distribution + a software router (Quagga) + looking glass + mysql and some in-house code needed for data insertion on a remote route collector (to be). The server in Moscow will become rrc13. > What files, who might know more about this and so on? I am not sure how good the relationship between BC and the higher echelons of ops is nowadays, but he does definitely know more about the CD than I. Bruce, could you help us out? Otherwise, I'm fine with waiting until Monday. Have a good weekend. Cheers, Matthew > -----Original Message----- > From: Miriam Schoon via RT [mailto:ops at ripe.net] > Sent: 22 October 2004 14:59 > To: matthew at ripe.net > Subject: Re: [ripe.net #105795] R: rrc13 installation CD > briefly publicly available as ISO image via ftp > > > On Thu, Oct 21, 2004 at 05:50:56PM +0200, Matthew Williams wrote: > > > > At ops everyone presumed these were shipped together with the > > > machines. > > > > No, this request concerns a customised installation CD for a Remote > > Route Collector that's already in Moscow. James, who has > been working > > on this deployment, should know the details. > > Hi Matthew, > > Unfortunately, James is out of the country. > > Could you give me some more details? > What files, who might know more about this and so on? > > Thanks, > > -- > Miriam Schoon | miriam at ripe.net > RIPE NCC | Support Technician > From vasco at ripe.net Fri Oct 22 15:30:43 2004 From: vasco at ripe.net (Vasco Asturiano) Date: Fri, 22 Oct 2004 15:30:43 +0200 Subject: [ris-int] RRC00 down Message-ID: <20041022153043.1d6ba6cf.vasco@ripe.net> Hello all, I just noticed that RRC00 is currently down, apparently since yesterday at around 08:00. The host is reachable but Quagga doesn't seem to respond. In the case that the downtime wasn't planned, BGPd probably needs to be restarted. Is there a procedure for this operation? Thanks, Vasco From bruce.campbell at ripe.net Fri Oct 22 15:35:22 2004 From: bruce.campbell at ripe.net (Bruce Campbell) Date: Fri, 22 Oct 2004 15:35:22 +0200 (CEST) Subject: [ris-int] RE: [ripe.net #105795] R: rrc13 installation CD briefly publicly available as ISO image via ftp In-Reply-To: <015301c4b83b$06387100$aba8a8c0@rockstar> References: <015301c4b83b$06387100$aba8a8c0@rockstar> Message-ID: On Fri, 22 Oct 2004, Matthew Williams wrote: > > Could you give me some more details? > > What files, who might know more about this and so on? Miriam, the instructions for generating the image are at: http://iii.ripe.net/ops/docs/areas/hardware/server/ris-cdgenerate.html The configuration files for rrc13 should already be there, as I burnt a CD with them in mid-september. Could you make one version of the ISO available on for the Moscow people to FTP, and burn another copy of the ISO ? ( rrc13's hardware was purchased by the Moscow people, and so the NCC has never seen the bits'n'pieces. ) -- Bruce Campbell RIPE Systems/Network Engineer NCC www.ripe.net - PGP562C8B1B From matthew at ripe.net Mon Oct 25 18:14:46 2004 From: matthew at ripe.net (Matthew Williams) Date: Mon, 25 Oct 2004 18:14:46 +0200 Subject: [ris-int] RE: Installation CD for RRC13 In-Reply-To: <20041021163009.Y97610@argo.ripn.net> Message-ID: <003401c4baad$bea3a240$1f0200c1@rockstar> Hello again, Hope you had a good weekend. We should now have an image of the installation cd available via http: http://www.ris.ripe.net/source/ [file name: rrc_cd.img]. James, who prepared the image, should be able to answer technical questions that may arise. Thank you for your patience :) Kind regards, Matthew > -----Original Message----- > From: Elena P. Voronina [mailto:elin at ripn.net] > Sent: 21 October 2004 14:38 > To: Matthew Williams > Cc: 'Timakin Vladimir'; ris-int at ripe.net; 'Bruce Campbell' > Subject: RE: Installation CD for RRC13 > > > Hello, > > On Thu, 21 Oct 2004, Matthew Williams wrote: > > > Hi Elena, > > > > It seems that Bruce sent you the CD with express mail from > NL shortly > > after the RIPE meeting. I could ask our OPS department to make > unfortunately, we didn't receive this mail. > > > an ISO image available via ftp, or alternatively, have a > new one sent > > to your attention via DHL this time ;) > > It doesn't matter. We can take file via ftp, if it is > convenient for you. > > Elena > > > > > What suites you? > > > > Kind regards, > > Matthew > > > > > -----Original Message----- > > > From: Elena P. Voronina [mailto:elin at ripn.net] > > > Sent: 21 October 2004 10:08 > > > To: Matthew Williams > > > Cc: 'Timakin Vladimir'; ris-int at ripe.net; 'Bruce Campbell' > > > Subject: Re: Installation CD for RRC13 > > > > > > > > > > > > Hello, > > > > > > i'm very sorry, but we din't receive CD. > > > > > > Sincerely, Elena > > > > > > > > > On Tue, 19 Oct 2004, Matthew Williams wrote: > > > > > > > Hi there, > > > > > > > > Thanks for getting the RRC in place. > > > > > > > > BTW, did receive the installation cd that Bruce > Campbell sent you > > > > a while ago? > > > > > > > > Kind regards, > > > > Matthew > > > > > > > > > > > > > > > > From elin at ripn.net Thu Oct 28 14:46:27 2004 From: elin at ripn.net (Elena P. Voronina) Date: Thu, 28 Oct 2004 16:46:27 +0400 (MSD) Subject: [ris-int] RE: Installation CD for RRC13 In-Reply-To: <003401c4baad$bea3a240$1f0200c1@rockstar> References: <003401c4baad$bea3a240$1f0200c1@rockstar> Message-ID: <20041028163057.G55097@argo.ripn.net> Hello, i re-send this e-mail for Evgueni Kouskevitch, who will install software. On Mon, 25 Oct 2004, Matthew Williams wrote: > Hello again, > > Hope you had a good weekend. > > We should now have an image of the installation cd available via http: http://www.ris.ripe.net/source/ [file name: rrc_cd.img]. > James, who prepared the image, should be able to answer technical questions that may arise. > > Thank you for your patience :) Not at all, Sincerely, Elena > > Kind regards, > Matthew > From ryn999 at 126.com Sun Oct 31 21:04:59 2004 From: ryn999 at 126.com (=?GB2312?B?wfXPyMn6?=) Date: Mon, 1 Nov 2004 04:04:59 +0800 Subject: [ris-int] =?GB2312?B?yMu/qreixrE=?= Message-ID: <20041031200133.56C256A4A6@postboy.ripe.net> ?????? ??????????????????????????????????????????????????????????????????????,????????????????.?????????????????? ?????????????????? ?? ???? ???? ?????????? ??????????13535599081 ------------------------------------------------------------------------ // ???????? SOYO ????????????????????????????http://soyomail.51.net/ // ???? SOYO ????????????????????????????????????????????????!