From arife at ripe.net Thu Jul 1 09:25:09 2004 From: arife at ripe.net (Arife Vural) Date: Thu, 1 Jul 2004 09:25:09 +0200 Subject: [ris-int] Re: RRC and TTM at DE-CIX, schedule May/June In-Reply-To: <40E2F11A.6070603@de-cix.net> References: <007401c44402$6ea8dc00$300200c1@rockstar> <40B613C9.80206@de-cix.net> <20040607155134.GA3293@ripe.net> <40C4AF49.5060908@de-cix.net> <20040630161824.GP3878@ripe.net> <40E2F11A.6070603@de-cix.net> Message-ID: <20040701072509.GA22880@ripe.net> > we are a little bit short on engineers this week (one on holiday, one > ill), but I hope to get the work done this week. > > I will let you know the RFS date tomorrow. OK. Thanks Arnold. Regards. Arife From arife at ripe.net Thu Jul 1 11:23:30 2004 From: arife at ripe.net (Arife Vural) Date: Thu, 1 Jul 2004 11:23:30 +0200 Subject: [ris-int] Re: RRC and TTM at DE-CIX, schedule May/June In-Reply-To: <40E3D24B.4090008@de-cix.net> References: <007401c44402$6ea8dc00$300200c1@rockstar> <40B613C9.80206@de-cix.net> <20040607155134.GA3293@ripe.net> <40C4AF49.5060908@de-cix.net> <20040630161824.GP3878@ripe.net> <40E2F11A.6070603@de-cix.net> <20040701072509.GA22880@ripe.net> <40E3D24B.4090008@de-cix.net> Message-ID: <20040701092330.GE22880@ripe.net> > >>we are a little bit short on engineers this week (one on holiday, one > >>ill), but I hope to get the work done this week. > >> > >>I will let you know the RFS date tomorrow. > > > > > > OK. Thanks Arnold. > > > > RRC server and TTM server will be connected till 2004-07-02 11:00 UTC. Great! > Should the engineer also power on both servers? Yes, please. Regards. Arife From arnold.nipper at de-cix.net Thu Jul 1 10:58:51 2004 From: arnold.nipper at de-cix.net (Nipper, Arnold) Date: Thu, 01 Jul 2004 10:58:51 +0200 Subject: [ris-int] Re: RRC and TTM at DE-CIX, schedule May/June In-Reply-To: <20040701072509.GA22880@ripe.net> References: <007401c44402$6ea8dc00$300200c1@rockstar> <40B613C9.80206@de-cix.net> <20040607155134.GA3293@ripe.net> <40C4AF49.5060908@de-cix.net> <20040630161824.GP3878@ripe.net> <40E2F11A.6070603@de-cix.net> <20040701072509.GA22880@ripe.net> Message-ID: <40E3D24B.4090008@de-cix.net> Arife, On 01.07.2004 09:25 Arife Vural wrote: >>we are a little bit short on engineers this week (one on holiday, one >>ill), but I hope to get the work done this week. >> >>I will let you know the RFS date tomorrow. > > > OK. Thanks Arnold. > RRC server and TTM server will be connected till 2004-07-02 11:00 UTC. Should the engineer also power on both servers? Regards, Arnold From arife at ripe.net Thu Jul 1 13:13:33 2004 From: arife at ripe.net (Arife Vural) Date: Thu, 1 Jul 2004 13:13:33 +0200 Subject: [ris-int] Re: RIS stuff for AS559 - MD5, IPv6 with RRC04 In-Reply-To: <20040505102127.GG32540@ripe.net> References: <16536.43768.532721.506952@diotima.switch.ch> <20040505102127.GG32540@ripe.net> Message-ID: <20040701111333.GA32140@ripe.net> Hi Simon, IPv6 peering at CIXP with AS559 is down by now. We upgraded the box from FreeBSD to Linux, and Linux kernel does not have IPv6 support now, we try to get a new kernel with IPv6 support. As soon as we get new kernel, the session with AS559 will come up. Sorry for that. Regards. Arife From arife at ripe.net Thu Jul 1 13:18:24 2004 From: arife at ripe.net (Arife Vural) Date: Thu, 1 Jul 2004 13:18:24 +0200 Subject: [ris-int] RRC04 is done, end of Linux migration Message-ID: <20040701111824.GA30129@ripe.net> Hi guys, With RRC04 migration, we are done at Linux migration. It was the last box. Arife From henk at ripe.net Thu Jul 1 13:24:27 2004 From: henk at ripe.net (Henk Uijterwaal (RIPE NCC)) Date: Thu, 1 Jul 2004 13:24:27 +0200 (CEST) Subject: [ris-int] RRC04 is done, end of Linux migration In-Reply-To: <20040701111824.GA30129@ripe.net> References: <20040701111824.GA30129@ripe.net> Message-ID: On Thu, 1 Jul 2004, Arife Vural wrote: > > Hi guys, > > With RRC04 migration, we are done at Linux migration. It was the last > box. Applause for a job well done, Henk > > Arife > ------------------------------------------------------------------------------ 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 ------------------------------------------------------------------------------ Process and Procedure are the last hiding place of people without the wit and wisdom to do their job properly. (David Brent). From matthew at ripe.net Thu Jul 1 14:47:22 2004 From: matthew at ripe.net (Matthew Williams) Date: Thu, 1 Jul 2004 14:47:22 +0200 Subject: [ris-int] RE: One question about RIPE Data. In-Reply-To: Message-ID: <001e01c45f69$8ddb97c0$2d0200c1@rockstar> Hi there, 2001 will be difficult. Your best would be to have a look at the logs available here: http://data.ris.ripe.net/rrc00/logs/. However, please note that they start from Aug, 2002 and onwards. Kind regards, Matthew Williams > -----Original Message----- > From: Zhi Li [mailto:lizhi at cs.ucdavis.edu] > Sent: 01 July 2004 13:04 > To: ris at ripe.net > Subject: One question about RIPE Data. > > > Hello, > I am Zhi, a Ph.D student at University of California, Davis. > I am trying to analyze the data at rrc00 during 2001 about > the multi-hop BGP session statability. That is, I am trying > to estimate > the number of RESETs between rrc00 and other peering points. > I think there are some resets might be caused by Setup or > reconfigurations. I am trying to screen them out. I am > wondering whether > you have some records about rrc00's reconguration history during year > 2001? > Thanks a lot for your help! > Best Regards, > Zhi > > > From simon at limmat.switch.ch Thu Jul 1 14:31:57 2004 From: simon at limmat.switch.ch (Simon Leinen) Date: Thu, 1 Jul 2004 14:31:57 +0200 Subject: [ris-int] Re: RIS stuff for AS559 - MD5, IPv6 with RRC04 In-Reply-To: <20040701111333.GA32140@ripe.net> References: <16536.43768.532721.506952@diotima.switch.ch> <20040505102127.GG32540@ripe.net> <20040701111333.GA32140@ripe.net> Message-ID: <16612.1085.651788.177268@diotima.switch.ch> Arife Vural writes: > IPv6 peering at CIXP with AS559 is down by now. We upgraded the box > from FreeBSD to Linux, and Linux kernel does not have IPv6 support > now, we try to get a new kernel with IPv6 support. As soon as we get > new kernel, the session with AS559 will come up. I understand - thanks for working on the fix! Regards, -- Simon. From bruce.campbell at ripe.net Thu Jul 1 14:38:30 2004 From: bruce.campbell at ripe.net (Bruce Campbell) Date: Thu, 1 Jul 2004 14:38:30 +0200 (CEST) Subject: [ris-int] Re: RIS stuff for AS559 - MD5, IPv6 with RRC04 In-Reply-To: <16612.1085.651788.177268@diotima.switch.ch> References: <16536.43768.532721.506952@diotima.switch.ch> <20040505102127.GG32540@ripe.net> <20040701111333.GA32140@ripe.net> <16612.1085.651788.177268@diotima.switch.ch> Message-ID: On Thu, 1 Jul 2004, Simon Leinen wrote: > Arife Vural writes: > > IPv6 peering at CIXP with AS559 is down by now. We upgraded the box > > from FreeBSD to Linux, and Linux kernel does not have IPv6 support > > now, we try to get a new kernel with IPv6 support. As soon as we get > > new kernel, the session with AS559 will come up. > > I understand - thanks for working on the fix! s/IPv6/8021q/ actually. Hi Simon ;) --==-- Bruce. Man of many hats. From henk at ripe.net Fri Jul 2 16:03:04 2004 From: henk at ripe.net (Henk Uijterwaal (RIPE NCC)) Date: Fri, 2 Jul 2004 16:03:04 +0200 (CEST) Subject: [ris-int] rispeering e-mails are ticketized from now on. In-Reply-To: <20040630135114.GH3878@ripe.net> References: <200406301253.i5UCr28r005742@birch.ripe.net> <20040630135114.GH3878@ripe.net> Message-ID: Arife, I'm having pretty much the same problems as James. I can see 3 tickets, but every time, I try to access a ticket, I get a bunch of permission denied like: rtt: Error: Could not open message file '/ncc/TicketDB/Messages/2004/06/NCC#2004063336/NCC#2004063336.001' rtt: Error: Could not open message file '/ncc/TicketDB/Messages/2004/06/NCC#2004063336/NCC#2004063336.002' Cannot open dir /ncc/TicketDB/Messages/2004/06/NCC#2004063336: Permission denied Invalid registry name none When I try to do "show messages" on a ticket, I get a pop-up window saying "cannot read NCC#2004070127/subject". Any suggestions? Henk Do I have to be in the RIS request group? [x49:12] groups henk henk : projects staff tt-req named role infomnt test-traffic rttuser sudo-np eng-mt [x49:13] groups arife arife : projects staff tt-req named role test-traffic rttuser cvs sudo-np ris-request > > Hi Guys, > > When you get xrtt, please first resize window, make it bigger. Then you will > see window is divided two half. First one has the list of tickets, > each ticket might have more than one e-mail, and the second half has > the list of e-mails that are related to ticket you choose at first half. > > If you try to see the ticket (double left click), you get the error message > James sent. If you like to see e-mail related your ticket you should > go to second part and do double left click on the message. Also in this > part you should see all the replies which is related with this ticket. > > If you like answer one of those tickets, please first own the ticket > by Ticket Data section and then go an reply. > > Arife > > > > > it does not work? It looks, it works for me. It should also work for you. > > > > > > It does run, but I don't see any open tickets. > > > > I get error messages like: > > > > Cannot open dir /ncc/TicketDB/Messages/2004/06/NCC#2004063337: No such file or > > directory > > Cannot open Event File > > /ncc/TicketDB/Messages/2004/06/NCC#2004063337/NCC#2004063337.evt : No such > > file or directory > > Cannot open Message File > > /ncc/TicketDB/Messages/2004/06/NCC#2004063337/NCC#2004063337.000 : No such > > file or directory > > Cannot open dir /ncc/TicketDB/Messages/2004/06/NCC#2004063337: No such file or > > directory > > Cannot open Message File > > /ncc/TicketDB/Messages/2004/06/NCC#2004063337/NCC#2004063337.000 : No such > > file or directory > > Use of uninitialized value in string eq at /usr/local/ncc/bin/xrtt line 3518. > > > > > > James > ------------------------------------------------------------------------------ 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 ------------------------------------------------------------------------------ Process and Procedure are the last hiding place of people without the wit and wisdom to do their job properly. (David Brent). From wilhelm at ripe.net Fri Jul 2 16:24:59 2004 From: wilhelm at ripe.net (Rene Wilhelm) Date: Fri, 02 Jul 2004 16:24:59 +0200 Subject: [ris-int] rispeering e-mails are ticketized from now on. In-Reply-To: Message from "Henk Uijterwaal (RIPE NCC)" of "Fri, 02 Jul 2004 16:03:04 +0200." Message-ID: <200407021424.i62EOx4c016861@birch.ripe.net> > Do I have to be in the RIS request group? > > [x49:12] groups henk > henk : projects staff tt-req named role infomnt test-traffic rttuser > sudo-np eng-mt > [x49:13] groups arife > arife : projects staff tt-req named role test-traffic rttuser cvs sudo-np > ris-request not sure about ris-request, but rttuser is required to access the TicketDB directory tree. x27$ ls -ld /ncc/TicketDB/Messages drwxrws--- 12 rttadmin rttuser 4096 Feb 5 13:35 /ncc/TicketDB/Messages -- Rene > > > > > > > > > Hi Guys, > > > > When you get xrtt, please first resize window, make it bigger. Then you will > > see window is divided two half. First one has the list of tickets, > > each ticket might have more than one e-mail, and the second half has > > the list of e-mails that are related to ticket you choose at first half. > > > > If you try to see the ticket (double left click), you get the error message > > James sent. If you like to see e-mail related your ticket you should > > go to second part and do double left click on the message. Also in this > > part you should see all the replies which is related with this ticket. > > > > If you like answer one of those tickets, please first own the ticket > > by Ticket Data section and then go an reply. > > > > Arife > > > > > > > it does not work? It looks, it works for me. It should also work for you. > > > > > > > > It does run, but I don't see any open tickets. > > > > > > I get error messages like: > > > > > > Cannot open dir /ncc/TicketDB/Messages/2004/06/NCC#2004063337: No such file or > > > directory > > > Cannot open Event File > > > /ncc/TicketDB/Messages/2004/06/NCC#2004063337/NCC#2004063337.evt : No such > > > file or directory > > > Cannot open Message File > > > /ncc/TicketDB/Messages/2004/06/NCC#2004063337/NCC#2004063337.000 : No such > > > file or directory > > > Cannot open dir /ncc/TicketDB/Messages/2004/06/NCC#2004063337: No such file or > > > directory > > > Cannot open Message File > > > /ncc/TicketDB/Messages/2004/06/NCC#2004063337/NCC#2004063337.000 : No such > > > file or directory > > > Use of uninitialized value in string eq at /usr/local/ncc/bin/xrtt line 3518. > > > > > > > > > James > > > > ------------------------------------------------------------------------------ > 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 > ------------------------------------------------------------------------------ > > Process and Procedure are the last hiding place of people without the wit > and wisdom to do their job properly. (David Brent). > From henk at ripe.net Fri Jul 2 16:36:44 2004 From: henk at ripe.net (Henk Uijterwaal (RIPE NCC)) Date: Fri, 2 Jul 2004 16:36:44 +0200 (CEST) Subject: [ris-int] Logout, login Message-ID: Found it: i was added to a group, but had not logged out and back in since then. It now works. H. ------------------------------------------------------------------------------ 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 ------------------------------------------------------------------------------ Process and Procedure are the last hiding place of people without the wit and wisdom to do their job properly. (David Brent). From wilhelm at ripe.net Fri Jul 2 16:44:35 2004 From: wilhelm at ripe.net (Rene Wilhelm) Date: Fri, 02 Jul 2004 16:44:35 +0200 Subject: [ris-int] rispeering ticket auto-reply Message-ID: <200407021444.i62EiZ4c025136@birch.ripe.net> Hi Arife, Now that I finally learned how to make xrtt work for me, I had a quick look and immediately have a question: Would it be possible for the ticketing system to send a reply customized to RIS instead of a generic RIPE NCC reply? e.g. in NCC#2004070198, the reply is send by hm-ack and ends with these lines: For more information about the RIPE NCC (the Regional Internet Registry for Europe and Surrounding Areas), please refer to http://www.ripe.net/. I'd think a pointer to www.ripe.net/ris would be more appropriate when someone sends a message to rispeering (or in future ris at ripe.net) Cheers, -- Rene From arife at ripe.net Fri Jul 2 17:36:18 2004 From: arife at ripe.net (Arife Vural) Date: Fri, 2 Jul 2004 17:36:18 +0200 Subject: [ris-int] Re: Logout, login In-Reply-To: References: Message-ID: <20040702153617.GF21200@ripe.net> > Found it: i was added to a group, but had not logged out and back in since > then. It now works. Good! Oleg told me this. But I totally forgot. Arife > > H. > > ------------------------------------------------------------------------------ > 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 > ------------------------------------------------------------------------------ > > Process and Procedure are the last hiding place of people without the wit > and wisdom to do their job properly. (David Brent). From arife at ripe.net Fri Jul 2 17:52:31 2004 From: arife at ripe.net (Arife Vural) Date: Fri, 2 Jul 2004 17:52:31 +0200 Subject: [ris-int] Re: rispeering ticket auto-reply In-Reply-To: <200407021444.i62EiZ4c025136@birch.ripe.net> References: <200407021444.i62EiZ4c025136@birch.ripe.net> Message-ID: <20040702155231.GH21200@ripe.net> Hi Rene, I tried to customize the auto-reply message. I will check it out again, it's the one that I sent. Arife On Fri, Jul 02, 2004 at 04:44:35PM +0200, Rene Wilhelm wrote: > Hi Arife, > > Now that I finally learned how to make xrtt work for me, > I had a quick look and immediately have a question: > > Would it be possible for the ticketing system to send a reply > customized to RIS instead of a generic RIPE NCC reply? > > e.g. in NCC#2004070198, the reply is send by hm-ack > and ends with these lines: > > For more information about the RIPE NCC (the Regional Internet > Registry for Europe and Surrounding Areas), please refer to > http://www.ripe.net/. > > I'd think a pointer to www.ripe.net/ris would be more appropriate > when someone sends a message to rispeering (or in future ris at ripe.net) > > Cheers, > > -- Rene From arife at ripe.net Fri Jul 2 18:20:03 2004 From: arife at ripe.net (Arife Vural) Date: Fri, 2 Jul 2004 18:20:03 +0200 Subject: [ris-int] [hm-ack@ripe.net: NCC#2004070239 Re: test] Message-ID: <20040702162003.GL21200@ripe.net> Now, it has proper link. Arife ----- Forwarded message from RIPE NCC Acknowledgements ----- From: RIPE NCC Acknowledgements To: Arife Vural Subject: NCC#2004070239 Re: test Date: Fri, 02 Jul 2004 18:15:49 +0200 (CEST) Greetings, This message has been automatically generated in response to the e-mail: To: Ris-request Role Account From: Arife Vural Date: Fri, 2 Jul 2004 18:15:41 +0200 Message-ID: <20040702161541.GK21200 at ripe.net> Subject: test There is no need to reply to this message right now. Your ticket has been assigned an ID of "NCC#2004070239". Please include this string in the subject line of any further correspondence on this matter. For more information about the RIPE NCC RIS Project, please refer to http://www.ripe.net/ris/. Thank you, RIPE NCC Software Department ----- End forwarded message ----- From matthew at ripe.net Fri Jul 2 18:50:08 2004 From: matthew at ripe.net (Matthew Williams) Date: Fri, 2 Jul 2004 18:50:08 +0200 Subject: [ris-int] public version of the myASn getting started Message-ID: <003f01c46054$a1dd22c0$2d0200c1@rockstar> I made a public version of the myASn getting started guide available here: http://www.ripe.net/ris/myasngsg.html Please comment. Cheers, Matthew --- > Matthew Williams (MW243-RIPE) > Customer Liaison Engineer > RIPE NCC - http://www.ripe.net/np/ From colitti at dia.uniroma3.it Sat Jul 3 13:42:47 2004 From: colitti at dia.uniroma3.it (Lorenzo Colitti) Date: Sat, 03 Jul 2004 13:42:47 +0200 Subject: [ris-int] Bug in bgpdump Message-ID: <40E69BB7.7050707@dia.uniroma3.it> Hi RIS folks, while working on IPv6 BGP data here in Rome I discovered a bug in Agilent's bgpdump where if processing a RIB dump in machine-compatible (-m, -M) mode it would not print out the correct IPv6 addresses but output bogus IPv4 addresses (32.1.x.x, 63.254.x.x...) instead. The attached patch should fix the problem. I can't check it in because I don't have access from here. Could someone else do it for me? Thanks! Cheers, Lorenzo -- --------------------------------------------------------- Lorenzo Colitti Ph.D student Computer Networks research group Roma Tre University colitti at dia.uniroma3.it +39-0655173215 --------------------------------------------------------- From arife at ripe.net Mon Jul 5 09:39:23 2004 From: arife at ripe.net (Arife Vural) Date: Mon, 5 Jul 2004 09:39:23 +0200 Subject: [ris-int] RIS meeting at 10.00 Message-ID: <20040705073923.GA8132@ripe.net> Hi guys, Let's do the RIS meeting in Training Room. Arife From henk at ripe.net Mon Jul 5 11:23:39 2004 From: henk at ripe.net (Henk Uijterwaal (RIPE NCC)) Date: Mon, 5 Jul 2004 11:23:39 +0200 (CEST) Subject: [ris-int] Notes from this morning Message-ID: RIS meeting 5/7/2004 ==================== Present (for at least a fraction of the meeting): Matthew, Henk (Notes), James, Gerard, Vasco, Arife (chair), Ruud, Katie Absent: Shane, Bruce 0. New chair ------------ Henk introduced Arife as the new chairperson for this meeting. Arife took control of the meeting after this. 1. Minutes ----------- Henk voluntered as notetaker 2. Migration ------------ A lot of work has been done. RRC12 up and running, need a day of work from our side before peering requests can be accepted. Public announcement and request for peerings will be done on Wednesday. This closes the work item "migration to linux". Progress was made on the other integration work with OPS. It was not clear to Gerard (or anybody) if the item software sync was done. Action on Bruce to report status. Otherwise "Integration with OPS" work item is done. Procedures draft: After some discussion, an action on Bruce was put to check if the s/w and h/w maintenance procedures are in line with the draft operations document. If not, Bruce to provide text to update the draft. Ticketting: rispeering at ripe.net now in xrtt. ripops at ripe.net to follow this week after Arife has gone through the error messages. If you have not yet check if you can use xrtt, please do so. Some operational aspects were discussed: RRC04 and RRC06 need kernel patches (standard procedure). BGPd was updated, the problem with it crashing seems to have been solved at the expense of removing SNMP support. As we were not using the latter, this was not a great loss. 3. v6 version of CGI's ---------------------- Prefix query 90% done. Works for 1 day, not for more 1 day. THis will be added. James going through the other cgi's. Arife has not made much progress. Still hope to finish by Thu, Matthew to send announcement Fri. 4. myASn -------- WP4 finished by the end of the week, handover of software planned for the week of 12/7. Shane to appoint a second person from SED for this. All users have been transferred from the prototype. Matthew will announce that the prototype is going to disappear today, then shut it down on Friday. 5. Peering requests. -------------------- 12 pending, Vasco will do them. The question was raised if it'd make sense to integrate peerings at ripe.net (regular peerings with AS3333) and rispeerings at ripe.net. No decision was taken at this point. Gerard mentioned that he has a nagiop script to verify if peerings are up and running. This could replace the regular (3/year) RIS peering checks automatically. 6. AOB ------ 1. Have to find a start page for the RIS iii stuff. No clear consensus on where to put the wrapper page. 2. Need to introduce new RIS folks to Olaf, Alex, etc. some time. Mainly for their information. 7. Meeting closed @ 9:32 ------------------------ Actions Matthew 5/7 Announce that the myASn prototype will disappear. 7/7 Announce RRC12 9/7 Announce v6 version of CGI's. Bruce 5/7 Report on status of software sync. Bruce Check if ops procedures are in line with what is in the draft procedures document ------------------------------------------------------------------------------ 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 ------------------------------------------------------------------------------ Process and Procedure are the last hiding place of people without the wit and wisdom to do their job properly. (David Brent). From henk at ripe.net Mon Jul 5 12:00:27 2004 From: henk at ripe.net (Henk Uijterwaal (RIPE NCC)) Date: Mon, 5 Jul 2004 12:00:27 +0200 (CEST) Subject: [ris-int] RE: Bgplay question (fwd) Message-ID: Hi, Can somebody please burn a copy of the update CD that we sent around to upgrade the RRC's and mail it to Radoslav? Note that this has been promised to him as is WITHOUT ANY SUPPORT, so once he has it, he is on is own. Thanks, 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 ------------------------------------------------------------------------------ Process and Procedure are the last hiding place of people without the wit and wisdom to do their job properly. (David Brent). ---------- Forwarded message ---------- Date: Thu, 1 Jul 2004 09:57:48 +0300 From: Radoslav Vasilev To: "Henk Uijterwaal (RIPE NCC)" Subject: RE: Bgplay question Hello Henk, Thanks for your readiness to help me. Here's our office address: Radoslav Vasilev Mladost 1, bl.9 1784 Sofia Bulgaria -----Original Message----- From: Henk Uijterwaal (RIPE NCC) [mailto:henk at ripe.net] Sent: Wednesday, June 30, 2004 6:06 PM To: Radoslav Vasilev Cc: bgplay at dia.uniroma3.it; ris-int at ripe.net Subject: Re: Bgplay question Hi Radoslav, Sorry for the somewhat slow reply. > My names Radoslav Vasilev. I'm working as network administrator for > one of the biggest Bulgarian ISP. What I'm interested in is > implementing route-collector software, for the bulgarian peering routing (only). We do have a CD with a script that installs Linux on a machine with Linux and builds a route collector out of it. It contains the O/S, quagga (bgp client), mysql (db), plus supporting software. If you have a suitable machine (we use Dell Poweredge 1750's, but anything that supports Linux should work) then you can use that as a route collector. We can give you a copy of that CD. This is not something we actively support though, so you are on your own here. An occasional question by email would be fine, we can send you updates of software every once in a while, but that is about all the support we can give. I simply don't have the resources to do anything more. > My question is related for the status of BGPlay, and whether we have > chance of using it for a graphical representation for the data > collected. Thanks for your time in advance. To get a copy of the software, talk to the Rome guys. Once you have a route collector and DB, this should work though. If you are interested, please send me a postal address for the CD, 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 ------------------------------------------------------------------------------ Process and Procedure are the last hiding place of people without the wit and wisdom to do their job properly. (David Brent). --- Incoming mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.707 / Virus Database: 463 - Release Date: 15.6.2004 ?. --- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.707 / Virus Database: 463 - Release Date: 15.6.2004 ?. From colitti at dia.uniroma3.it Mon Jul 5 12:33:47 2004 From: colitti at dia.uniroma3.it (Lorenzo Colitti) Date: Mon, 05 Jul 2004 12:33:47 +0200 Subject: [ris-int] RE: Bgplay question (fwd) In-Reply-To: References: Message-ID: <40E92E8B.9020609@dia.uniroma3.it> Henk Uijterwaal (RIPE NCC) wrote: > Can somebody please burn a copy of the update CD that we sent around > to upgrade the RRC's and mail it to Radoslav? > [...] Might making an ISO image of the OS available on some FTP site be a good idea? Maybe more people are interested in this. For example, I remember there was some interest on the part of the Rome internet exchange a few months ago. Cheers, Lorenzo -- --------------------------------------------------------- Lorenzo Colitti Ph.D student Computer Networks research group Roma Tre University colitti at dia.uniroma3.it +39-0655173215 --------------------------------------------------------- From henk at ripe.net Mon Jul 5 12:42:26 2004 From: henk at ripe.net (Henk Uijterwaal (RIPE NCC)) Date: Mon, 5 Jul 2004 12:42:26 +0200 (CEST) Subject: [ris-int] RE: Bgplay question (fwd) In-Reply-To: <40E92E8B.9020609@dia.uniroma3.it> References: <40E92E8B.9020609@dia.uniroma3.it> Message-ID: On Mon, 5 Jul 2004, Lorenzo Colitti wrote: > Henk Uijterwaal (RIPE NCC) wrote: > > Can somebody please burn a copy of the update CD that we sent around > > to upgrade the RRC's and mail it to Radoslav? > > [...] > > Might making an ISO image of the OS available on some FTP site be a good > idea? I don't see a problem with that, as long as it is 200% clear that we do not support this. Henk > > Maybe more people are interested in this. For example, I remember there > was some interest on the part of the Rome internet exchange a few months > ago. > > > Cheers, > Lorenzo > > -- > --------------------------------------------------------- > Lorenzo Colitti Ph.D student > Computer Networks research group Roma Tre University > colitti at dia.uniroma3.it +39-0655173215 > --------------------------------------------------------- > ------------------------------------------------------------------------------ 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 ------------------------------------------------------------------------------ Process and Procedure are the last hiding place of people without the wit and wisdom to do their job properly. (David Brent). From matthew at ripe.net Mon Jul 5 13:37:36 2004 From: matthew at ripe.net (Matthew Williams) Date: Mon, 5 Jul 2004 13:37:36 +0200 Subject: [ris-int] See... Message-ID: <000201c46284$78c380a0$1f0200c1@rockstar> If it all makes sense to you... http://www.ripe.net/ris/myasngls.html Cheers, Matthew From matthew at ripe.net Mon Jul 5 13:37:36 2004 From: matthew at ripe.net (Matthew Williams) Date: Mon, 5 Jul 2004 13:37:36 +0200 Subject: [ris-int] Bread crumbs Message-ID: <000801c46284$7926d650$1f0200c1@rockstar> Hi Alexis, Can you add bread crumbs (top-left corner: myASn>xxx) for 'Getting Started Guide', 'FAQ', 'Reported Bugs', 'Requested Features' and 'Acknowledgments'? Cheers, Matthew From hong-wei_kong at agilent.com Mon Jul 5 13:40:14 2004 From: hong-wei_kong at agilent.com (hong-wei_kong at agilent.com) Date: Mon, 5 Jul 2004 19:40:14 +0800 Subject: [ris-int] RE: Bug in bgpdump Message-ID: Hi Lorenzo, Thank you for fixing this bug. However, I don't find the attached patch with your email. Have you forgot to attach the file? regards, hongwei -----Original Message----- From: Lorenzo Colitti [mailto:colitti at dia.uniroma3.it] Sent: Saturday, July 03, 2004 7:43 PM To: ris-int at ripe.net Cc: Hong-Wei Kong; Maurizio Pizzonia Subject: Bug in bgpdump Hi RIS folks, while working on IPv6 BGP data here in Rome I discovered a bug in Agilent's bgpdump where if processing a RIB dump in machine-compatible (-m, -M) mode it would not print out the correct IPv6 addresses but output bogus IPv4 addresses (32.1.x.x, 63.254.x.x...) instead. The attached patch should fix the problem. I can't check it in because I don't have access from here. Could someone else do it for me? Thanks! Cheers, Lorenzo -- --------------------------------------------------------- Lorenzo Colitti Ph.D student Computer Networks research group Roma Tre University colitti at dia.uniroma3.it +39-0655173215 --------------------------------------------------------- From colitti at dia.uniroma3.it Mon Jul 5 13:56:04 2004 From: colitti at dia.uniroma3.it (Lorenzo Colitti) Date: Mon, 05 Jul 2004 13:56:04 +0200 Subject: [ris-int] Re: Bug in bgpdump In-Reply-To: References: Message-ID: <40E941D4.3020307@dia.uniroma3.it> hong-wei_kong at agilent.com wrote: > Hi Lorenzo, > > Thank you for fixing this bug. However, I don't find the attached > patch with your email. Have you forgot to attach the file? Yes, I forgot. ;-) Here it is. Can someone check it in? Cheers, Lorenzo -- --------------------------------------------------------- Lorenzo Colitti Ph.D student Computer Networks research group Roma Tre University colitti at dia.uniroma3.it +39-0655173215 --------------------------------------------------------- -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: patch-bgpdump-ipv6-M URL: From daniel.karrenberg at ripe.net Mon Jul 5 16:48:37 2004 From: daniel.karrenberg at ripe.net (Daniel Karrenberg) Date: Mon, 5 Jul 2004 16:48:37 +0200 Subject: [ris-int] See... In-Reply-To: <000201c46284$78c380a0$1f0200c1@rockstar> References: <000201c46284$78c380a0$1f0200c1@rockstar> Message-ID: <20040705144837.GE6382@reifa.karrenberg.net> On 05.07 13:37, Matthew Williams wrote: > If it all makes sense to you... > > http://www.ripe.net/ris/myasngls.html > > Cheers, > Matthew Hold Down Event: The number of times an event can occur before an alarm message is sent (default: 1 event). s/can/has to/ Also: Hold Down Time better Min-Event-Duration Hold Down Event better Min-Event-Count Time To Live better Event-Hold-Down-Time or Event-Suppress-Time From matthew at ripe.net Mon Jul 5 19:15:49 2004 From: matthew at ripe.net (Matthew Williams) Date: Mon, 5 Jul 2004 19:15:49 +0200 Subject: FW: [ris-int] See... Message-ID: <003501c462b3$b82dbdd0$1f0200c1@rockstar> Hi James, I like DFK's suggestions. What do you think? > Hold Down Time better Min-Event-Duration > Hold Down Event better Min-Event-Count > > Time To Live > or Event-Suppress-Time Cheers, Matthew > -----Original Message----- > From: ris-int-admin at ripe.net [mailto:ris-int-admin at ripe.net] > On Behalf Of Daniel Karrenberg > Sent: 05 July 2004 16:49 > To: Matthew Williams > Cc: ris-int at ripe.net > Subject: Re: [ris-int] See... > > > On 05.07 13:37, Matthew Williams wrote: > > If it all makes sense to you... > > > > http://www.ripe.net/ris/myasngls.html > > > > Cheers, > > Matthew > > Hold Down Event: > The number of times an event can occur before an alarm > message is sent (default: 1 event). > > s/can/has to/ > > > > Also: > > Hold Down Time better Min-Event-Duration > Hold Down Event better Min-Event-Count > > Time To Live better Event-Hold-Down-Time > or Event-Suppress-Time > From matthew at ripe.net Tue Jul 6 02:37:46 2004 From: matthew at ripe.net (Matthew Williams) Date: Tue, 6 Jul 2004 02:37:46 +0200 Subject: FW: [ris-int] See... Message-ID: <000101c462f1$754a23d0$aba8a8c0@rockstar> > > Time To Live > > or Event-Suppress-Time Probably max-detect-window is probably better. We should get this right once and for all ;) Alexis, let's sync the change (you - interface/email, I - doc). Cheers, Matthew > -----Original Message----- > From: ris-int-admin at ripe.net [mailto:ris-int-admin at ripe.net] > On Behalf Of Matthew Williams > Sent: 05 July 2004 19:16 > To: 'James Aldridge' > Cc: ris-int at ripe.net; 'Alexis Yushin' > Subject: FW: [ris-int] See... > > > Hi James, > > I like DFK's suggestions. What do you think? > > > Hold Down Time better Min-Event-Duration > > Hold Down Event better Min-Event-Count > > > > Time To Live > > or Event-Suppress-Time > > Cheers, > Matthew > > > -----Original Message----- > > From: ris-int-admin at ripe.net [mailto:ris-int-admin at ripe.net] > > On Behalf Of Daniel Karrenberg > > Sent: 05 July 2004 16:49 > > To: Matthew Williams > > Cc: ris-int at ripe.net > > Subject: Re: [ris-int] See... > > > > > > On 05.07 13:37, Matthew Williams wrote: > > > If it all makes sense to you... > > > > > > http://www.ripe.net/ris/myasngls.html > > > > > > Cheers, > > > Matthew > > > > Hold Down Event: > > The number of times an event can occur before an alarm > > message is sent (default: 1 event). > > > > s/can/has to/ > > > > > > > > Also: > > > > Hold Down Time better Min-Event-Duration > > Hold Down Event better Min-Event-Count > > > > Time To Live better Event-Hold-Down-Time > > or Event-Suppress-Time > > > From james at ripe.net Tue Jul 6 09:28:09 2004 From: james at ripe.net (James Aldridge) Date: Tue, 06 Jul 2004 09:28:09 +0200 Subject: FW: [ris-int] See... In-Reply-To: Message from "Matthew Williams" of "Mon, 05 Jul 2004 19:15:49 +0200." <003501c462b3$b82dbdd0$1f0200c1@rockstar> Message-ID: <200407060728.i667S94c027261@birch.ripe.net> "Matthew Williams" wrote: > Hi James, > > I like DFK's suggestions. What do you think? > > > Hold Down Time better Min-Event-Duration > > Hold Down Event better Min-Event-Count > > > > Time To Live > > or Event-Suppress-Time It's getting closer to what I wrote back in April: | My thoughts: | | HDT - "Minimum Event Duration" ? | | HDE - "Event-count Threshold" ? | TTL - "Event-count Window" ? | James > Cheers, > Matthew > > > -----Original Message----- > > From: ris-int-admin at ripe.net [mailto:ris-int-admin at ripe.net] > > On Behalf Of Daniel Karrenberg > > Sent: 05 July 2004 16:49 > > To: Matthew Williams > > Cc: ris-int at ripe.net > > Subject: Re: [ris-int] See... > > > > > > On 05.07 13:37, Matthew Williams wrote: > > > If it all makes sense to you... > > > > > > http://www.ripe.net/ris/myasngls.html > > > > > > Cheers, > > > Matthew > > > > Hold Down Event: > > The number of times an event can occur before an alarm > > message is sent (default: 1 event). > > > > s/can/has to/ > > > > > > > > Also: > > > > Hold Down Time better Min-Event-Duration > > Hold Down Event better Min-Event-Count > > > > Time To Live better Event-Hold-Down-Time > > or Event-Suppress-Time > > > From matthew at ripe.net Tue Jul 6 13:23:22 2004 From: matthew at ripe.net (Matthew Williams) Date: Tue, 6 Jul 2004 13:23:22 +0200 Subject: FW: [ris-int] See... In-Reply-To: <20040706062611.GH6382@reifa.karrenberg.net> Message-ID: <000801c4634b$a632ca60$1f0200c1@rockstar> Alarm/notification-Suppress-Time then? The term we've used so far for 'email entries' is notifications. I guess it could be anything (alarm) as long as we're consequent in documentation ;) The time is also a max, which we might want to make clear above. I'll send an email to comms for some 'soft' fb. Cheers, Matthew > -----Original Message----- > From: 'Daniel Karrenberg' [mailto:dfk at ripe.net] > Sent: 06 July 2004 08:26 > To: Matthew Williams > Cc: 'James Aldridge'; 'Alexis Yushin'; ris-int at ripe.net > Subject: Re: FW: [ris-int] See... > > > On 06.07 02:37, Matthew Williams wrote: > > > > Time To Live > > > > or Event-Suppress-Time > > > > Probably max-detect-window is probably better. We should get this > > right once and for all ;) > > I don't like that too much. I like Event-Suppress-Time or > Alarm-Suppress-Time better. > From matthew at ripe.net Tue Jul 6 13:25:34 2004 From: matthew at ripe.net (Matthew Williams) Date: Tue, 6 Jul 2004 13:25:34 +0200 Subject: FW: [ris-int] See... In-Reply-To: <200407060728.i667S94c027261@birch.ripe.net> Message-ID: <000901c4634b$f5685910$1f0200c1@rockstar> > It's getting closer to what I wrote back in April: I believe it's called convergence, although I must admit that we're pretty slow :-D > -----Original Message----- > From: ris-int-admin at ripe.net [mailto:ris-int-admin at ripe.net] > On Behalf Of James Aldridge > Sent: 06 July 2004 09:28 > To: Matthew Williams > Cc: 'James Aldridge'; ris-int at ripe.net; 'Alexis Yushin' > Subject: Re: FW: [ris-int] See... > > > "Matthew Williams" wrote: > > Hi James, > > > > I like DFK's suggestions. What do you think? > > > > > Hold Down Time better Min-Event-Duration > > > Hold Down Event better Min-Event-Count > > > > > > Time To Live > > > or Event-Suppress-Time > > It's getting closer to what I wrote back in April: > > | My thoughts: > | > | HDT - "Minimum Event Duration" ? > | > | HDE - "Event-count Threshold" ? > | TTL - "Event-count Window" ? > | > > James > > > > Cheers, > > Matthew > > > > > -----Original Message----- > > > From: ris-int-admin at ripe.net [mailto:ris-int-admin at ripe.net] > > > On Behalf Of Daniel Karrenberg > > > Sent: 05 July 2004 16:49 > > > To: Matthew Williams > > > Cc: ris-int at ripe.net > > > Subject: Re: [ris-int] See... > > > > > > > > > On 05.07 13:37, Matthew Williams wrote: > > > > If it all makes sense to you... > > > > > > > > http://www.ripe.net/ris/myasngls.html > > > > > > > > Cheers, > > > > Matthew > > > > > > Hold Down Event: > > > The number of times an event can occur before an alarm > > > message is sent (default: 1 event). > > > > > > s/can/has to/ > > > > > > > > > > > > Also: > > > > > > Hold Down Time better Min-Event-Duration > > > Hold Down Event better Min-Event-Count > > > > > > Time To Live better Event-Hold-Down-Time > > > or Event-Suppress-Time > > > > > > From matthew at ripe.net Tue Jul 6 13:32:26 2004 From: matthew at ripe.net (Matthew Williams) Date: Tue, 6 Jul 2004 13:32:26 +0200 Subject: FW: [ris-int] See... In-Reply-To: <20040706062611.GH6382@reifa.karrenberg.net> Message-ID: <000a01c4634c$e9a622a0$1f0200c1@rockstar> One more thing, we need to once and for all converge on capitalisation of myasn, so we get that right in the int once and for all before Alexis leaves. Should it be 'myASn' or 'MyASn'? I really don't care as long as we consequently use one of them ;) Cheers, Matthew > -----Original Message----- > From: 'Daniel Karrenberg' [mailto:dfk at ripe.net] > Sent: 06 July 2004 08:26 > To: Matthew Williams > Cc: 'James Aldridge'; 'Alexis Yushin'; ris-int at ripe.net > Subject: Re: FW: [ris-int] See... > > > On 06.07 02:37, Matthew Williams wrote: > > > > Time To Live > > > > or Event-Suppress-Time > > > > Probably max-detect-window is probably better. We should get this > > right once and for all ;) > > I don't like that too much. I like Event-Suppress-Time or > Alarm-Suppress-Time better. > From matthew at ripe.net Tue Jul 6 14:11:57 2004 From: matthew at ripe.net (Matthew Williams) Date: Tue, 6 Jul 2004 14:11:57 +0200 Subject: [ris-int] We need your fb again ;) Message-ID: <000c01c46352$6f589180$1f0200c1@rockstar> Hi Comms, Please see explanations here: http://www.ripe.net/ris/myasngls.html#50 And then think about alternative terms for below: *Hold Down Time *Hold Down Event: 'Min-Event-Duration' and 'Min-Event-Count' are our current candidates. *Time To Live: We have two lines of thought here. One relates to 'detection' of events building up to an alarm entry in the email sent to the user, while the other follows the line of 'suppression' of further entries once the first entry has been triggered (based on exactly the same events). If we go along with the second concept, then this is a maximum time interval. In the first case, we're talking about a fixed 'window' (time interval). I hope all that made sense ;) Here come some suggestions: "Event-count Window", "Alarm-Suppress-Time", "Max-suppress-time", "Event-Suppress-Time', "max-detect-window", "alarm-detect-window"... Etc etc... We could go on forever and ever. The question is: What works for you? The beta is more or less ready so we need to get this one out of the way once and for all... ;) Cheers, Matthew --- > Matthew Williams (MW243-RIPE) > Customer Liaison Engineer > RIPE NCC - http://www.ripe.net/np/ From wilhelm at ripe.net Tue Jul 6 14:29:53 2004 From: wilhelm at ripe.net (Rene Wilhelm) Date: Tue, 6 Jul 2004 14:29:53 +0200 (CEST) Subject: MyASN logo (RE: FW: [ris-int] See...) In-Reply-To: <000a01c4634c$e9a622a0$1f0200c1@rockstar> References: <000a01c4634c$e9a622a0$1f0200c1@rockstar> Message-ID: > http://www.ripe.net/ris/myasngls.html this and other pages could do with a myasn logo on top. How 'bout the attached? (result of few minutes juggling with previous work :-) -- Rene -------------- next part -------------- A non-text attachment was scrubbed... Name: myasn.ps Type: application/postscript Size: 1672 bytes Desc: MyASN logo URL: From matthew at ripe.net Tue Jul 6 14:44:03 2004 From: matthew at ripe.net (Matthew Williams) Date: Tue, 6 Jul 2004 14:44:03 +0200 Subject: MyASN logo (RE: FW: [ris-int] See...) In-Reply-To: Message-ID: <001701c46356$eaf182d0$1f0200c1@rockstar> Are you trying to get us into troubles with Comms? This kind of work is always outsorced to a 3rd party for big bucks. You should know that! :-D Cheers, Matthew > -----Original Message----- > From: ris-int-admin at ripe.net [mailto:ris-int-admin at ripe.net] > On Behalf Of Rene Wilhelm > Sent: 06 July 2004 14:30 > To: Matthew Williams > Cc: ris-int at ripe.net > Subject: MyASN logo (RE: FW: [ris-int] See...) > > > > > http://www.ripe.net/ris/myasngls.html > > this and other pages could do with a myasn logo on top. > > How 'bout the attached? > > (result of few minutes juggling with previous work :-) > > > -- Rene > From matthew at ripe.net Tue Jul 6 15:01:40 2004 From: matthew at ripe.net (Matthew Williams) Date: Tue, 6 Jul 2004 15:01:40 +0200 Subject: [ris-int] RE: myasntesting In-Reply-To: Message-ID: <001a01c46359$6113e730$1f0200c1@rockstar> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi there, Many thanks for your kind words. I will add your suggestion on the 'Requested Features' page in the UI. Kind regards, Matthew Williams --- > Matthew Williams (MW243-RIPE) > Customer Liaison Engineer > RIPE NCC - http://www.ripe.net/np/ > -----Original Message----- > From: Sonny Franslay [mailto:sonnyfranslay at pacific.net.sg] > Sent: 06 July 2004 03:39 > To: ris at ripe.net > Subject: myasntesting > > > Hi, > > Thanks for the effort in developing the tools. It's great stuff! > > Just a small suggestion, it'd be good if we could upload a > csv kind of > flat file to configure the alarms. This is to ease the > configuration of > the alarms, especially for the first time. > > It's a great tool nonetheless :) > > regards, > -- > -sonny (AS4628) > -----BEGIN PGP SIGNATURE----- Version: PGP 7.0.4 iQA/AwUBQOqissHkFbJe+GdoEQJsCgCglQOMSGlzKSj4lwUBXc0pPpehZCYAoL4W FSLgPqoBEaRUfCRGtghZ+V9v =27YR -----END PGP SIGNATURE----- From wilhelm at ripe.net Tue Jul 6 15:15:11 2004 From: wilhelm at ripe.net (Rene Wilhelm) Date: Tue, 06 Jul 2004 15:15:11 +0200 Subject: MyASN logo (RE: FW: [ris-int] See...) In-Reply-To: Message from "Matthew Williams" of "Tue, 06 Jul 2004 14:44:03 +0200." <001701c46356$eaf182d0$1f0200c1@rockstar> Message-ID: <200407061315.i66DFB4c029786@birch.ripe.net> > Are you trying to get us into troubles with Comms? > This kind of work is always outsorced to a 3rd party for big bucks. > You should know that! :-D I forgot :( must be getting old :-(( With regards to capitalization, it seems you managed to confuse even comms: http://iii.ripe.net/comms/styleguide.html says: Appendix A Acronyms & Terms .... MyASn: A notification system for BGP in cases of unexpected routing behaviour - integrated into the RIPE NCC LIR Portal. Appendix B - Common Formatting Errors ... myASn: This has a lower case 'm' even at the start of a sentence. which is not consistent :) (unless myASn and MyASn are different entities:-)) -- Rene From henk at ripe.net Tue Jul 6 15:57:49 2004 From: henk at ripe.net (Henk Uijterwaal (RIPE NCC)) Date: Tue, 6 Jul 2004 15:57:49 +0200 (CEST) Subject: MyASN logo (RE: FW: [ris-int] See...) In-Reply-To: <200407061315.i66DFB4c029786@birch.ripe.net> References: <200407061315.i66DFB4c029786@birch.ripe.net> Message-ID: Nick, See attached, the styleguide is not following the styleguide. Henk On Tue, 6 Jul 2004, Rene Wilhelm wrote: > > > Are you trying to get us into troubles with Comms? > > This kind of work is always outsorced to a 3rd party for big bucks. > > You should know that! :-D > > I forgot :( must be getting old :-(( > > With regards to capitalization, it seems you managed to > confuse even comms: > > > http://iii.ripe.net/comms/styleguide.html says: > > Appendix A Acronyms & Terms > .... > MyASn: A notification system for BGP in cases of unexpected > routing behaviour - integrated into the RIPE NCC LIR Portal. > > > Appendix B - Common Formatting Errors > ... > myASn: This has a lower case 'm' even at the start of a sentence. > > > which is not consistent :) > > (unless myASn and MyASn are different entities:-)) > > -- Rene > ------------------------------------------------------------------------------ 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 ------------------------------------------------------------------------------ Process and Procedure are the last hiding place of people without the wit and wisdom to do their job properly. (David Brent). From henk at ripe.net Tue Jul 6 16:00:19 2004 From: henk at ripe.net (Henk Uijterwaal (RIPE NCC)) Date: Tue, 6 Jul 2004 16:00:19 +0200 (CEST) Subject: MyASN logo (RE: FW: [ris-int] See...) In-Reply-To: <200407061315.i66DFB4c029786@birch.ripe.net> References: <200407061315.i66DFB4c029786@birch.ripe.net> Message-ID: On Tue, 6 Jul 2004, Rene Wilhelm wrote: > > > Are you trying to get us into troubles with Comms? > > This kind of work is always outsorced to a 3rd party for big bucks. > > You should know that! :-D > > I forgot :( must be getting old :-(( > > With regards to capitalization, it seems you managed to > confuse even comms: It should be myASn, but MicroSoft Typewriter will use its built intelligence and correct that to MyASn for you :-) Henk > > > http://iii.ripe.net/comms/styleguide.html says: > > Appendix A Acronyms & Terms > .... > MyASn: A notification system for BGP in cases of unexpected > routing behaviour - integrated into the RIPE NCC LIR Portal. > > > Appendix B - Common Formatting Errors > ... > myASn: This has a lower case 'm' even at the start of a sentence. > > > which is not consistent :) > > (unless myASn and MyASn are different entities:-)) > > -- Rene > ------------------------------------------------------------------------------ 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 ------------------------------------------------------------------------------ Process and Procedure are the last hiding place of people without the wit and wisdom to do their job properly. (David Brent). From henk at ripe.net Wed Jul 7 09:36:12 2004 From: henk at ripe.net (Henk Uijterwaal (RIPE NCC)) Date: Wed, 7 Jul 2004 09:36:12 +0200 (CEST) Subject: MyASN logo (RE: FW: [ris-int] See...) In-Reply-To: References: <000a01c4634c$e9a622a0$1f0200c1@rockstar> Message-ID: On Tue, 6 Jul 2004, Rene Wilhelm wrote: > > > http://www.ripe.net/ris/myasngls.html > > this and other pages could do with a myasn logo on top. > > How 'bout the attached? > > (result of few minutes juggling with previous work :-) I like it (except for the caps, we agreed on myASn). Henk > > > -- Rene ------------------------------------------------------------------------------ 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 ------------------------------------------------------------------------------ Process and Procedure are the last hiding place of people without the wit and wisdom to do their job properly. (David Brent). From wilhelm at ripe.net Wed Jul 7 13:06:55 2004 From: wilhelm at ripe.net (Rene Wilhelm) Date: Wed, 07 Jul 2004 13:06:55 +0200 Subject: MyASN logo (RE: FW: [ris-int] See...) In-Reply-To: Message from "Henk Uijterwaal (RIPE NCC)" of "Wed, 07 Jul 2004 09:36:12 +0200." Message-ID: <200407071106.i67B6t4c003256@birch.ripe.net> > I like it (except for the caps, we agreed on myASn). with PostScript & vi a five second fix! ;-) http://iii.ripe.net/~wilhelm/myasn.ps -- Rene From matthew at ripe.net Wed Jul 7 13:09:45 2004 From: matthew at ripe.net (Matthew Williams) Date: Wed, 7 Jul 2004 13:09:45 +0200 Subject: [ris-int] rrc12 Message-ID: <20040707110945.GA9649@ripe.net> Hi Arife, Are we ready to announce RRC12? Cheers, Matthew From arife at ripe.net Wed Jul 7 13:47:54 2004 From: arife at ripe.net (Arife Vural) Date: Wed, 7 Jul 2004 13:47:54 +0200 Subject: [ris-int] Re: rrc12 In-Reply-To: <20040707110945.GA9649@ripe.net> References: <20040707110945.GA9649@ripe.net> Message-ID: <20040707114754.GH22180@ripe.net> Hi Matthew, You can announce it. Rawdata link, and peering info pages are in place. Also updated Looking Glass. I could not finish rest of CGIs yet, because at the same time, I'm doing documentation about what needs to be change when a new RRC is added. It takes time. I will finish updating CGIs tomorrow with some bug fixes. Arife On Wed, Jul 07, 2004 at 01:09:45PM +0200, Matthew Williams wrote: > Hi Arife, > > Are we ready to announce RRC12? > > Cheers, > Matthew From matthew at ripe.net Wed Jul 7 13:55:47 2004 From: matthew at ripe.net (Matthew Williams) Date: Wed, 7 Jul 2004 13:55:47 +0200 Subject: [ris-int] RE: rrc12 In-Reply-To: <20040707114754.GH22180@ripe.net> Message-ID: <00d901c46419$57b6e320$1f0200c1@rockstar> Great stuff. We can wait with the CGIs until Fri (as agreed ;). Cheers, Matthew > -----Original Message----- > From: Arife Vural [mailto:arife at ripe.net] > Sent: 07 July 2004 13:48 > To: Matthew Williams > Cc: ris-int at ripe.net > Subject: Re: rrc12 > > > > Hi Matthew, > > You can announce it. Rawdata link, and peering info pages are > in place. Also updated Looking Glass. I could not finish rest > of CGIs yet, because at the same time, I'm doing > documentation about what needs to be change > when a new RRC is added. It takes time. > > I will finish updating CGIs tomorrow with some bug fixes. > > Arife > > On Wed, Jul 07, 2004 at 01:09:45PM +0200, Matthew Williams wrote: > > Hi Arife, > > > > Are we ready to announce RRC12? > > > > Cheers, > > Matthew > From arife at ripe.net Wed Jul 7 13:58:02 2004 From: arife at ripe.net (Arife Vural) Date: Wed, 7 Jul 2004 13:58:02 +0200 Subject: [ris-int] Re: rrc12 In-Reply-To: <20040707114754.GH22180@ripe.net> References: <20040707110945.GA9649@ripe.net> <20040707114754.GH22180@ripe.net> Message-ID: <20040707115802.GI22180@ripe.net> BTW, we have already got quite few peers at DE-CIX. Vasco is busy to clean up tickets. Arife On Wed, Jul 07, 2004 at 01:47:54PM +0200, Arife Vural wrote: > > Hi Matthew, > > You can announce it. Rawdata link, and peering info pages are in place. > Also updated Looking Glass. I could not finish rest of CGIs yet, because > at the same time, I'm doing documentation about what needs to be change > when a new RRC is added. It takes time. > > I will finish updating CGIs tomorrow with some bug fixes. > > Arife > > On Wed, Jul 07, 2004 at 01:09:45PM +0200, Matthew Williams wrote: > > Hi Arife, > > > > Are we ready to announce RRC12? > > > > Cheers, > > Matthew From vasco at ripe.net Wed Jul 7 14:29:31 2004 From: vasco at ripe.net (Vasco Asturiano) Date: Wed, 7 Jul 2004 14:29:31 +0200 Subject: [ris-int] Re: rrc12 In-Reply-To: <20040707115802.GI22180@ripe.net> References: <20040707110945.GA9649@ripe.net> <20040707114754.GH22180@ripe.net> <20040707115802.GI22180@ripe.net> Message-ID: <20040707142931.17be8682.vasco@ripe.net> Hi, We had indeed quite some peering requests already for RRC12. There's now 17 sessions configured, though some are still not up, with one full-feed. It seems to be on its way then... :) Cheers, Vasco On Wed, 7 Jul 2004 13:58:02 +0200 Arife Vural wrote: > > BTW, we have already got quite few peers at DE-CIX. Vasco is > busy to clean up tickets. > > Arife > > On Wed, Jul 07, 2004 at 01:47:54PM +0200, Arife Vural wrote: > > > > Hi Matthew, > > > > You can announce it. Rawdata link, and peering info pages are in > > place. Also updated Looking Glass. I could not finish rest of CGIs > > yet, because at the same time, I'm doing documentation about what > > needs to be change when a new RRC is added. It takes time. > > > > I will finish updating CGIs tomorrow with some bug fixes. > > > > Arife > > > > On Wed, Jul 07, 2004 at 01:09:45PM +0200, Matthew Williams wrote: > > > Hi Arife, > > > > > > Are we ready to announce RRC12? > > > > > > Cheers, > > > Matthew > From matthew at ripe.net Wed Jul 7 15:32:15 2004 From: matthew at ripe.net (Matthew Williams) Date: Wed, 7 Jul 2004 15:32:15 +0200 Subject: [ris-int] Re: rrc12 In-Reply-To: <20040707142931.17be8682.vasco@ripe.net> Message-ID: <000201c46426$d1024be0$1f0200c1@rockstar> > There's now 17 sessions configured, though some are still not > up, with one full-feed. Wow, that's quite a good start :) Cheers, Matthew > -----Original Message----- > From: ris-int-admin at ripe.net [mailto:ris-int-admin at ripe.net] > On Behalf Of Vasco Asturiano > Sent: 07 July 2004 14:30 > To: ris-int at ripe.net > Subject: Re: [ris-int] Re: rrc12 > > > Hi, > > We had indeed quite some peering requests already for RRC12. > There's now 17 sessions configured, though some are still not > up, with one full-feed. > > It seems to be on its way then... :) > > Cheers, > > Vasco > > On Wed, 7 Jul 2004 13:58:02 +0200 > Arife Vural wrote: > > > > > BTW, we have already got quite few peers at DE-CIX. Vasco > is busy to > > clean up tickets. > > > > Arife > > > > On Wed, Jul 07, 2004 at 01:47:54PM +0200, Arife Vural wrote: > > > > > > Hi Matthew, > > > > > > You can announce it. Rawdata link, and peering info pages are in > > > place. Also updated Looking Glass. I could not finish > rest of CGIs > > > yet, because at the same time, I'm doing documentation about what > > > needs to be change when a new RRC is added. It takes time. > > > > > > I will finish updating CGIs tomorrow with some bug fixes. > > > > > > Arife > > > > > > On Wed, Jul 07, 2004 at 01:09:45PM +0200, Matthew Williams wrote: > > > > Hi Arife, > > > > > > > > Are we ready to announce RRC12? > > > > > > > > Cheers, > > > > Matthew > > > > From matthew at ripe.net Wed Jul 7 15:44:02 2004 From: matthew at ripe.net (Matthew Williams) Date: Wed, 7 Jul 2004 15:44:02 +0200 Subject: [ris-int] Re: rrc12 In-Reply-To: <20040707115802.GI22180@ripe.net> Message-ID: <000301c46428$76b8d2b0$1f0200c1@rockstar> Have you spoken to Arnold about sync effort? I'll put something together for ris-users and forward the contents to him for dist on their tech-list. Cheers, Matthew > -----Original Message----- > From: ris-int-admin at ripe.net [mailto:ris-int-admin at ripe.net] > On Behalf Of Arife Vural > Sent: 07 July 2004 13:58 > To: Matthew Williams > Cc: ris-int at ripe.net > Subject: Re: [ris-int] Re: rrc12 > > > > BTW, we have already got quite few peers at DE-CIX. Vasco is > busy to clean up tickets. > > Arife > > On Wed, Jul 07, 2004 at 01:47:54PM +0200, Arife Vural wrote: > > > > Hi Matthew, > > > > You can announce it. Rawdata link, and peering info pages are in > > place. Also updated Looking Glass. I could not finish rest of CGIs > > yet, because at the same time, I'm doing documentation about what > > needs to be change when a new RRC is added. It takes time. > > > > I will finish updating CGIs tomorrow with some bug fixes. > > > > Arife > > > > On Wed, Jul 07, 2004 at 01:09:45PM +0200, Matthew Williams wrote: > > > Hi Arife, > > > > > > Are we ready to announce RRC12? > > > > > > Cheers, > > > Matthew > From matthew at ripe.net Wed Jul 7 15:56:52 2004 From: matthew at ripe.net (Matthew Williams) Date: Wed, 7 Jul 2004 15:56:52 +0200 Subject: MyASN logo (RE: FW: [ris-int] See...) In-Reply-To: <200407071106.i67B6t4c003256@birch.ripe.net> Message-ID: <000401c4642a$41d1a980$1f0200c1@rockstar> Yeah, I like it too. But really we should run this through with comms, so we don't step on their toes. Cheers, Matthew > -----Original Message----- > From: ris-int-admin at ripe.net [mailto:ris-int-admin at ripe.net] > On Behalf Of Rene Wilhelm > Sent: 07 July 2004 13:07 > To: Henk Uijterwaal (RIPE NCC) > Cc: Matthew Williams; ris-int at ripe.net > Subject: Re: MyASN logo (RE: FW: [ris-int] See...) > > > > I like it (except for the caps, we agreed on myASn). > > with PostScript & vi a five second fix! ;-) > http://iii.ripe.net/~wilhelm/myasn.ps -- Rene From wilhelm at ripe.net Wed Jul 7 16:13:52 2004 From: wilhelm at ripe.net (Rene Wilhelm) Date: Wed, 07 Jul 2004 16:13:52 +0200 Subject: MyASN logo (RE: FW: [ris-int] See...) In-Reply-To: Message from "Matthew Williams" of "Wed, 07 Jul 2004 15:56:52 +0200." <000401c4642a$41d1a980$1f0200c1@rockstar> Message-ID: <200407071413.i67EDq4c021042@birch.ripe.net> > Yeah, I like it too. But really we should run this through > with comms, so we don't step on their toes. Sure, I was just having some fun with postscript. Feel free to do with it as you please: ignore / coordinate with comms / use on www.ris.ripe.net regardless -- Rene p.s. WARNING: the font used isn't arial, but helvetica-bold! :-D > > -----Original Message----- > > From: ris-int-admin at ripe.net [mailto:ris-int-admin at ripe.net] > > On Behalf Of Rene Wilhelm > > Sent: 07 July 2004 13:07 > > To: Henk Uijterwaal (RIPE NCC) > > Cc: Matthew Williams; ris-int at ripe.net > > Subject: Re: MyASN logo (RE: FW: [ris-int] See...) > > > > > > > I like it (except for the caps, we agreed on myASn). > > > > with PostScript & vi a five second fix! ;-) > > > http://iii.ripe.net/~wilhelm/myasn.ps > > -- Rene > From matthew at ripe.net Wed Jul 7 19:02:17 2004 From: matthew at ripe.net (Matthew Williams) Date: Wed, 7 Jul 2004 19:02:17 +0200 Subject: [ris-int] http://www.ris.ripe.net/cgi-bin/peerreg.cgi Message-ID: <002601c46444$28a19b90$1f0200c1@rockstar> Pls update with DE-CIX :) Cheers, Matthew From matthew at ripe.net Wed Jul 7 19:13:02 2004 From: matthew at ripe.net (Matthew Williams) Date: Wed, 7 Jul 2004 19:13:02 +0200 Subject: [ris-int] FW: ANNOUNCEMENT: New RIS Remote Route Collector at DE-CIX (RRC12) Message-ID: <002801c46445$a9330270$1f0200c1@rockstar> Hi there, Would you be so kind to forward this mail to your members? Edit at will ;) Kind regards, Matthew > -----Original Message----- > From: ris-users-admin at ripe.net > [mailto:ris-users-admin at ripe.net] On Behalf Of Matthew Williams > Sent: 07 July 2004 19:11 > To: ris-users at ripe.net > Subject: ANNOUNCEMENT: New RIS Remote Route Collector at > DE-CIX (RRC12) > > > > > *** PGP Signature Status: good > *** Signer: Matthew Williams-Bywater > *** Signed: 07/07/2004 19:11:05 > *** Verified: 07/07/2004 19:11:32 > *** BEGIN PGP VERIFIED MESSAGE *** > > [Apologies for duplicate mails] > > Dear All, > > The RIPE NCC is pleased to announce that the RIS Project's > twelth* Remote Route Collector, RRC12, is now ready to peer > with members at the German Internet Exchange (DE-CIX). > > RRC12 is located at the German Internet Exchange (DE-CIX), > and has been operational since July 2004. The RRC has an > interface on the shared DE-CIX fabric, running both IPv4 and > IPv6, and collects routing information from all exchange > members, who are willing to peer with us. > > The use of TCP MD5 Signatures on IPv4 BGP sessions is > supported on all RIS Route Collectors. MD5, however, is not > supported on IPv6 sessions. > > Details: > -------- > - Peering address: 80.81.192.152 (IPv4); 2001:7f8::316e:0:1 (IPv6) > - Autonomous system: 12654 > - Policy: http://www.ripe.net/ris/rrc12.html > - Peering requests: > * Email: rispeering at ripe.net > * Web form at URL: http://www.ris.ripe.net/cgi-bin/peerreg.cgi > > The Routing Information Service (RIS), which started as a > modest RIPE NCC project in 1999, has gradually grown to over > 300 IPv4 and IPv6 peers at now twelve* data collection points > in Europe, Japan and North America. Our mission is to collect > BGP routing information over a function of time, and make it > available to the Internet community. In essence, this means > devising tools that can help ISPs debug problems over time > without being limited to one BGP view and providing RIS raw > data regarding the Internet's historical development. > > Useful Links: > ------------- > RIS Info: http://www.ripe.net/ris/ > RIS Tools: http://www.ripe.net/ris/query.html > List of RRC Locations: http://www.ris.ripe.net/cgi-bin/rrcstatus.cgi > > Please send your comments to ris-int at ripe.net. > > Best regards, > The RIS Team > > *) RRC09 has been decommissioned > > --- > > Matthew Williams (MW243-RIPE) > > Customer Liaison Engineer > > RIPE NCC - http://www.ripe.net/np/ > > > *** END PGP VERIFIED MESSAGE *** > From alexis at ripe.net Thu Jul 8 21:26:43 2004 From: alexis at ripe.net (Alexis Yushin) Date: Thu, 8 Jul 2004 21:26:43 +0200 (CEST) Subject: [ris-int] Re: Bread crumbs In-Reply-To: <000801c46284$7926d650$1f0200c1@rockstar> from "Matthew Williams" at Jul 05, 2004 01:37:36 PM Message-ID: <200407081926.i68JQh3C003621@birch.ripe.net> Once Matthew Williams wrote: >Can you add bread crumbs (top-left corner: myASn>xxx) for 'Getting Started Guide', 'FAQ', 'Reported Bugs', 'Requested Features' and >'Acknowledgments'? Done. By the way, you dont need to include all the html elements like body etc in those pages, they are added automatically by autohandler.html Alexis From matthew at ripe.net Thu Jul 8 23:45:18 2004 From: matthew at ripe.net (Matthew Williams) Date: Thu, 8 Jul 2004 23:45:18 +0200 Subject: [ris-int] RE: Bread crumbs In-Reply-To: <200407081926.i68JQh3C003621@birch.ripe.net> Message-ID: <00bf01c46534$dcdfb650$aaa8a8c0@rockstar> Hi Alexis, > automatically by autohandler.html Ah, okay. BTW, I haven't heard from Comms yet... Let's agree on: 1. MYASN should be capitalised as "myASn" 2. Change HDT and HDE to - Min-Event-Duration - Min-Event-Count And TTL to - [Max-]Alarm-Supress[-Time] (you decide) Tell me when you'll make the changes in the UI, and I'll adapt the documentation at the same time. Cheers, Matthew > -----Original Message----- > From: Alexis Yushin [mailto:alexis at ripe.net] > Sent: 08 July 2004 21:27 > To: Matthew Williams > Cc: 'Alexis Yushin'; ris-int at ripe.net > Subject: Re: Bread crumbs > > > Once Matthew Williams wrote: > >Can you add bread crumbs (top-left corner: myASn>xxx) for 'Getting > >Started Guide', 'FAQ', 'Reported Bugs', 'Requested Features' and > >'Acknowledgments'? > > Done. By the way, you dont need to include all the html > elements like body etc in those pages, they are added > automatically by autohandler.html > > Alexis > From alexis at ripe.net Fri Jul 9 00:00:34 2004 From: alexis at ripe.net (Alexis Yushin) Date: Fri, 9 Jul 2004 00:00:34 +0200 (CEST) Subject: [ris-int] Re: Bread crumbs In-Reply-To: <00bf01c46534$dcdfb650$aaa8a8c0@rockstar> from "Matthew Williams" at Jul 08, 2004 11:45:18 PM Message-ID: <200407082200.i68M0YeT027679@birch.ripe.net> Once Matthew Williams wrote: >> automatically by autohandler.html > >Ah, okay. > >BTW, I haven't heard from Comms yet... Did you hear from the softies about when the transfer should take place? >Let's agree on: > >1. MYASN should be capitalised as "myASn" > >2. Change HDT and HDE to > >- Min-Event-Duration >- Min-Event-Count > >And TTL to > >- [Max-]Alarm-Supress[-Time] (you decide) Ah thanks for summarizing it for me, I was all confused about the email discussion... Alarm-Suppress-Time makes more sense, Max is more consequent.... Time for the sake of old ttl :) >Tell me when you'll make the changes in the UI, and I'll adapt the documentation at the same time. Will do. Alexis From matthew at ripe.net Fri Jul 9 13:30:47 2004 From: matthew at ripe.net (Matthew Williams) Date: Fri, 9 Jul 2004 13:30:47 +0200 Subject: [ris-int] Re: Bread crumbs In-Reply-To: <200407082200.i68M0YeT027679@birch.ripe.net> Message-ID: <000301c465a8$2e5ffc10$aaa8a8c0@rockstar> One last thing? The mail delivery errors need to be sent back to another address than risops, otherwise we might get swamped... Maybe even /dev/null? Cheers, Matthew > -----Original Message----- > From: ris-int-admin at ripe.net [mailto:ris-int-admin at ripe.net] > On Behalf Of Alexis Yushin > Sent: 09 July 2004 00:01 > To: Matthew Williams > Cc: 'Alexis Yushin'; ris-int at ripe.net > Subject: [ris-int] Re: Bread crumbs > > > Once Matthew Williams wrote: > >> automatically by autohandler.html > > > >Ah, okay. > > > >BTW, I haven't heard from Comms yet... > > Did you hear from the softies about when the transfer should > take place? > > > >Let's agree on: > > > >1. MYASN should be capitalised as "myASn" > > > >2. Change HDT and HDE to > > > >- Min-Event-Duration > >- Min-Event-Count > > > >And TTL to > > > >- [Max-]Alarm-Supress[-Time] (you decide) > > Ah thanks for summarizing it for me, I was all confused about > the email discussion... > > Alarm-Suppress-Time makes more sense, Max is more > consequent.... Time for the sake of old ttl :) > > >Tell me when you'll make the changes in the UI, and I'll adapt the > >documentation at the same time. > > Will do. > > Alexis > From alexis at ripe.net Fri Jul 9 13:47:54 2004 From: alexis at ripe.net (Alexis Yushin) Date: Fri, 9 Jul 2004 13:47:54 +0200 (CEST) Subject: [ris-int] Re: Bread crumbs In-Reply-To: <000301c465a8$2e5ffc10$aaa8a8c0@rockstar> from "Matthew Williams" at Jul 09, 2004 01:30:47 PM Message-ID: <200407091147.i69Blsdb002988@birch.ripe.net> Once Matthew Williams wrote: >One last thing? > >The mail delivery errors need to be sent back to another address than risops, otherwise we might get swamped... Maybe even >/dev/null? Sure no problem. I'm now trying to get all the stuff running on diemen. Pff its all in all a HUGE code change, I'm not sure how to go about testing... It will be a miracle if there are no new bugs introduced. Alexis From alexis at ripe.net Fri Jul 9 14:12:31 2004 From: alexis at ripe.net (Alexis Yushin) Date: Fri, 9 Jul 2004 14:12:31 +0200 (CEST) Subject: [ris-int] code update Message-ID: <200407091212.i69CCVFY013420@birch.ripe.net> Matthew, I think the best option since we have limited time if you send a notification to users that due to code update or maintenance of myASn users might be not able to access the myasn system, not receive or receive bogus alarms etc beginning from 4pm today until Monday 10am Amsterdam time? That should be enough for me to make the updates and test stuff. Otherwise it will take really extra long amount of time to get a whole second copy of myasn on diemen test it and then update...... Alexis From matthew at ripe.net Fri Jul 9 14:50:15 2004 From: matthew at ripe.net (Matthew Williams) Date: Fri, 9 Jul 2004 14:50:15 +0200 Subject: [ris-int] RE: code update In-Reply-To: <200407091212.i69CCVFY013420@birch.ripe.net> Message-ID: <000101c465b3$4816ed70$aaa8a8c0@rockstar> Okay, let's do that. Cheers, Matthew > -----Original Message----- > From: Alexis Yushin [mailto:alexis at ripe.net] > Sent: 09 July 2004 14:13 > To: Matthew Williams > Cc: ris-int at ripe.net > Subject: code update > > > Matthew, > > I think the best option since we have limited time if you > send a notification to users that due to code update or > maintenance of myASn users might be not able to access the > myasn system, not receive or receive bogus alarms etc > beginning from 4pm today until Monday 10am Amsterdam time? > That should be enough for me to make the updates and test > stuff. Otherwise it will take really extra long amount of > time to get a whole second copy of myasn on diemen test it > and then update...... > > Alexis > From arife at ripe.net Fri Jul 9 15:03:14 2004 From: arife at ripe.net (Arife Vural) Date: Fri, 9 Jul 2004 15:03:14 +0200 Subject: [ris-int] Re: rrc12 In-Reply-To: <000301c46428$76b8d2b0$1f0200c1@rockstar> References: <20040707115802.GI22180@ripe.net> <000301c46428$76b8d2b0$1f0200c1@rockstar> Message-ID: <20040709130313.GB30660@ripe.net> > Have you spoken to Arnold about sync effort? I'll put something together for ris-users and forward the contents to him for dist on > their tech-list. Sorry missed this e-mail. Can you tell me more what I have to talk about with Arno? Arife > > Cheers, > Matthew > > > -----Original Message----- > > From: ris-int-admin at ripe.net [mailto:ris-int-admin at ripe.net] > > On Behalf Of Arife Vural > > Sent: 07 July 2004 13:58 > > To: Matthew Williams > > Cc: ris-int at ripe.net > > Subject: Re: [ris-int] Re: rrc12 > > > > > > > > BTW, we have already got quite few peers at DE-CIX. Vasco is > > busy to clean up tickets. > > > > Arife > > > > On Wed, Jul 07, 2004 at 01:47:54PM +0200, Arife Vural wrote: > > > > > > Hi Matthew, > > > > > > You can announce it. Rawdata link, and peering info pages are in > > > place. Also updated Looking Glass. I could not finish rest of CGIs > > > yet, because at the same time, I'm doing documentation about what > > > needs to be change when a new RRC is added. It takes time. > > > > > > I will finish updating CGIs tomorrow with some bug fixes. > > > > > > Arife > > > > > > On Wed, Jul 07, 2004 at 01:09:45PM +0200, Matthew Williams wrote: > > > > Hi Arife, > > > > > > > > Are we ready to announce RRC12? > > > > > > > > Cheers, > > > > Matthew > > From matthew at ripe.net Fri Jul 9 15:15:21 2004 From: matthew at ripe.net (Matthew Williams) Date: Fri, 9 Jul 2004 15:15:21 +0200 Subject: [ris-int] Re: rrc12 In-Reply-To: <20040709130313.GB30660@ripe.net> Message-ID: <000301c465b6$c9818b60$aaa8a8c0@rockstar> Arnold Nipper? :) Please remind him to forward my mail about RRC12. Cheers, Matthew > -----Original Message----- > From: ris-int-admin at ripe.net [mailto:ris-int-admin at ripe.net] > On Behalf Of Arife Vural > Sent: 09 July 2004 15:03 > To: Matthew Williams > Cc: ris-int at ripe.net > Subject: Re: [ris-int] Re: rrc12 > > > > > Have you spoken to Arnold about sync effort? I'll put something > > together for ris-users and forward the contents to him for dist on > > their tech-list. > > Sorry missed this e-mail. Can you tell me more what I have to > talk about with Arno? > > Arife > > > > > Cheers, > > Matthew > > > > > -----Original Message----- > > > From: ris-int-admin at ripe.net [mailto:ris-int-admin at ripe.net] > > > On Behalf Of Arife Vural > > > Sent: 07 July 2004 13:58 > > > To: Matthew Williams > > > Cc: ris-int at ripe.net > > > Subject: Re: [ris-int] Re: rrc12 > > > > > > > > > > > > BTW, we have already got quite few peers at DE-CIX. Vasco is > > > busy to clean up tickets. > > > > > > Arife > > > > > > On Wed, Jul 07, 2004 at 01:47:54PM +0200, Arife Vural wrote: > > > > > > > > Hi Matthew, > > > > > > > > You can announce it. Rawdata link, and peering info pages are in > > > > place. Also updated Looking Glass. I could not finish > rest of CGIs > > > > yet, because at the same time, I'm doing documentation > about what > > > > needs to be change when a new RRC is added. It takes time. > > > > > > > > I will finish updating CGIs tomorrow with some bug fixes. > > > > > > > > Arife > > > > > > > > On Wed, Jul 07, 2004 at 01:09:45PM +0200, Matthew > Williams wrote: > > > > > Hi Arife, > > > > > > > > > > Are we ready to announce RRC12? > > > > > > > > > > Cheers, > > > > > Matthew > > > > From arife at ripe.net Fri Jul 9 15:22:17 2004 From: arife at ripe.net (Arife Vural) Date: Fri, 9 Jul 2004 15:22:17 +0200 Subject: [ris-int] Re: rrc12 In-Reply-To: <000301c465b6$c9818b60$aaa8a8c0@rockstar> References: <20040709130313.GB30660@ripe.net> <000301c465b6$c9818b60$aaa8a8c0@rockstar> Message-ID: <20040709132216.GD30660@ripe.net> > Arnold Nipper? :) I see :-) > Please remind him to forward my mail about RRC12. I guess we are not in their member mailinglist. Arife > > Cheers, > Matthew > > > -----Original Message----- > > From: ris-int-admin at ripe.net [mailto:ris-int-admin at ripe.net] > > On Behalf Of Arife Vural > > Sent: 09 July 2004 15:03 > > To: Matthew Williams > > Cc: ris-int at ripe.net > > Subject: Re: [ris-int] Re: rrc12 > > > > > > > > > Have you spoken to Arnold about sync effort? I'll put something > > > together for ris-users and forward the contents to him for dist on > > > their tech-list. > > > > Sorry missed this e-mail. Can you tell me more what I have to > > talk about with Arno? > > > > Arife > > > > > > > > Cheers, > > > Matthew > > > > > > > -----Original Message----- > > > > From: ris-int-admin at ripe.net [mailto:ris-int-admin at ripe.net] > > > > On Behalf Of Arife Vural > > > > Sent: 07 July 2004 13:58 > > > > To: Matthew Williams > > > > Cc: ris-int at ripe.net > > > > Subject: Re: [ris-int] Re: rrc12 > > > > > > > > > > > > > > > > BTW, we have already got quite few peers at DE-CIX. Vasco is > > > > busy to clean up tickets. > > > > > > > > Arife > > > > > > > > On Wed, Jul 07, 2004 at 01:47:54PM +0200, Arife Vural wrote: > > > > > > > > > > Hi Matthew, > > > > > > > > > > You can announce it. Rawdata link, and peering info pages are in > > > > > place. Also updated Looking Glass. I could not finish > > rest of CGIs > > > > > yet, because at the same time, I'm doing documentation > > about what > > > > > needs to be change when a new RRC is added. It takes time. > > > > > > > > > > I will finish updating CGIs tomorrow with some bug fixes. > > > > > > > > > > Arife > > > > > > > > > > On Wed, Jul 07, 2004 at 01:09:45PM +0200, Matthew > > Williams wrote: > > > > > > Hi Arife, > > > > > > > > > > > > Are we ready to announce RRC12? > > > > > > > > > > > > Cheers, > > > > > > Matthew > > > > > > From matthew at ripe.net Fri Jul 9 21:07:15 2004 From: matthew at ripe.net (Matthew Williams) Date: Fri, 9 Jul 2004 21:07:15 +0200 Subject: [ris-int] Web Access Report for the Routing Information Service - June, 2004 Message-ID: <006e01c465e7$f2dc4870$aaa8a8c0@rockstar> Hi All, The monthly RIS Web Access Report is available at the following URL: http://iii.ripe.net/np/ris/WWW062004_RIS.pdf Please comment on oddities (there is a 'p' missing somewhere ;) Cheers, Matthew -------------- next part -------------- A non-text attachment was scrubbed... Name: WWW062004_RIS.pdf Type: application/pdf Size: 252069 bytes Desc: not available URL: From alexis at ripe.net Fri Jul 9 21:18:53 2004 From: alexis at ripe.net (Alexis Yushin) Date: Fri, 9 Jul 2004 21:18:53 +0200 (CEST) Subject: [ris-int] Re: Bread crumbs In-Reply-To: <00bf01c46534$dcdfb650$aaa8a8c0@rockstar> from "Matthew Williams" at Jul 08, 2004 11:45:18 PM Message-ID: <200407091918.i69JIrJG018083@birch.ripe.net> Ok, This is done as well. (A bit late perhaps) but I moved the myasn-passwords to myasn-passwords.master and only added RIS users to the new myasn-passwords so users won't get confused by changing code. Like you annonced it will be inaccessible. Can you please take a look see if anything's broken? If we're still fine I'll be putting the new features into it and trying not to break too many things at the same time... Alexis Once Matthew Williams wrote: >Hi Alexis, > >> automatically by autohandler.html > >Ah, okay. > >BTW, I haven't heard from Comms yet... > >Let's agree on: > >1. MYASN should be capitalised as "myASn" > >2. Change HDT and HDE to > >- Min-Event-Duration >- Min-Event-Count > >And TTL to > >- [Max-]Alarm-Supress[-Time] (you decide) > >Tell me when you'll make the changes in the UI, and I'll adapt the documentation at the same time. > >Cheers, >Matthew > >> -----Original Message----- >> From: Alexis Yushin [mailto:alexis at ripe.net] >> Sent: 08 July 2004 21:27 >> To: Matthew Williams >> Cc: 'Alexis Yushin'; ris-int at ripe.net >> Subject: Re: Bread crumbs >> >> >> Once Matthew Williams wrote: >> >Can you add bread crumbs (top-left corner: myASn>xxx) for 'Getting >> >Started Guide', 'FAQ', 'Reported Bugs', 'Requested Features' and >> >'Acknowledgments'? >> >> Done. By the way, you dont need to include all the html >> elements like body etc in those pages, they are added >> automatically by autohandler.html >> >> Alexis >> > From hong-wei_kong at agilent.com Sat Jul 10 14:11:21 2004 From: hong-wei_kong at agilent.com (hong-wei_kong at agilent.com) Date: Sat, 10 Jul 2004 20:11:21 +0800 Subject: [ris-int] RE: Bug in bgpdump Message-ID: Hi Lorenzo, I noticed that the patch will cause problem to IPv4 prefixes and next hop. There is some minor bug in the patch. I have fixed it and checked the result. please check this one in. regards, hongwei -----Original Message----- From: Lorenzo Colitti [mailto:colitti at dia.uniroma3.it] Sent: Monday, July 05, 2004 7:56 PM To: hong-wei_kong at agilent.com Cc: ris-int at ripe.net; pizzonia at dia.uniroma3.it Subject: Re: Bug in bgpdump hong-wei_kong at agilent.com wrote: > Hi Lorenzo, > > Thank you for fixing this bug. However, I don't find the attached > patch with your email. Have you forgot to attach the file? Yes, I forgot. ;-) Here it is. Can someone check it in? Cheers, Lorenzo -- --------------------------------------------------------- Lorenzo Colitti Ph.D student Computer Networks research group Roma Tre University colitti at dia.uniroma3.it +39-0655173215 --------------------------------------------------------- -------------- next part -------------- A non-text attachment was scrubbed... Name: bgpdump.c Type: application/octet-stream Size: 51725 bytes Desc: not available URL: From matthew at ripe.net Mon Jul 12 11:28:10 2004 From: matthew at ripe.net (Matthew Williams) Date: Mon, 12 Jul 2004 11:28:10 +0200 Subject: [ris-int] Shut down of myASn prototype Message-ID: <000801c467f2$8bf93c50$1f0200c1@rockstar> Hi Arife, It might be a good idea to send out a brief notification shortly before you shut it down ;) Cheers, Matthew From matthew at ripe.net Mon Jul 12 15:36:12 2004 From: matthew at ripe.net (Matthew Williams) Date: Mon, 12 Jul 2004 15:36:12 +0200 Subject: [ris-int] FW: myasn handover Message-ID: <000601c46815$32530500$1f0200c1@rockstar> Hi Shane, How do you want to schedule below? Cheers, Matthew > -----Original Message----- > From: Alexis Yushin [mailto:alexis at ripe.net] > Sent: 12 July 2004 14:13 > To: Matthew Williams > Subject: myasn handover > > I'm pratically finished with all the stuff (unless I forgot > something), how do we go about the handover? Is there a > meeting scheduled with Shane or whoever? In my contract we > have three days at the office planned for handover, do you > know which days these will be? From matthew at ripe.net Tue Jul 13 15:25:31 2004 From: matthew at ripe.net (Matthew Williams) Date: Tue, 13 Jul 2004 15:25:31 +0200 Subject: [ris-int] Logging on to rrcs Message-ID: <000501c468dc$ded91900$1f0200c1@rockstar> Hi Arife, I seem to have some probs logging on.... (all rrcs?) matthew at cow at 15:22:15:~$ ssh rrc031 -l risops Warning: Permanently added 'rrc031,193.0.0.232' (RSA) to the list of known hosts. Permission denied (publickey,keyboard-interactive). matthew at cow at 15:22:20:~$ ssh rrc021 -l risops Permission denied (publickey,keyboard-interactive). Cheers, Matthew From arife at ripe.net Tue Jul 13 15:37:02 2004 From: arife at ripe.net (Arife Vural) Date: Tue, 13 Jul 2004 15:37:02 +0200 Subject: [ris-int] Logging on to rrcs In-Reply-To: <000501c468dc$ded91900$1f0200c1@rockstar> References: <000501c468dc$ded91900$1f0200c1@rockstar> Message-ID: <20040713133702.GF22530@ripe.net> Hi Matthew, > I seem to have some probs logging on.... (all rrcs?) > You have to login by your username, and then if you need you can run sudo command switch to risops or root user. After Linux migration, OPS changed login to RRC boxes from risops to individual users. This way it would more easy for OPS to keep track who runs which command and so. BTW, if you need to connect BGPD on RRCs you do not need to loging box, you can run, telnet rrc031 2605 That connection is open only RIPE NCC prefix. Arife > matthew at cow at 15:22:15:~$ ssh rrc031 -l risops > Warning: Permanently added 'rrc031,193.0.0.232' (RSA) to the list of known hosts. > Permission denied (publickey,keyboard-interactive). > > matthew at cow at 15:22:20:~$ ssh rrc021 -l risops > Permission denied (publickey,keyboard-interactive). > > Cheers, > Matthew From matthew at ripe.net Tue Jul 13 15:41:18 2004 From: matthew at ripe.net (Matthew Williams) Date: Tue, 13 Jul 2004 15:41:18 +0200 Subject: [ris-int] Logging on to rrcs In-Reply-To: <20040713133702.GF22530@ripe.net> Message-ID: <000001c468df$132c90e0$1f0200c1@rockstar> Hi Arife, Thanks for the info :) Please change references in newrom.txt accordingly. Yours or James's responsibility? I just cannot keep up-to-date nowadays ;) Cheers, Matthew > -----Original Message----- > From: Arife Vural [mailto:arife at ripe.net] > Sent: 13 July 2004 15:37 > To: Matthew Williams > Cc: ris-int at ripe.net > Subject: Re: [ris-int] Logging on to rrcs > > > > Hi Matthew, > > > I seem to have some probs logging on.... (all rrcs?) > > > > You have to login by your username, and then if you need you > can run sudo command switch to risops or root user. After > Linux migration, OPS changed login to RRC boxes from risops > to individual users. This way it would more easy for OPS to > keep track who runs which command and so. > > BTW, if you need to connect BGPD on RRCs you do not need > to loging box, you can run, > > telnet rrc031 2605 > > That connection is open only RIPE NCC prefix. > > Arife > > > matthew at cow at 15:22:15:~$ ssh rrc031 -l risops > > Warning: Permanently added 'rrc031,193.0.0.232' (RSA) to > the list of > > known hosts. Permission denied (publickey,keyboard-interactive). > > > > matthew at cow at 15:22:20:~$ ssh rrc021 -l risops > > Permission denied (publickey,keyboard-interactive). > > > > Cheers, > > Matthew > From arife at ripe.net Tue Jul 13 15:42:37 2004 From: arife at ripe.net (Arife Vural) Date: Tue, 13 Jul 2004 15:42:37 +0200 Subject: [ris-int] Logging on to rrcs In-Reply-To: <20040713133702.GF22530@ripe.net> References: <000501c468dc$ded91900$1f0200c1@rockstar> <20040713133702.GF22530@ripe.net> Message-ID: <20040713134237.GH22530@ripe.net> Hi Matthew, It looks your username is not in /etc/passwd file on RRCs. Can you send an e-mail to OPS to add? Arife On Tue, Jul 13, 2004 at 03:37:02PM +0200, Arife Vural wrote: > > Hi Matthew, > > > I seem to have some probs logging on.... (all rrcs?) > > > > You have to login by your username, and then if you need you > can run sudo command switch to risops or root user. After > Linux migration, OPS changed login to RRC boxes from risops > to individual users. This way it would more easy for OPS to > keep track who runs which command and so. > > BTW, if you need to connect BGPD on RRCs you do not need > to loging box, you can run, > > telnet rrc031 2605 > > That connection is open only RIPE NCC prefix. > > Arife > > > matthew at cow at 15:22:15:~$ ssh rrc031 -l risops > > Warning: Permanently added 'rrc031,193.0.0.232' (RSA) to the list of known hosts. > > Permission denied (publickey,keyboard-interactive). > > > > matthew at cow at 15:22:20:~$ ssh rrc021 -l risops > > Permission denied (publickey,keyboard-interactive). > > > > Cheers, > > Matthew From matthew at ripe.net Tue Jul 13 15:44:08 2004 From: matthew at ripe.net (Matthew Williams) Date: Tue, 13 Jul 2004 15:44:08 +0200 Subject: FW: [ris-int] Logging on to rrcs Message-ID: <000201c468df$78a15050$1f0200c1@rockstar> Hi there, Please add me to users who can logon to rrcs :) Cheers, Matthew > -----Original Message----- > From: ris-int-admin at ripe.net [mailto:ris-int-admin at ripe.net] > On Behalf Of Arife Vural > Sent: 13 July 2004 15:43 > To: Matthew Williams > Cc: ris-int at ripe.net > Subject: Re: [ris-int] Logging on to rrcs > > > > Hi Matthew, > > It looks your username is not in /etc/passwd file on RRCs. > Can you send an e-mail to OPS to add? > > Arife > > On Tue, Jul 13, 2004 at 03:37:02PM +0200, Arife Vural wrote: > > > > Hi Matthew, > > > > > I seem to have some probs logging on.... (all rrcs?) > > > > > > > You have to login by your username, and then if you need you > > can run sudo command switch to risops or root user. After > > Linux migration, OPS changed login to RRC boxes from risops > > to individual users. This way it would more easy for OPS to > > keep track who runs which command and so. > > > > BTW, if you need to connect BGPD on RRCs you do not need > > to loging box, you can run, > > > > telnet rrc031 2605 > > > > That connection is open only RIPE NCC prefix. > > > > Arife > > > > > matthew at cow at 15:22:15:~$ ssh rrc031 -l risops > > > Warning: Permanently added 'rrc031,193.0.0.232' (RSA) to > the list of > > > known hosts. Permission denied (publickey,keyboard-interactive). > > > > > > matthew at cow at 15:22:20:~$ ssh rrc021 -l risops > > > Permission denied (publickey,keyboard-interactive). > > > > > > Cheers, > > > Matthew > From matthew at ripe.net Tue Jul 13 16:01:19 2004 From: matthew at ripe.net (Matthew Williams) Date: Tue, 13 Jul 2004 16:01:19 +0200 Subject: FW: [ris-int] Logging on to rrcs Message-ID: <000301c468e1$df8b11a0$1f0200c1@rockstar> Don't bother as I'll probably only need bgpd access anyway ;) , but please update docs with procedure. Cheers, matthew > -----Original Message----- > From: ris-int-admin at ripe.net [mailto:ris-int-admin at ripe.net] > On Behalf Of Matthew Williams > Sent: 13 July 2004 15:44 > To: 'James Aldridge' > Cc: ris-int at ripe.net > Subject: FW: [ris-int] Logging on to rrcs > > > Hi there, > > Please add me to users who can logon to rrcs :) > > Cheers, > Matthew > > > -----Original Message----- > > From: ris-int-admin at ripe.net [mailto:ris-int-admin at ripe.net] > > On Behalf Of Arife Vural > > Sent: 13 July 2004 15:43 > > To: Matthew Williams > > Cc: ris-int at ripe.net > > Subject: Re: [ris-int] Logging on to rrcs > > > > > > > > Hi Matthew, > > > > It looks your username is not in /etc/passwd file on RRCs. Can you > > send an e-mail to OPS to add? > > > > Arife > > > > On Tue, Jul 13, 2004 at 03:37:02PM +0200, Arife Vural wrote: > > > > > > Hi Matthew, > > > > > > > I seem to have some probs logging on.... (all rrcs?) > > > > > > > > > > You have to login by your username, and then if you need > you can run > > > sudo command switch to risops or root user. After Linux > migration, > > > OPS changed login to RRC boxes from risops to individual > users. This > > > way it would more easy for OPS to keep track who runs > which command > > > and so. > > > > > > BTW, if you need to connect BGPD on RRCs you do not need > > > to loging box, you can run, > > > > > > telnet rrc031 2605 > > > > > > That connection is open only RIPE NCC prefix. > > > > > > Arife > > > > > > > matthew at cow at 15:22:15:~$ ssh rrc031 -l risops > > > > Warning: Permanently added 'rrc031,193.0.0.232' (RSA) to > > the list of > > > > known hosts. Permission denied (publickey,keyboard-interactive). > > > > > > > > matthew at cow at 15:22:20:~$ ssh rrc021 -l risops > Permission denied > > > > (publickey,keyboard-interactive). > > > > > > > > Cheers, > > > > Matthew > > > From james at ripe.net Tue Jul 13 16:10:05 2004 From: james at ripe.net (James Aldridge) Date: Tue, 13 Jul 2004 16:10:05 +0200 Subject: FW: [ris-int] Logging on to rrcs In-Reply-To: <000201c468df$78a15050$1f0200c1@rockstar> References: <000201c468df$78a15050$1f0200c1@rockstar> Message-ID: <69EAFDCB7616C8860BDF0D6C@guest-wv-22.ripe.net> --On Tuesday, 13 July, 2004 15:44 +0200 Matthew Williams wrote: > Hi there, > > Please add me to users who can logon to rrcs :) > Please open a ticket using "stt ops" or via the form on iii James > Cheers, > Matthew > >> -----Original Message----- >> From: ris-int-admin at ripe.net [mailto:ris-int-admin at ripe.net] >> On Behalf Of Arife Vural >> Sent: 13 July 2004 15:43 >> To: Matthew Williams >> Cc: ris-int at ripe.net >> Subject: Re: [ris-int] Logging on to rrcs >> >> >> >> Hi Matthew, >> >> It looks your username is not in /etc/passwd file on RRCs. >> Can you send an e-mail to OPS to add? >> >> Arife >> >> On Tue, Jul 13, 2004 at 03:37:02PM +0200, Arife Vural wrote: >> > >> > Hi Matthew, >> > >> > > I seem to have some probs logging on.... (all rrcs?) >> > > >> > >> > You have to login by your username, and then if you need you >> > can run sudo command switch to risops or root user. After >> > Linux migration, OPS changed login to RRC boxes from risops >> > to individual users. This way it would more easy for OPS to >> > keep track who runs which command and so. >> > >> > BTW, if you need to connect BGPD on RRCs you do not need >> > to loging box, you can run, >> > >> > telnet rrc031 2605 >> > >> > That connection is open only RIPE NCC prefix. >> > >> > Arife >> > >> > > matthew at cow at 15:22:15:~$ ssh rrc031 -l risops >> > > Warning: Permanently added 'rrc031,193.0.0.232' (RSA) to >> the list of >> > > known hosts. Permission denied (publickey,keyboard-interactive). >> > > >> > > matthew at cow at 15:22:20:~$ ssh rrc021 -l risops >> > > Permission denied (publickey,keyboard-interactive). >> > > >> > > Cheers, >> > > Matthew >> -- James Aldridge, Network Engineer, New Projects Group, RIPE NCC Tel: +31 20 535 4421 Fax: +31 20 535 4445 GSM: +31 6 5247 6932 PGP Key Fingerprint: 8F8F D923 48E8 FB76 8DD1 60CB 5003 859C F4BB E729 -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 186 bytes Desc: not available URL: From matthew at ripe.net Tue Jul 13 16:39:30 2004 From: matthew at ripe.net (Matthew Williams) Date: Tue, 13 Jul 2004 16:39:30 +0200 Subject: FW: [ris-int] Logging on to rrcs In-Reply-To: <69EAFDCB7616C8860BDF0D6C@guest-wv-22.ripe.net> Message-ID: <002301c468e7$3497bc70$1f0200c1@rockstar> Like I said earlier, bgpd access should be fine for me. Doc needs to be up-to-date though. Cheers, Matthew > -----Original Message----- > From: ris-int-admin at ripe.net [mailto:ris-int-admin at ripe.net] > On Behalf Of James Aldridge > Sent: 13 July 2004 16:10 > To: Matthew Williams; 'James Aldridge' > Cc: ris-int at ripe.net > Subject: Re: FW: [ris-int] Logging on to rrcs > > > --On Tuesday, 13 July, 2004 15:44 +0200 Matthew Williams > > wrote: > > Hi there, > > > > Please add me to users who can logon to rrcs :) > > > > Please open a ticket using "stt ops" or via the form on iii > > James > > > Cheers, > > Matthew > > > >> -----Original Message----- > >> From: ris-int-admin at ripe.net [mailto:ris-int-admin at ripe.net] On > >> Behalf Of Arife Vural > >> Sent: 13 July 2004 15:43 > >> To: Matthew Williams > >> Cc: ris-int at ripe.net > >> Subject: Re: [ris-int] Logging on to rrcs > >> > >> > >> > >> Hi Matthew, > >> > >> It looks your username is not in /etc/passwd file on RRCs. Can you > >> send an e-mail to OPS to add? > >> > >> Arife > >> > >> On Tue, Jul 13, 2004 at 03:37:02PM +0200, Arife Vural wrote: > >> > > >> > Hi Matthew, > >> > > >> > > I seem to have some probs logging on.... (all rrcs?) > >> > > > >> > > >> > You have to login by your username, and then if you need you can > >> > run sudo command switch to risops or root user. After Linux > >> > migration, OPS changed login to RRC boxes from risops to > individual > >> > users. This way it would more easy for OPS to keep track > who runs > >> > which command and so. > >> > > >> > BTW, if you need to connect BGPD on RRCs you do not need > to loging > >> > box, you can run, > >> > > >> > telnet rrc031 2605 > >> > > >> > That connection is open only RIPE NCC prefix. > >> > > >> > Arife > >> > > >> > > matthew at cow at 15:22:15:~$ ssh rrc031 -l risops > >> > > Warning: Permanently added 'rrc031,193.0.0.232' (RSA) to > >> the list of > >> > > known hosts. Permission denied > (publickey,keyboard-interactive). > >> > > > >> > > matthew at cow at 15:22:20:~$ ssh rrc021 -l risops > Permission denied > >> > > (publickey,keyboard-interactive). > >> > > > >> > > Cheers, > >> > > Matthew > >> > > > > > -- > James Aldridge, Network Engineer, New Projects Group, RIPE NCC > Tel: +31 20 535 4421 Fax: +31 20 535 4445 GSM: +31 6 5247 6932 > > PGP Key Fingerprint: 8F8F D923 48E8 FB76 8DD1 60CB 5003 859C F4BB E729 > From wilhelm at ripe.net Tue Jul 13 16:55:16 2004 From: wilhelm at ripe.net (Rene Wilhelm) Date: Tue, 13 Jul 2004 16:55:16 +0200 Subject: FW: [ris-int] Logging on to rrcs In-Reply-To: Message from James Aldridge of "Tue, 13 Jul 2004 16:10:05 +0200." <69EAFDCB7616C8860BDF0D6C@guest-wv-22.ripe.net> Message-ID: <200407131455.i6DEtG4c006248@birch.ripe.net> Hi James, > Matthew wrote: > > > > > Please add me to users who can logon to rrcs :) > > > > Please open a ticket using "stt ops" or via the form on iii > > James while I can understand mailto:ops, I still have difficulty seeing any benefit in "stt" or webform. What difference does it make to ops? Do you (yes you're one of "them" now:-) have seperate queues for each (sub)category? Or are these purely administrative, to see how many tickets in which category were handled by which person? Why does the user have to classify his ticket? isn't that better done by ops? -- Rene From matthew at ripe.net Tue Jul 13 16:54:40 2004 From: matthew at ripe.net (Matthew Williams) Date: Tue, 13 Jul 2004 16:54:40 +0200 Subject: [ris-int] Re: rrc12 In-Reply-To: <20040709132216.GD30660@ripe.net> Message-ID: <002901c468e9$5406d8a0$1f0200c1@rockstar> Did anything happen there? Cheers, Matthew > -----Original Message----- > From: ris-int-admin at ripe.net [mailto:ris-int-admin at ripe.net] > On Behalf Of Arife Vural > Sent: 09 July 2004 15:22 > To: Matthew Williams > Cc: ris-int at ripe.net > Subject: Re: [ris-int] Re: rrc12 > > > > > Arnold Nipper? :) > > I see :-) > > > Please remind him to forward my mail about RRC12. > > I guess we are not in their member mailinglist. > > Arife > > > > > Cheers, > > Matthew > > > > > -----Original Message----- > > > From: ris-int-admin at ripe.net [mailto:ris-int-admin at ripe.net] > > > On Behalf Of Arife Vural > > > Sent: 09 July 2004 15:03 > > > To: Matthew Williams > > > Cc: ris-int at ripe.net > > > Subject: Re: [ris-int] Re: rrc12 > > > > > > > > > > > > > Have you spoken to Arnold about sync effort? I'll put something > > > > together for ris-users and forward the contents to him > for dist on > > > > their tech-list. > > > > > > Sorry missed this e-mail. Can you tell me more what I have to > > > talk about with Arno? > > > > > > Arife > > > > > > > > > > > Cheers, > > > > Matthew > > > > > > > > > -----Original Message----- > > > > > From: ris-int-admin at ripe.net > [mailto:ris-int-admin at ripe.net] On > > > > > Behalf Of Arife > Vural > > > > > Sent: 07 July 2004 13:58 > > > > > To: Matthew Williams > > > > > Cc: ris-int at ripe.net > > > > > Subject: Re: [ris-int] Re: rrc12 > > > > > > > > > > > > > > > > > > > > BTW, we have already got quite few peers at DE-CIX. Vasco is > > > > > busy to clean up tickets. > > > > > > > > > > Arife > > > > > > > > > > On Wed, Jul 07, 2004 at 01:47:54PM +0200, Arife Vural wrote: > > > > > > > > > > > > Hi Matthew, > > > > > > > > > > > > You can announce it. Rawdata link, and peering info > pages are > > > > > > in place. Also updated Looking Glass. I could not finish > > > rest of CGIs > > > > > > yet, because at the same time, I'm doing documentation > > > about what > > > > > > needs to be change when a new RRC is added. It takes time. > > > > > > > > > > > > I will finish updating CGIs tomorrow with some bug fixes. > > > > > > > > > > > > Arife > > > > > > > > > > > > On Wed, Jul 07, 2004 at 01:09:45PM +0200, Matthew > > > Williams wrote: > > > > > > > Hi Arife, > > > > > > > > > > > > > > Are we ready to announce RRC12? > > > > > > > > > > > > > > Cheers, > > > > > > > Matthew > > > > > > > > > From arife at ripe.net Tue Jul 13 17:00:20 2004 From: arife at ripe.net (Arife Vural) Date: Tue, 13 Jul 2004 17:00:20 +0200 Subject: [ris-int] Re: rrc12 In-Reply-To: <002901c468e9$5406d8a0$1f0200c1@rockstar> References: <20040709132216.GD30660@ripe.net> <002901c468e9$5406d8a0$1f0200c1@rockstar> Message-ID: <20040713150019.GA5682@ripe.net> > Did anything happen there? Yes, he said he forward your e-mail to list on of his e-mail. You can follow the thread from xrtt. Arife > > Cheers, > Matthew > > > -----Original Message----- > > From: ris-int-admin at ripe.net [mailto:ris-int-admin at ripe.net] > > On Behalf Of Arife Vural > > Sent: 09 July 2004 15:22 > > To: Matthew Williams > > Cc: ris-int at ripe.net > > Subject: Re: [ris-int] Re: rrc12 > > > > > > > > > Arnold Nipper? :) > > > > I see :-) > > > > > Please remind him to forward my mail about RRC12. > > > > I guess we are not in their member mailinglist. > > > > Arife > > > > > > > > Cheers, > > > Matthew > > > > > > > -----Original Message----- > > > > From: ris-int-admin at ripe.net [mailto:ris-int-admin at ripe.net] > > > > On Behalf Of Arife Vural > > > > Sent: 09 July 2004 15:03 > > > > To: Matthew Williams > > > > Cc: ris-int at ripe.net > > > > Subject: Re: [ris-int] Re: rrc12 > > > > > > > > > > > > > > > > > Have you spoken to Arnold about sync effort? I'll put something > > > > > together for ris-users and forward the contents to him > > for dist on > > > > > their tech-list. > > > > > > > > Sorry missed this e-mail. Can you tell me more what I have to > > > > talk about with Arno? > > > > > > > > Arife > > > > > > > > > > > > > > Cheers, > > > > > Matthew > > > > > > > > > > > -----Original Message----- > > > > > > From: ris-int-admin at ripe.net > > [mailto:ris-int-admin at ripe.net] On > > > > > > Behalf Of Arife > > Vural > > > > > > Sent: 07 July 2004 13:58 > > > > > > To: Matthew Williams > > > > > > Cc: ris-int at ripe.net > > > > > > Subject: Re: [ris-int] Re: rrc12 > > > > > > > > > > > > > > > > > > > > > > > > BTW, we have already got quite few peers at DE-CIX. Vasco is > > > > > > busy to clean up tickets. > > > > > > > > > > > > Arife > > > > > > > > > > > > On Wed, Jul 07, 2004 at 01:47:54PM +0200, Arife Vural wrote: > > > > > > > > > > > > > > Hi Matthew, > > > > > > > > > > > > > > You can announce it. Rawdata link, and peering info > > pages are > > > > > > > in place. Also updated Looking Glass. I could not finish > > > > rest of CGIs > > > > > > > yet, because at the same time, I'm doing documentation > > > > about what > > > > > > > needs to be change when a new RRC is added. It takes time. > > > > > > > > > > > > > > I will finish updating CGIs tomorrow with some bug fixes. > > > > > > > > > > > > > > Arife > > > > > > > > > > > > > > On Wed, Jul 07, 2004 at 01:09:45PM +0200, Matthew > > > > Williams wrote: > > > > > > > > Hi Arife, > > > > > > > > > > > > > > > > Are we ready to announce RRC12? > > > > > > > > > > > > > > > > Cheers, > > > > > > > > Matthew > > > > > > > > > > > > From matthew at ripe.net Tue Jul 13 17:18:08 2004 From: matthew at ripe.net (Matthew Williams) Date: Tue, 13 Jul 2004 17:18:08 +0200 Subject: [ris-int] Re: rrc12 In-Reply-To: <20040713150019.GA5682@ripe.net> Message-ID: <002d01c468ec$9a9393f0$1f0200c1@rockstar> > You can follow the thread from xrtt. Thanks for the pointer. Another wonderful piece of sw engineering to make our lives easier ;) Cheers, Matthew > -----Original Message----- > From: Arife Vural [mailto:arife at ripe.net] > Sent: 13 July 2004 17:00 > To: Matthew Williams > Cc: ris-int at ripe.net > Subject: Re: [ris-int] Re: rrc12 > > > > > Did anything happen there? > > Yes, he said he forward your e-mail to list on of his e-mail. > You can follow the thread from xrtt. > > Arife > > > > > Cheers, > > Matthew > > > > > -----Original Message----- > > > From: ris-int-admin at ripe.net [mailto:ris-int-admin at ripe.net] > > > On Behalf Of Arife Vural > > > Sent: 09 July 2004 15:22 > > > To: Matthew Williams > > > Cc: ris-int at ripe.net > > > Subject: Re: [ris-int] Re: rrc12 > > > > > > > > > > > > > Arnold Nipper? :) > > > > > > I see :-) > > > > > > > Please remind him to forward my mail about RRC12. > > > > > > I guess we are not in their member mailinglist. > > > > > > Arife > > > > > > > > > > > Cheers, > > > > Matthew > > > > > > > > > -----Original Message----- > > > > > From: ris-int-admin at ripe.net > [mailto:ris-int-admin at ripe.net] On > > > > > Behalf Of Arife Vural > > > > > Sent: 09 July 2004 15:03 > > > > > To: Matthew Williams > > > > > Cc: ris-int at ripe.net > > > > > Subject: Re: [ris-int] Re: rrc12 > > > > > > > > > > > > > > > > > > > > > Have you spoken to Arnold about sync effort? I'll put > > > > > > something together for ris-users and forward the > contents to > > > > > > him > > > for dist on > > > > > > their tech-list. > > > > > > > > > > Sorry missed this e-mail. Can you tell me more what I have to > > > > > talk about with Arno? > > > > > > > > > > Arife > > > > > > > > > > > > > > > > > Cheers, > > > > > > Matthew > > > > > > > > > > > > > -----Original Message----- > > > > > > > From: ris-int-admin at ripe.net > > > [mailto:ris-int-admin at ripe.net] On > > > > > > > Behalf Of Arife > > > Vural > > > > > > > Sent: 07 July 2004 13:58 > > > > > > > To: Matthew Williams > > > > > > > Cc: ris-int at ripe.net > > > > > > > Subject: Re: [ris-int] Re: rrc12 > > > > > > > > > > > > > > > > > > > > > > > > > > > > BTW, we have already got quite few peers at > DE-CIX. Vasco is > > > > > > > busy to clean up tickets. > > > > > > > > > > > > > > Arife > > > > > > > > > > > > > > On Wed, Jul 07, 2004 at 01:47:54PM +0200, Arife > Vural wrote: > > > > > > > > > > > > > > > > Hi Matthew, > > > > > > > > > > > > > > > > You can announce it. Rawdata link, and peering info > > > pages are > > > > > > > > in place. Also updated Looking Glass. I could not finish > > > > > rest of CGIs > > > > > > > > yet, because at the same time, I'm doing documentation > > > > > about what > > > > > > > > needs to be change when a new RRC is added. It > takes time. > > > > > > > > > > > > > > > > I will finish updating CGIs tomorrow with some > bug fixes. > > > > > > > > > > > > > > > > Arife > > > > > > > > > > > > > > > > On Wed, Jul 07, 2004 at 01:09:45PM +0200, Matthew > > > > > Williams wrote: > > > > > > > > > Hi Arife, > > > > > > > > > > > > > > > > > > Are we ready to announce RRC12? > > > > > > > > > > > > > > > > > > Cheers, > > > > > > > > > Matthew > > > > > > > > > > > > > > > > From alexis at ripe.net Wed Jul 14 13:17:01 2004 From: alexis at ripe.net (Alexis Yushin) Date: Wed, 14 Jul 2004 13:17:01 +0200 (CEST) Subject: [ris-int] Re: [MAILER-DAEMON@ripe.net: Undelivered Mail Returned to Sender] In-Reply-To: <20040714020040.GA5097@ripe.net> from "Matthew Williams" at Jul 14, 2004 04:00:40 AM Message-ID: <200407141117.i6EBH1fv030516@birch.ripe.net> Arife, We need to add risops to the trusted users class in sendmail.cf on weesp. Something like FEATURE(`use_ct_file') dnl and /etc/mail/trusted-users uucp root daemon risops So myASn can use reply-to address forwarded to /dev/null Alexis Once Matthew Williams wrote: >Hi Alexis, > >Working on this? > >Cheers, >Matthew > >----- Forwarded message from Mail Delivery System ----- > >X-Recipient: >Date: Tue, 13 Jul 2004 23:43:50 +0200 (CEST) >From: MAILER-DAEMON at ripe.net (Mail Delivery System) >Subject: Undelivered Mail Returned to Sender >To: risops at ripe.net > >Content-Description: Notification >This is the Postfix program at host postman.ripe.net. > >I'm sorry to have to inform you that the message returned >below could not be delivered to one or more destinations. > >For further assistance, please send mail to > >If you do so, please include this problem report. You can >delete your own text from the message returned below. > > The Postfix program > >: host mail.linkey.ru[213.159.99.4] said: 550 sorry, no > mailbox here by that name (#5.1.1 - chkusr) > >Content-Description: Delivery error report >Reporting-MTA: dns; postman.ripe.net >Arrival-Date: Tue, 13 Jul 2004 23:43:50 +0200 (CEST) > >Final-Recipient: rfc822; asnalarm at linkey.ru >Action: failed >Status: 5.0.0 >Diagnostic-Code: X-Postfix; host mail.linkey.ru[213.159.99.4] said: 550 sorry, > no mailbox here by that name (#5.1.1 - chkusr) > >Content-Description: Undelivered Message >Date: Tue, 13 Jul 2004 21:43:49 GMT >From: myASn Notifications >To: asnalarm at linkey.ru >Subject: New alarms for 13302 >X-RIPE-Spam-Level: >X-RIPE-Spam-Status: N 0.111983 / 0.0 / 0.0 / disabled >X-RIPE-Signature: b5599a70a52cbd8205f40bab1f24afd6 > > >Dear myASn contact, > >New alarms were detected for 13302. Please find the details below. Depending on your detail >level settings you might not see all the events. Please use the web interface for further details. > >-- myASn System > > >Transit alarm 713 (Transit), 213.159.96.0/19 (exceptions not shown), myASn: , Their ASn: , HDT: 60, HDE: 1, TTL: 3600 >.=------+-----------------+---------+----------+---------------+--------------------------+--------------------------+------=. >| RRC | Prefix | AS Path | Conflict | Peer | UTC First | UTC Last | Count | >|=------+-----------------+---------+----------+---------------+--------------------------+--------------------------+------=| >| rrc00 | 213.159.96.0/19 | | | 129.250.0.232 | Tue Jul 13 21:16:35 2004 | Tue Jul 13 21:16:35 2004 | 1 | >'=------+-----------------+---------+----------+---------------+--------------------------+--------------------------+------=' > > >----- End forwarded message ----- > >-- >>Matthew Williams >>Customer Liaison Engineer >>RIPE - Network Coordination Centre (www.ripe.net) > From arife at ripe.net Wed Jul 14 13:56:22 2004 From: arife at ripe.net (Arife Vural) Date: Wed, 14 Jul 2004 13:56:22 +0200 Subject: [ris-int] [alexis@ripe.net: Re: [MAILER-DAEMON@ripe.net: Undelivered Mail Returned to Sender]] Message-ID: <20040714115622.GB10817@ripe.net> Hi guys, Can we do this? Arife ----- Forwarded message from Alexis Yushin ----- From: Alexis Yushin To: matthew at ripe.net (Matthew Williams) Subject: Re: [MAILER-DAEMON at ripe.net: Undelivered Mail Returned to Sender] Date: Wed, 14 Jul 2004 13:17:01 +0200 (CEST) Cc: alexis at ripe.net (Alexis Yushin), arife at ripe.net (Arife Vural), ris-int at ripe.net Arife, We need to add risops to the trusted users class in sendmail.cf on weesp. Something like FEATURE(`use_ct_file') dnl and /etc/mail/trusted-users uucp root daemon risops So myASn can use reply-to address forwarded to /dev/null Alexis Once Matthew Williams wrote: >Hi Alexis, > >Working on this? > >Cheers, >Matthew > >----- Forwarded message from Mail Delivery System ----- > >X-Recipient: >Date: Tue, 13 Jul 2004 23:43:50 +0200 (CEST) >From: MAILER-DAEMON at ripe.net (Mail Delivery System) >Subject: Undelivered Mail Returned to Sender >To: risops at ripe.net > >Content-Description: Notification >This is the Postfix program at host postman.ripe.net. > >I'm sorry to have to inform you that the message returned >below could not be delivered to one or more destinations. > >For further assistance, please send mail to > >If you do so, please include this problem report. You can >delete your own text from the message returned below. > > The Postfix program > >: host mail.linkey.ru[213.159.99.4] said: 550 sorry, no > mailbox here by that name (#5.1.1 - chkusr) > >Content-Description: Delivery error report >Reporting-MTA: dns; postman.ripe.net >Arrival-Date: Tue, 13 Jul 2004 23:43:50 +0200 (CEST) > >Final-Recipient: rfc822; asnalarm at linkey.ru >Action: failed >Status: 5.0.0 >Diagnostic-Code: X-Postfix; host mail.linkey.ru[213.159.99.4] said: 550 sorry, > no mailbox here by that name (#5.1.1 - chkusr) > >Content-Description: Undelivered Message >Date: Tue, 13 Jul 2004 21:43:49 GMT >From: myASn Notifications >To: asnalarm at linkey.ru >Subject: New alarms for 13302 >X-RIPE-Spam-Level: >X-RIPE-Spam-Status: N 0.111983 / 0.0 / 0.0 / disabled >X-RIPE-Signature: b5599a70a52cbd8205f40bab1f24afd6 > > >Dear myASn contact, > >New alarms were detected for 13302. Please find the details below. Depending on your detail >level settings you might not see all the events. Please use the web interface for further details. > >-- myASn System > > >Transit alarm 713 (Transit), 213.159.96.0/19 (exceptions not shown), myASn: , Their ASn: , HDT: 60, HDE: 1, TTL: 3600 >.=------+-----------------+---------+----------+---------------+--------------------------+--------------------------+------=. >| RRC | Prefix | AS Path | Conflict | Peer | UTC First | UTC Last | Count | >|=------+-----------------+---------+----------+---------------+--------------------------+--------------------------+------=| >| rrc00 | 213.159.96.0/19 | | | 129.250.0.232 | Tue Jul 13 21:16:35 2004 | Tue Jul 13 21:16:35 2004 | 1 | >'=------+-----------------+---------+----------+---------------+--------------------------+--------------------------+------=' > > >----- End forwarded message ----- > >-- >>Matthew Williams >>Customer Liaison Engineer >>RIPE - Network Coordination Centre (www.ripe.net) > ----- End forwarded message ----- From arife at ripe.net Wed Jul 14 13:58:26 2004 From: arife at ripe.net (Arife Vural) Date: Wed, 14 Jul 2004 13:58:26 +0200 Subject: [ris-int] Re: [MAILER-DAEMON@ripe.net: Undelivered Mail Returned to Sender] In-Reply-To: <200407141117.i6EBH1fv030516@birch.ripe.net> References: <20040714020040.GA5097@ripe.net> <200407141117.i6EBH1fv030516@birch.ripe.net> Message-ID: <20040714115826.GC10817@ripe.net> Alexis, Could you change myASn config to send new user request to ris-request at ripe.net? This way those request would be ticketized. Arife On Wed, Jul 14, 2004 at 01:17:01PM +0200, Alexis Yushin wrote: > Arife, > > We need to add risops to the trusted users class in sendmail.cf on weesp. > Something like > > FEATURE(`use_ct_file') dnl > > and > > /etc/mail/trusted-users > uucp > root > daemon > risops > > So myASn can use reply-to address forwarded to /dev/null > > Alexis > > > Once Matthew Williams wrote: > >Hi Alexis, > > > >Working on this? > > > >Cheers, > >Matthew > > > >----- Forwarded message from Mail Delivery System ----- > > > >X-Recipient: > >Date: Tue, 13 Jul 2004 23:43:50 +0200 (CEST) > >From: MAILER-DAEMON at ripe.net (Mail Delivery System) > >Subject: Undelivered Mail Returned to Sender > >To: risops at ripe.net > > > >Content-Description: Notification > >This is the Postfix program at host postman.ripe.net. > > > >I'm sorry to have to inform you that the message returned > >below could not be delivered to one or more destinations. > > > >For further assistance, please send mail to > > > >If you do so, please include this problem report. You can > >delete your own text from the message returned below. > > > > The Postfix program > > > >: host mail.linkey.ru[213.159.99.4] said: 550 sorry, no > > mailbox here by that name (#5.1.1 - chkusr) > > > >Content-Description: Delivery error report > >Reporting-MTA: dns; postman.ripe.net > >Arrival-Date: Tue, 13 Jul 2004 23:43:50 +0200 (CEST) > > > >Final-Recipient: rfc822; asnalarm at linkey.ru > >Action: failed > >Status: 5.0.0 > >Diagnostic-Code: X-Postfix; host mail.linkey.ru[213.159.99.4] said: 550 sorry, > > no mailbox here by that name (#5.1.1 - chkusr) > > > >Content-Description: Undelivered Message > >Date: Tue, 13 Jul 2004 21:43:49 GMT > >From: myASn Notifications > >To: asnalarm at linkey.ru > >Subject: New alarms for 13302 > >X-RIPE-Spam-Level: > >X-RIPE-Spam-Status: N 0.111983 / 0.0 / 0.0 / disabled > >X-RIPE-Signature: b5599a70a52cbd8205f40bab1f24afd6 > > > > > >Dear myASn contact, > > > >New alarms were detected for 13302. Please find the details below. Depending on your detail > >level settings you might not see all the events. Please use the web interface for further details. > > > >-- myASn System > > > > > >Transit alarm 713 (Transit), 213.159.96.0/19 (exceptions not shown), myASn: , Their ASn: , HDT: 60, HDE: 1, TTL: 3600 > >.=------+-----------------+---------+----------+---------------+--------------------------+--------------------------+------=. > >| RRC | Prefix | AS Path | Conflict | Peer | UTC First | UTC Last | Count | > >|=------+-----------------+---------+----------+---------------+--------------------------+--------------------------+------=| > >| rrc00 | 213.159.96.0/19 | | | 129.250.0.232 | Tue Jul 13 21:16:35 2004 | Tue Jul 13 21:16:35 2004 | 1 | > >'=------+-----------------+---------+----------+---------------+--------------------------+--------------------------+------=' > > > > > >----- End forwarded message ----- > > > >-- > >>Matthew Williams > >>Customer Liaison Engineer > >>RIPE - Network Coordination Centre (www.ripe.net) > > From wilhelm at ripe.net Wed Jul 14 14:32:18 2004 From: wilhelm at ripe.net (Rene Wilhelm) Date: Wed, 14 Jul 2004 14:32:18 +0200 Subject: [ris-int] Reply-To forwarded to /dev/null in myASn messages In-Reply-To: Message from Arife Vural of "Wed, 14 Jul 2004 13:56:22 +0200." <20040714115622.GB10817@ripe.net> Message-ID: <200407141232.i6ECWI4c026188@birch.ripe.net> Hi, > ... myASn can use reply-to address forwarded to /dev/null Are we sure we want that? How often does it happen? Shouldn't there be follow by a risopsy when a notification fails to be delivered? (for permanent failures, either try to get in touch with representatives of the AS to correct the address, or deconfigure the alarm???) -- Rene > Hi guys, > > Can we do this? > > Arife > > ----- Forwarded message from Alexis Yushin ----- > > From: Alexis Yushin > To: matthew at ripe.net (Matthew Williams) > Subject: Re: [MAILER-DAEMON at ripe.net: Undelivered Mail Returned to Sender] > Date: Wed, 14 Jul 2004 13:17:01 +0200 (CEST) > Cc: alexis at ripe.net (Alexis Yushin), arife at ripe.net (Arife Vural), > ris-int at ripe.net > > Arife, > > We need to add risops to the trusted users class in sendmail.cf on weesp. > Something like > > FEATURE(`use_ct_file') dnl > > and > > /etc/mail/trusted-users > uucp > root > daemon > risops > > So myASn can use reply-to address forwarded to /dev/null > > Alexis > > > Once Matthew Williams wrote: > >Hi Alexis, > > > >Working on this? > > > >Cheers, > >Matthew > > > >----- Forwarded message from Mail Delivery System ----- > > > >X-Recipient: > >Date: Tue, 13 Jul 2004 23:43:50 +0200 (CEST) > >From: MAILER-DAEMON at ripe.net (Mail Delivery System) > >Subject: Undelivered Mail Returned to Sender > >To: risops at ripe.net > > > >Content-Description: Notification > >This is the Postfix program at host postman.ripe.net. > > > >I'm sorry to have to inform you that the message returned > >below could not be delivered to one or more destinations. > > > >For further assistance, please send mail to > > > >If you do so, please include this problem report. You can > >delete your own text from the message returned below. > > > > The Postfix program > > > >: host mail.linkey.ru[213.159.99.4] said: 550 sorry, no > > mailbox here by that name (#5.1.1 - chkusr) > > > >Content-Description: Delivery error report > >Reporting-MTA: dns; postman.ripe.net > >Arrival-Date: Tue, 13 Jul 2004 23:43:50 +0200 (CEST) > > > >Final-Recipient: rfc822; asnalarm at linkey.ru > >Action: failed > >Status: 5.0.0 > >Diagnostic-Code: X-Postfix; host mail.linkey.ru[213.159.99.4] said: 550 sorry, > > no mailbox here by that name (#5.1.1 - chkusr) > > > >Content-Description: Undelivered Message > >Date: Tue, 13 Jul 2004 21:43:49 GMT > >From: myASn Notifications > >To: asnalarm at linkey.ru > >Subject: New alarms for 13302 > >X-RIPE-Spam-Level: > >X-RIPE-Spam-Status: N 0.111983 / 0.0 / 0.0 / disabled > >X-RIPE-Signature: b5599a70a52cbd8205f40bab1f24afd6 > > > > > >Dear myASn contact, > > > >New alarms were detected for 13302. Please find the details below. Depending on your detail > >level settings you might not see all the events. Please use the web interface for further details. > > > >-- myASn System > > > > > >Transit alarm 713 (Transit), 213.159.96.0/19 (exceptions not shown), myASn: , Their ASn: , HDT: 60, HDE: 1, TTL: 3600 > >.=------+-----------------+---------+----------+---------------+--------------------------+--------------------------+------=. > >| RRC | Prefix | AS Path | Conflict | Peer | UTC First | UTC Last | Count | > >|=------+-----------------+---------+----------+---------------+--------------------------+--------------------------+------=| > >| rrc00 | 213.159.96.0/19 | | | 129.250.0.232 | Tue Jul 13 21:16:35 2004 | Tue Jul 13 21:16:35 2004 | 1 | > >'=------+-----------------+---------+----------+---------------+--------------------------+--------------------------+------=' > > > > > >----- End forwarded message ----- > > > >-- > >>Matthew Williams > >>Customer Liaison Engineer > >>RIPE - Network Coordination Centre (www.ripe.net) > > > > ----- End forwarded message ----- > From arife at ripe.net Wed Jul 14 14:36:32 2004 From: arife at ripe.net (Arife Vural) Date: Wed, 14 Jul 2004 14:36:32 +0200 Subject: [ris-int] Re: [MAILER-DAEMON@ripe.net: Undelivered Mail Returned to Sender] In-Reply-To: <20040714115826.GC10817@ripe.net> References: <20040714020040.GA5097@ripe.net> <200407141117.i6EBH1fv030516@birch.ripe.net> <20040714115826.GC10817@ripe.net> Message-ID: <20040714123632.GD10817@ripe.net> Hoi Alexis, > Could you change myASn config to send new user request to > ris-request at ripe.net? This way those request would be > ticketized. Please ignore this request by now. After talked with Matthew, we decided to keep it as risops for a while. Arife > > Arife > > On Wed, Jul 14, 2004 at 01:17:01PM +0200, Alexis Yushin wrote: > > Arife, > > > > We need to add risops to the trusted users class in sendmail.cf on weesp. > > Something like > > > > FEATURE(`use_ct_file') dnl > > > > and > > > > /etc/mail/trusted-users > > uucp > > root > > daemon > > risops > > > > So myASn can use reply-to address forwarded to /dev/null > > > > Alexis > > > > > > Once Matthew Williams wrote: > > >Hi Alexis, > > > > > >Working on this? > > > > > >Cheers, > > >Matthew > > > > > >----- Forwarded message from Mail Delivery System ----- > > > > > >X-Recipient: > > >Date: Tue, 13 Jul 2004 23:43:50 +0200 (CEST) > > >From: MAILER-DAEMON at ripe.net (Mail Delivery System) > > >Subject: Undelivered Mail Returned to Sender > > >To: risops at ripe.net > > > > > >Content-Description: Notification > > >This is the Postfix program at host postman.ripe.net. > > > > > >I'm sorry to have to inform you that the message returned > > >below could not be delivered to one or more destinations. > > > > > >For further assistance, please send mail to > > > > > >If you do so, please include this problem report. You can > > >delete your own text from the message returned below. > > > > > > The Postfix program > > > > > >: host mail.linkey.ru[213.159.99.4] said: 550 sorry, no > > > mailbox here by that name (#5.1.1 - chkusr) > > > > > >Content-Description: Delivery error report > > >Reporting-MTA: dns; postman.ripe.net > > >Arrival-Date: Tue, 13 Jul 2004 23:43:50 +0200 (CEST) > > > > > >Final-Recipient: rfc822; asnalarm at linkey.ru > > >Action: failed > > >Status: 5.0.0 > > >Diagnostic-Code: X-Postfix; host mail.linkey.ru[213.159.99.4] said: 550 sorry, > > > no mailbox here by that name (#5.1.1 - chkusr) > > > > > >Content-Description: Undelivered Message > > >Date: Tue, 13 Jul 2004 21:43:49 GMT > > >From: myASn Notifications > > >To: asnalarm at linkey.ru > > >Subject: New alarms for 13302 > > >X-RIPE-Spam-Level: > > >X-RIPE-Spam-Status: N 0.111983 / 0.0 / 0.0 / disabled > > >X-RIPE-Signature: b5599a70a52cbd8205f40bab1f24afd6 > > > > > > > > >Dear myASn contact, > > > > > >New alarms were detected for 13302. Please find the details below. Depending on your detail > > >level settings you might not see all the events. Please use the web interface for further details. > > > > > >-- myASn System > > > > > > > > >Transit alarm 713 (Transit), 213.159.96.0/19 (exceptions not shown), myASn: , Their ASn: , HDT: 60, HDE: 1, TTL: 3600 > > >.=------+-----------------+---------+----------+---------------+--------------------------+--------------------------+------=. > > >| RRC | Prefix | AS Path | Conflict | Peer | UTC First | UTC Last | Count | > > >|=------+-----------------+---------+----------+---------------+--------------------------+--------------------------+------=| > > >| rrc00 | 213.159.96.0/19 | | | 129.250.0.232 | Tue Jul 13 21:16:35 2004 | Tue Jul 13 21:16:35 2004 | 1 | > > >'=------+-----------------+---------+----------+---------------+--------------------------+--------------------------+------=' > > > > > > > > >----- End forwarded message ----- > > > > > >-- > > >>Matthew Williams > > >>Customer Liaison Engineer > > >>RIPE - Network Coordination Centre (www.ripe.net) > > > From matthew at ripe.net Wed Jul 14 14:46:19 2004 From: matthew at ripe.net (Matthew Williams) Date: Wed, 14 Jul 2004 14:46:19 +0200 Subject: [ris-int] Reply-To forwarded to /dev/null in myASn messages In-Reply-To: <200407141232.i6ECWI4c026188@birch.ripe.net> Message-ID: <044801c469a0$8f779840$1f0200c1@rockstar> > Shouldn't there be follow by a risopsy when a notification > fails to be delivered? (for permanent failures, either try Quite unlikely, if I know that alarm notifications were successfully sent to my inbox. We could possibly set up a few fake risops accounts without fwd to /dev/null to monitor that the prob at least wasn't internal. If you have other ideas then pls share them :) Cheers, Matthew > -----Original Message----- > From: ris-int-admin at ripe.net [mailto:ris-int-admin at ripe.net] > On Behalf Of Rene Wilhelm > Sent: 14 July 2004 14:32 > To: Arife Vural > Cc: ris-int at ripe.net > Subject: Re: [ris-int] Reply-To forwarded to /dev/null in > myASn messages > > > Hi, > > > > ... myASn can use reply-to address forwarded to /dev/null > > Are we sure we want that? How often does it happen? > Shouldn't there be follow by a risopsy when a notification > fails to be delivered? (for permanent failures, either try > to get in touch with representatives of the AS to correct the > address, or deconfigure the alarm???) > > -- Rene > > > > > Hi guys, > > > > Can we do this? > > > > Arife > > > > ----- Forwarded message from Alexis Yushin ----- > > > > From: Alexis Yushin > > To: matthew at ripe.net (Matthew Williams) > > Subject: Re: [MAILER-DAEMON at ripe.net: Undelivered Mail Returned to > > Sender] > > Date: Wed, 14 Jul 2004 13:17:01 +0200 (CEST) > > Cc: alexis at ripe.net (Alexis Yushin), arife at ripe.net (Arife Vural), > > ris-int at ripe.net > > > > Arife, > > > > We need to add risops to the trusted users class in sendmail.cf on > > weesp. Something like > > > > FEATURE(`use_ct_file') dnl > > > > and > > > > /etc/mail/trusted-users > > uucp > > root > > daemon > > risops > > > > So myASn can use reply-to address forwarded to /dev/null > > > > Alexis > > > > > > Once Matthew Williams wrote: > > >Hi Alexis, > > > > > >Working on this? > > > > > >Cheers, > > >Matthew > > > > > >----- Forwarded message from Mail Delivery System > > > ----- > > > > > >X-Recipient: > > >Date: Tue, 13 Jul 2004 23:43:50 +0200 (CEST) > > >From: MAILER-DAEMON at ripe.net (Mail Delivery System) > > >Subject: Undelivered Mail Returned to Sender > > >To: risops at ripe.net > > > > > >Content-Description: Notification > > >This is the Postfix program at host postman.ripe.net. > > > > > >I'm sorry to have to inform you that the message returned > below could > > >not be delivered to one or more destinations. > > > > > >For further assistance, please send mail to > > > > > >If you do so, please include this problem report. You can > delete your > > >own text from the message returned below. > > > > > > The Postfix program > > > > > >: host mail.linkey.ru[213.159.99.4] > said: 550 sorry, no > > > mailbox here by that name (#5.1.1 - chkusr) > > > > > >Content-Description: Delivery error report > > >Reporting-MTA: dns; postman.ripe.net > > >Arrival-Date: Tue, 13 Jul 2004 23:43:50 +0200 (CEST) > > > > > >Final-Recipient: rfc822; asnalarm at linkey.ru > > >Action: failed > > >Status: 5.0.0 > > >Diagnostic-Code: X-Postfix; host > mail.linkey.ru[213.159.99.4] said: 550 sorry, > > > no mailbox here by that name (#5.1.1 - chkusr) > > > > > >Content-Description: Undelivered Message > > >Date: Tue, 13 Jul 2004 21:43:49 GMT > > >From: myASn Notifications > > >To: asnalarm at linkey.ru > > >Subject: New alarms for 13302 > > >X-RIPE-Spam-Level: > > >X-RIPE-Spam-Status: N 0.111983 / 0.0 / 0.0 / disabled > > >X-RIPE-Signature: b5599a70a52cbd8205f40bab1f24afd6 > > > > > > > > >Dear myASn contact, > > > > > >New alarms were detected for 13302. Please find the details below. > > >Depending on your detail level settings you might not see all the > > >events. Please use the web interface for further details. > > > > > >-- myASn System > > > > > > > > >Transit alarm 713 (Transit), 213.159.96.0/19 (exceptions > not shown), > > >myASn: , Their ASn: , HDT: 60, HDE: 1, TTL: 3600 > > > >.=------+-----------------+---------+----------+------------- > --+--------------------------+--------------------------+------=. > > >| RRC | Prefix | AS Path | Conflict | Peer > | UTC First | UTC Last | Count | > > > >|=------+-----------------+---------+----------+------------- > --+--------------------------+--------------------------+------=| > > >| rrc00 | 213.159.96.0/19 | | | > 129.250.0.232 | Tue Jul 13 21:16:35 2004 | Tue Jul 13 > 21:16:35 2004 | 1 | > > > >'=------+-----------------+---------+----------+---------------+----- > > >---------------------+--------------------------+------=' > > > > > > > > >----- End forwarded message ----- > > > > > >-- > > >>Matthew Williams > > >>Customer Liaison Engineer > > >>RIPE - Network Coordination Centre (www.ripe.net) > > > > > > > ----- End forwarded message ----- > > > From matthew at ripe.net Wed Jul 14 14:53:17 2004 From: matthew at ripe.net (Matthew Williams) Date: Wed, 14 Jul 2004 14:53:17 +0200 Subject: [ris-int] Re: [MAILER-DAEMON@ripe.net: Undelivered Mail Returned to Sender] In-Reply-To: <20040714123632.GD10817@ripe.net> Message-ID: <044901c469a1$88c3a1f0$1f0200c1@rockstar> Maybe I should clarify: As much as I like acc creation, during this phase, ie beta testing, I'd like to have too much info rather than too little re: user fb on features or bugs. Xrtt, not being proactive, introduces lags in the info flow that I'd rather avoid right now. The world is Kafka, right? ;) Cheers, Matthew > -----Original Message----- > From: ris-int-admin at ripe.net [mailto:ris-int-admin at ripe.net] > On Behalf Of Arife Vural > Sent: 14 July 2004 14:37 > To: Alexis Yushin > Cc: Matthew Williams; ris-int at ripe.net > Subject: Re: [ris-int] Re: [MAILER-DAEMON at ripe.net: > Undelivered Mail Returned to Sender] > > > > Hoi Alexis, > > > Could you change myASn config to send new user request to > > ris-request at ripe.net? This way those request would be > > ticketized. > > Please ignore this request by now. After talked with Matthew, > we decided to keep it as risops for a while. > > Arife > > > > > Arife > > > > On Wed, Jul 14, 2004 at 01:17:01PM +0200, Alexis Yushin wrote: > > > Arife, > > > > > > We need to add risops to the trusted users class in > sendmail.cf on > > > weesp. Something like > > > > > > FEATURE(`use_ct_file') dnl > > > > > > and > > > > > > /etc/mail/trusted-users > > > uucp > > > root > > > daemon > > > risops > > > > > > So myASn can use reply-to address forwarded to /dev/null > > > > > > Alexis > > > > > > > > > Once Matthew Williams wrote: > > > >Hi Alexis, > > > > > > > >Working on this? > > > > > > > >Cheers, > > > >Matthew > > > > > > > >----- Forwarded message from Mail Delivery System > > > > ----- > > > > > > > >X-Recipient: > > > >Date: Tue, 13 Jul 2004 23:43:50 +0200 (CEST) > > > >From: MAILER-DAEMON at ripe.net (Mail Delivery System) > > > >Subject: Undelivered Mail Returned to Sender > > > >To: risops at ripe.net > > > > > > > >Content-Description: Notification > > > >This is the Postfix program at host postman.ripe.net. > > > > > > > >I'm sorry to have to inform you that the message returned below > > > >could not be delivered to one or more destinations. > > > > > > > >For further assistance, please send mail to > > > > > > > >If you do so, please include this problem report. You can delete > > > >your own text from the message returned below. > > > > > > > > The Postfix program > > > > > > > >: host mail.linkey.ru[213.159.99.4] > said: 550 sorry, no > > > > mailbox here by that name (#5.1.1 - chkusr) > > > > > > > >Content-Description: Delivery error report > > > >Reporting-MTA: dns; postman.ripe.net > > > >Arrival-Date: Tue, 13 Jul 2004 23:43:50 +0200 (CEST) > > > > > > > >Final-Recipient: rfc822; asnalarm at linkey.ru > > > >Action: failed > > > >Status: 5.0.0 > > > >Diagnostic-Code: X-Postfix; host > mail.linkey.ru[213.159.99.4] said: 550 sorry, > > > > no mailbox here by that name (#5.1.1 - chkusr) > > > > > > > >Content-Description: Undelivered Message > > > >Date: Tue, 13 Jul 2004 21:43:49 GMT > > > >From: myASn Notifications > > > >To: asnalarm at linkey.ru > > > >Subject: New alarms for 13302 > > > >X-RIPE-Spam-Level: > > > >X-RIPE-Spam-Status: N 0.111983 / 0.0 / 0.0 / disabled > > > >X-RIPE-Signature: b5599a70a52cbd8205f40bab1f24afd6 > > > > > > > > > > > >Dear myASn contact, > > > > > > > >New alarms were detected for 13302. Please find the > details below. > > > >Depending on your detail level settings you might not > see all the > > > >events. Please use the web interface for further details. > > > > > > > >-- myASn System > > > > > > > > > > > >Transit alarm 713 (Transit), 213.159.96.0/19 (exceptions not > > > >shown), myASn: , Their ASn: , HDT: 60, HDE: 1, TTL: 3600 > > > > >.=------+-----------------+---------+----------+------------- > --+--------------------------+--------------------------+------=. > > > >| RRC | Prefix | AS Path | Conflict | Peer > | UTC First | UTC Last | Count | > > > > >|=------+-----------------+---------+----------+------------- > --+--------------------------+--------------------------+------=| > > > >| rrc00 | 213.159.96.0/19 | | | > 129.250.0.232 | Tue Jul 13 21:16:35 2004 | Tue Jul 13 > 21:16:35 2004 | 1 | > > > > >'=------+-----------------+---------+----------+---------------+--- > > > >-----------------------+--------------------------+------=' > > > > > > > > > > > >----- End forwarded message ----- > > > > > > > >-- > > > >>Matthew Williams > > > >>Customer Liaison Engineer > > > >>RIPE - Network Coordination Centre (www.ripe.net) > > > > > From wilhelm at ripe.net Wed Jul 14 15:09:28 2004 From: wilhelm at ripe.net (Rene Wilhelm) Date: Wed, 14 Jul 2004 15:09:28 +0200 Subject: [ris-int] Reply-To forwarded to /dev/null in myASn messages In-Reply-To: Message from "Matthew Williams" of "Wed, 14 Jul 2004 14:46:19 +0200." <044801c469a0$8f779840$1f0200c1@rockstar> Message-ID: <200407141309.i6ED9S4c008967@birch.ripe.net> >> Shouldn't there be follow up by a risopsy when a notification >> fails to be delivered? (for permanent failures, either try > Quite unlikely, if I know that alarm notifications were successfully > sent to my inbox. Sorry, I don't understand your reply. If a mail from the myASn system bounces, someone should in my opinion take action. Either the user made a mistake, typo, entering the e-mail address in the myASn system, or he has left the ISP owning the ASn. risops could try to get in touch with the ASn owner, to get the email address corrrected (remember, we are running a _service_ ) or when that fails remove the address from the alarm system (no point polluting internal an external systems with e-mails you know will bounce back) Also, when the human recipients behind a remote e-mail change, they might reply, querying what the message was about; it's not polite to silently ignore such one-off replies. -- Rene > > We need to add risops to the trusted users class in sendmail.cf on > > weesp. Something like > > So myASn can use reply-to address forwarded to /dev/null > > > > Once Matthew Williams wrote: > > >Hi Alexis, > > > > > >Working on this? > > > > > >Cheers, > > >Matthew > > > > > >----- Forwarded message from Mail Delivery System > > > ----- > > > > > >X-Recipient: > > >Date: Tue, 13 Jul 2004 23:43:50 +0200 (CEST) > > >From: MAILER-DAEMON at ripe.net (Mail Delivery System) > > >Subject: Undelivered Mail Returned to Sender > > >To: risops at ripe.net From alexis at ripe.net Wed Jul 14 15:15:21 2004 From: alexis at ripe.net (Alexis Yushin) Date: Wed, 14 Jul 2004 15:15:21 +0200 (CEST) Subject: [ris-int] Re: [MAILER-DAEMON@ripe.net: Undelivered Mail Returned to Sender] In-Reply-To: <20040714115826.GC10817@ripe.net> from "Arife Vural" at Jul 14, 2004 01:58:26 PM Message-ID: <200407141315.i6EDFLj3011248@birch.ripe.net> Its done. Alexis Once Arife Vural wrote: >Alexis, > >Could you change myASn config to send new user request to >ris-request at ripe.net? This way those request would be >ticketized. > >Arife > >On Wed, Jul 14, 2004 at 01:17:01PM +0200, Alexis Yushin wrote: >> Arife, >> >> We need to add risops to the trusted users class in sendmail.cf on weesp. >> Something like >> >> FEATURE(`use_ct_file') dnl >> >> and >> >> /etc/mail/trusted-users >> uucp >> root >> daemon >> risops >> >> So myASn can use reply-to address forwarded to /dev/null >> >> Alexis >> >> >> Once Matthew Williams wrote: >> >Hi Alexis, >> > >> >Working on this? >> > >> >Cheers, >> >Matthew >> > >> >----- Forwarded message from Mail Delivery System ----- >> > >> >X-Recipient: >> >Date: Tue, 13 Jul 2004 23:43:50 +0200 (CEST) >> >From: MAILER-DAEMON at ripe.net (Mail Delivery System) >> >Subject: Undelivered Mail Returned to Sender >> >To: risops at ripe.net >> > >> >Content-Description: Notification >> >This is the Postfix program at host postman.ripe.net. >> > >> >I'm sorry to have to inform you that the message returned >> >below could not be delivered to one or more destinations. >> > >> >For further assistance, please send mail to >> > >> >If you do so, please include this problem report. You can >> >delete your own text from the message returned below. >> > >> > The Postfix program >> > >> >: host mail.linkey.ru[213.159.99.4] said: 550 sorry, no >> > mailbox here by that name (#5.1.1 - chkusr) >> > >> >Content-Description: Delivery error report >> >Reporting-MTA: dns; postman.ripe.net >> >Arrival-Date: Tue, 13 Jul 2004 23:43:50 +0200 (CEST) >> > >> >Final-Recipient: rfc822; asnalarm at linkey.ru >> >Action: failed >> >Status: 5.0.0 >> >Diagnostic-Code: X-Postfix; host mail.linkey.ru[213.159.99.4] said: 550 sorry, >> > no mailbox here by that name (#5.1.1 - chkusr) >> > >> >Content-Description: Undelivered Message >> >Date: Tue, 13 Jul 2004 21:43:49 GMT >> >From: myASn Notifications >> >To: asnalarm at linkey.ru >> >Subject: New alarms for 13302 >> >X-RIPE-Spam-Level: >> >X-RIPE-Spam-Status: N 0.111983 / 0.0 / 0.0 / disabled >> >X-RIPE-Signature: b5599a70a52cbd8205f40bab1f24afd6 >> > >> > >> >Dear myASn contact, >> > >> >New alarms were detected for 13302. Please find the details below. Depending on your detail >> >level settings you might not see all the events. Please use the web interface for further details. >> > >> >-- myASn System >> > >> > >> >Transit alarm 713 (Transit), 213.159.96.0/19 (exceptions not shown), myASn: , Their ASn: , HDT: 60, HDE: 1, TTL: 3600 >> >.=------+-----------------+---------+----------+---------------+--------------------------+--------------------------+------=. >> >| RRC | Prefix | AS Path | Conflict | Peer | UTC First | UTC Last | Count | >> >|=------+-----------------+---------+----------+---------------+--------------------------+--------------------------+------=| >> >| rrc00 | 213.159.96.0/19 | | | 129.250.0.232 | Tue Jul 13 21:16:35 2004 | Tue Jul 13 21:16:35 2004 | 1 | >> >'=------+-----------------+---------+----------+---------------+--------------------------+--------------------------+------=' >> > >> > >> >----- End forwarded message ----- >> > >> >-- >> >>Matthew Williams >> >>Customer Liaison Engineer >> >>RIPE - Network Coordination Centre (www.ripe.net) >> > > From matthew at ripe.net Wed Jul 14 15:16:27 2004 From: matthew at ripe.net (Matthew Williams) Date: Wed, 14 Jul 2004 15:16:27 +0200 Subject: [ris-int] Reply-To forwarded to /dev/null in myASn messages In-Reply-To: <200407141309.i6ED9S4c008967@birch.ripe.net> Message-ID: <044b01c469a4$c53870e0$1f0200c1@rockstar> > >> Shouldn't there be follow up by a risopsy when a notification > >> fails to be delivered? (for permanent failures, either try > > > Quite unlikely, if I know that alarm notifications were > successfully > > sent to my inbox. > > Sorry, I don't understand your reply. > > If a mail from the myASn system bounces, someone should in my > opinion take action. Either the user made a mistake, typo, > entering the e-mail address in the myASn system, or he has > left the ISP owning the ASn. risops could try to get in touch > with the ASn owner, to get the email address corrrected > (remember, we are running a _service_ ) or when that fails > remove the address from the alarm system (no point polluting > internal an external systems with e-mails you know will bounce back) I think you are a few months ahead in planning. Now, if reply-to was set to the destination email addr, then we could incorporate a function that would disable the alarm nots after a few bounces. Until then, we need a quick fix. Cheers, Matthew > > Also, when the human recipients behind a remote e-mail change, > they might reply, querying what the message was about; it's > not polite to silently ignore such one-off replies. > > -- Rene > > > > We need to add risops to the trusted users class in sendmail.cf on > > > weesp. Something like > > > So myASn can use reply-to address forwarded to /dev/null > > > > > > Once Matthew Williams wrote: > > > >Hi Alexis, > > > > > > > >Working on this? > > > > > > > >Cheers, > > > >Matthew > > > > > > > >----- Forwarded message from Mail Delivery System > > > > ----- > > > > > > > >X-Recipient: > > > >Date: Tue, 13 Jul 2004 23:43:50 +0200 (CEST) > > > >From: MAILER-DAEMON at ripe.net (Mail Delivery System) > > > >Subject: Undelivered Mail Returned to Sender > > > >To: risops at ripe.net > From matthew at ripe.net Wed Jul 14 15:50:50 2004 From: matthew at ripe.net (Matthew Williams) Date: Wed, 14 Jul 2004 15:50:50 +0200 Subject: [ris-int] Reply-To forwarded to /dev/null in myASn messages In-Reply-To: <044b01c469a4$c53870e0$1f0200c1@rockstar> Message-ID: <045101c469a9$92aedf60$1f0200c1@rockstar> Now, if > reply-to was set to the destination email addr, Error... this should of course be something related to the account itself, not the dest addr. Anyway, I have added disable-after-n-bounces to the requested features page. Cheers, Matthew > -----Original Message----- > From: ris-int-admin at ripe.net [mailto:ris-int-admin at ripe.net] > On Behalf Of Matthew Williams > Sent: 14 July 2004 15:16 > To: 'Rene Wilhelm' > Cc: ris-int at ripe.net; 'Arife Vural' > Subject: RE: [ris-int] Reply-To forwarded to /dev/null in > myASn messages > > > > >> Shouldn't there be follow up by a risopsy when a > notification fails > > >> to be delivered? (for permanent failures, either try > > > > > Quite unlikely, if I know that alarm notifications were > > successfully > > > sent to my inbox. > > > > Sorry, I don't understand your reply. > > > > If a mail from the myASn system bounces, someone should in my > > opinion take action. Either the user made a mistake, typo, > > entering the e-mail address in the myASn system, or he has > > left the ISP owning the ASn. risops could try to get in touch > > with the ASn owner, to get the email address corrrected > > (remember, we are running a _service_ ) or when that fails > > remove the address from the alarm system (no point polluting > > internal an external systems with e-mails you know will bounce back) > > I think you are a few months ahead in planning. Now, if > reply-to was set to the destination email addr, then we could > incorporate a function that would disable the alarm nots > after a few bounces. Until then, we need a quick fix. > > Cheers, > Matthew > > > > > Also, when the human recipients behind a remote e-mail change, > > they might reply, querying what the message was about; it's > > not polite to silently ignore such one-off replies. > > > > -- Rene > > > > > > We need to add risops to the trusted users class in > sendmail.cf on > > > > weesp. Something like So myASn can use reply-to address > forwarded > > > > to /dev/null > > > > > > > > Once Matthew Williams wrote: > > > > >Hi Alexis, > > > > > > > > > >Working on this? > > > > > > > > > >Cheers, > > > > >Matthew > > > > > > > > > >----- Forwarded message from Mail Delivery System > > > > > ----- > > > > > > > > > >X-Recipient: > > > > >Date: Tue, 13 Jul 2004 23:43:50 +0200 (CEST) > > > > >From: MAILER-DAEMON at ripe.net (Mail Delivery System) > > > > >Subject: Undelivered Mail Returned to Sender > > > > >To: risops at ripe.net > > > From colitti at dia.uniroma3.it Wed Jul 14 16:46:41 2004 From: colitti at dia.uniroma3.it (Lorenzo Colitti) Date: Wed, 14 Jul 2004 16:46:41 +0200 Subject: [ris-int] Reply-To forwarded to /dev/null in myASn messages In-Reply-To: <200407141232.i6ECWI4c026188@birch.ripe.net> References: <200407141232.i6ECWI4c026188@birch.ripe.net> Message-ID: <40F54751.1080902@dia.uniroma3.it> Rene Wilhelm wrote: >>... myASn can use reply-to address forwarded to /dev/null > > Are we sure we want that? How often does it happen? > Shouldn't there be follow by a risopsy when a notification > fails to be delivered? (for permanent failures, either > try to get in touch with representatives of the AS to > correct the address, or deconfigure the alarm???) What about setting the Return-Path: and Reply-To: headers to different values? When mail bounces it goes to the address specified in Return-Path, but when a human replies, the mail goes to the address specified in Reply-To (or From if Reply-To is not present). So it could be: Return-Path: [...] From: myASn Reply-To: risops at ripe.net or something like that. If you want automatic bounce unsubscription, you could set the Return-Path to something like Return-Path: where "colitti=dia.uniroma3.it" is the address that the notification was sent to. Then you can hook up a script to all myasn-bounce-*@ripe.net mailboxes that automatically unsubscribes after one or more bounces. Cheers, Lorenzo -- --------------------------------------------------------- Lorenzo Colitti Ph.D student Computer Networks research group Roma Tre University colitti at dia.uniroma3.it +39-0655173215 --------------------------------------------------------- From shane at ripe.net Wed Jul 14 17:27:28 2004 From: shane at ripe.net (Shane Kerr) Date: Wed, 14 Jul 2004 17:27:28 +0200 Subject: [ris-int] Reply-To forwarded to /dev/null in myASn messages In-Reply-To: <40F54751.1080902@dia.uniroma3.it> References: <200407141232.i6ECWI4c026188@birch.ripe.net> <40F54751.1080902@dia.uniroma3.it> Message-ID: <40F550E0.8090104@ripe.net> [ Don't know if it got announced, but Arife added me to the ris-int list today. Yay! ] Lorenzo Colitti wrote: > Rene Wilhelm wrote: > >>> ... myASn can use reply-to address forwarded to /dev/null >> >> >> Are we sure we want that? How often does it happen? >> Shouldn't there be follow by a risopsy when a notification >> fails to be delivered? (for permanent failures, either >> try to get in touch with representatives of the AS to >> correct the address, or deconfigure the alarm???) > > > What about setting the Return-Path: and Reply-To: headers to different > values? When mail bounces it goes to the address specified in > Return-Path, but when a human replies, the mail goes to the address > specified in Reply-To (or From if Reply-To is not present). > > So it could be: > > Return-Path: > [...] > From: myASn > Reply-To: risops at ripe.net > > or something like that. > > If you want automatic bounce unsubscription, you could set the > Return-Path to something like > > Return-Path: > > where "colitti=dia.uniroma3.it" is the address that the notification was > sent to. Then you can hook up a script to all myasn-bounce-*@ripe.net > mailboxes that automatically unsubscribes after one or more bounces. Interesting idea, although we need to take a bit of care security-wise. If we do an automatic unsubscribe, we'd need to: - Make the bound address non-predictable (hash with a secret would work): $ echo 'dia.uniroma3.it at ripe.net LotsOfRoutes' | md5sum 61081c9ee3097365710e7a0881f79e70 Return-Path That way I couldn't unsubscribe you by sending to your bounce address, since I won't be able to guess what your bounce auto-unsubscribe is. It can still be found by anyone who can read your mail, but there's not much we can do about that. - Track this information so that the user can be notified when they log in that their alarms are no disabled, and for what reason, and what they can do about it. Also, what about temporary delays? Do those go to the "Return-Path:"? I'd hate for someone to get unsubscribed because they exceeded their disk quota and had a bounce that made it through 30 minutes later. -- Shane Kerr RIPE NCC From colitti at dia.uniroma3.it Wed Jul 14 17:52:51 2004 From: colitti at dia.uniroma3.it (Lorenzo Colitti) Date: Wed, 14 Jul 2004 17:52:51 +0200 Subject: [ris-int] Reply-To forwarded to /dev/null in myASn messages In-Reply-To: <40F550E0.8090104@ripe.net> References: <200407141232.i6ECWI4c026188@birch.ripe.net> <40F54751.1080902@dia.uniroma3.it> <40F550E0.8090104@ripe.net> Message-ID: <40F556D3.30106@dia.uniroma3.it> Shane Kerr wrote: > Interesting idea, although we need to take a bit of care security-wise. > If we do an automatic unsubscribe, we'd need to: > > - Make the bound address non-predictable (hash with a secret would work): > > $ echo 'dia.uniroma3.it at ripe.net LotsOfRoutes' | md5sum > 61081c9ee3097365710e7a0881f79e70 > > Return-Path > > > That way I couldn't unsubscribe you by sending to your bounce address, Hmm... yes, I hadn't thought of that. Well, I was 50% there, wasn't I? :) > Also, what about temporary delays? Do those go to the "Return-Path:"? > I'd hate for someone to get unsubscribed because they exceeded their > disk quota and had a bounce that made it through 30 minutes later. I think so. But the only way to get around this is to keep state for every subscriber, right? Cheers, Lorenzo -- --------------------------------------------------------- Lorenzo Colitti Ph.D student Computer Networks research group Roma Tre University colitti at dia.uniroma3.it +39-0655173215 --------------------------------------------------------- From matthew at ripe.net Wed Jul 14 18:56:08 2004 From: matthew at ripe.net (Matthew Williams) Date: Wed, 14 Jul 2004 18:56:08 +0200 Subject: [ris-int] FW: ANNOUNCEMENT: New RIS Remote Route Collector at DE-CIX (RRC12) Message-ID: <000301c469c3$75c39e30$1f0200c1@rockstar> Hi Webbies, Would it be possible to link http://www.ripe.net/ris/rrc12.html from http://www.ripe.net/ ? Text something like: "RIPE NCC Remote Route Collector deployed at the German Internet Exchange (DE-CIX)" Many thanks! Cheers, Matthew > -----Original Message----- > From: Matthew Williams [mailto:matthew at ripe.net] > Sent: 07 July 2004 19:11 > To: 'ris-users at ripe.net' > Subject: ANNOUNCEMENT: New RIS Remote Route Collector at > DE-CIX (RRC12) > > > > > *** PGP Signature Status: good > *** Signer: Matthew Williams-Bywater > *** Signed: 07/07/2004 19:11:05 > *** Verified: 14/07/2004 18:50:15 > *** BEGIN PGP VERIFIED MESSAGE *** > > [Apologies for duplicate mails] > > Dear All, > > The RIPE NCC is pleased to announce that the RIS Project's > twelth* Remote Route Collector, RRC12, is now ready to peer > with members at the German Internet Exchange (DE-CIX). > > RRC12 is located at the German Internet Exchange (DE-CIX), > and has been operational since July 2004. The RRC has an > interface on the shared DE-CIX fabric, running both IPv4 and > IPv6, and collects routing information from all exchange > members, who are willing to peer with us. > > The use of TCP MD5 Signatures on IPv4 BGP sessions is > supported on all RIS Route Collectors. MD5, however, is not > supported on IPv6 sessions. > > Details: > -------- > - Peering address: 80.81.192.152 (IPv4); 2001:7f8::316e:0:1 (IPv6) > - Autonomous system: 12654 > - Policy: http://www.ripe.net/ris/rrc12.html > - Peering requests: > * Email: rispeering at ripe.net > * Web form at URL: http://www.ris.ripe.net/cgi-bin/peerreg.cgi > > The Routing Information Service (RIS), which started as a > modest RIPE NCC project in 1999, has gradually grown to over > 300 IPv4 and IPv6 peers at now twelve* data collection points > in Europe, Japan and North America. Our mission is to collect > BGP routing information over a function of time, and make it > available to the Internet community. In essence, this means > devising tools that can help ISPs debug problems over time > without being limited to one BGP view and providing RIS raw > data regarding the Internet's historical development. > > Useful Links: > ------------- > RIS Info: http://www.ripe.net/ris/ > RIS Tools: http://www.ripe.net/ris/query.html > List of RRC Locations: http://www.ris.ripe.net/cgi-bin/rrcstatus.cgi > > Please send your comments to ris-int at ripe.net. > > Best regards, > The RIS Team > > *) RRC09 has been decommissioned > > --- > > Matthew Williams (MW243-RIPE) > > Customer Liaison Engineer > > RIPE NCC - http://www.ripe.net/np/ > > > *** END PGP VERIFIED MESSAGE *** > From james at ripe.net Thu Jul 15 10:16:06 2004 From: james at ripe.net (James Aldridge) Date: Thu, 15 Jul 2004 10:16:06 +0200 Subject: [ris-int] Re: [staff] DHL: received goods In-Reply-To: Message from Saskia van Gorp of "Wed, 14 Jul 2004 15:15:10 +0200." <5.2.1.1.2.20040714151303.01b3ae78@mailhost.ripe.net> Message-ID: <200407150816.i6F8G64c020310@birch.ripe.net> Saskia van Gorp wrote: > Hi all, > > Did anybody around end of June - beginning of July receive a package from > Vienna (Austria) > Airway bill: 582 5977511 > Ref: inivie/vix > Sent out from Vienna on June 26. I guess that this was the old RIS Route Collector (rrc05) being returned. James From alexis at ripe.net Thu Jul 15 16:58:12 2004 From: alexis at ripe.net (Alexis Yushin) Date: Thu, 15 Jul 2004 16:58:12 +0200 (CEST) Subject: [ris-int] myasn xml Message-ID: <200407151458.i6FEwC0e031749@birch.ripe.net> Hi, I've just added http://www.ris.ripe.net/myasn/xml.html, a page to import myASn configuration as XML... Its not linked into index yet, since it has not been properly tested. Syntax is something like: 193.0.0.0/16 193.0.1.0/24 193.0.2.0/24 12324 2344 193.0.0.0/16 193.0.1.0/24 193.0.2.0/24 12324 2344 12324 2344 You get the idea... Alexis From arife at ripe.net Mon Jul 19 11:43:09 2004 From: arife at ripe.net (Arife Vural) Date: Mon, 19 Jul 2004 11:43:09 +0200 Subject: [ris-int] Today's RIS meeting minutes Message-ID: <20040719094308.GC15009@ripe.net> Main points: - RIS budget issue is discussed. New RRC hardware and replacement would be in OPS budget. Arife compiled the needs for RIS server and sent it to Shane. Shane will discuss this with Henk/Andrei. Shane suggest to make an analysis how many RIS servers we like to install and then do the installation at one go, rather than each year putting 2 new RRCs in budget. Matthew mentioned installation of 2 new RRCs (Dubai, Moscow) are in discussion. - This week Arife and Alessandro from SED will sit down with Alexis to talk about myASN transition. - After RIS transition it seems a lot of thing is settle down, because of that there is not much need to do RIS meeting every week. From now on, there will be RIS meeting once in two week. Arife will update the Ctime accordingly. Any correction/addition/comments are welcome. Arife From arife at ripe.net Mon Jul 19 11:47:13 2004 From: arife at ripe.net (Arife Vural) Date: Mon, 19 Jul 2004 11:47:13 +0200 Subject: [ris-int] myASN transition on Wed, 14.00 Message-ID: <20040719094713.GD15009@ripe.net> Hi guys, What about working myASN transition on Wed, 14.00? Arife From matthew at ripe.net Mon Jul 19 11:51:20 2004 From: matthew at ripe.net (Matthew Williams) Date: Mon, 19 Jul 2004 11:51:20 +0200 Subject: [ris-int] RE: myASN transition on Wed, 14.00 In-Reply-To: <20040719094713.GD15009@ripe.net> Message-ID: <002301c46d75$f157f090$1f0200c1@rockstar> I'd like to meet Alexis before the SED meeting... Alexis, what suites you? Cheers, Matthew > -----Original Message----- > From: Arife Vural [mailto:arife at ripe.net] > Sent: 19 July 2004 11:47 > To: Matthew Williams; alex at ripe.net; Alexis Yushin > Cc: ris-int at ripe.net > Subject: myASN transition on Wed, 14.00 > > > > Hi guys, > > What about working myASN transition on Wed, 14.00? > > Arife > From emma at ripe.net Mon Jul 19 12:41:01 2004 From: emma at ripe.net (Emma Bretherick) Date: Mon, 19 Jul 2004 12:41:01 +0200 Subject: [ris-int] Re: We need your fb again ;) In-Reply-To: <000c01c46352$6f589180$1f0200c1@rockstar> Message-ID: <5.1.0.14.2.20040719122445.00ac6058@mailhost.ripe.net> Hey, We still prefer our last suggestions: Error Time Limit Error Event Count We think they make a little more sense - at least to us! However in case you hate them, out of your suggestions we prefer: 'Min-Event-Duration' and 'Min-Event-Count' Ta muchly (and sorry for the delay in replying!) Cheers, Emma At 14:11 06/07/2004 +0200, Matthew Williams wrote: >Hi Comms, > >Please see explanations here: http://www.ripe.net/ris/myasngls.html#50 > >And then think about alternative terms for below: > >*Hold Down Time >*Hold Down Event: > >'Min-Event-Duration' and 'Min-Event-Count' are our current candidates. > >*Time To Live: > >We have two lines of thought here. One relates to 'detection' of events >building up to an alarm entry in the email sent to the user, >while the other follows the line of 'suppression' of further entries once >the first entry has been triggered (based on exactly the >same events). If we go along with the second concept, then this is a >maximum time interval. In the first case, we're talking about a >fixed 'window' (time interval). I hope all that made sense ;) > >Here come some suggestions: "Event-count Window", "Alarm-Suppress-Time", >"Max-suppress-time", "Event-Suppress-Time', >"max-detect-window", "alarm-detect-window"... Etc etc... We could go on >forever and ever. The question is: What works for you? > >The beta is more or less ready so we need to get this one out of the way >once and for all... ;) > >Cheers, >Matthew > > --- > > Matthew Williams (MW243-RIPE) > > Customer Liaison Engineer > > RIPE NCC - http://www.ripe.net/np/ ------------------------------------ Emma Bretherick RIPE NCC http://www.ripe.net/ From daniel.karrenberg at ripe.net Mon Jul 19 12:46:48 2004 From: daniel.karrenberg at ripe.net (Daniel Karrenberg) Date: Mon, 19 Jul 2004 12:46:48 +0200 Subject: [ris-int] Re: We need your fb again ;) In-Reply-To: <5.1.0.14.2.20040719122445.00ac6058@mailhost.ripe.net> References: <000c01c46352$6f589180$1f0200c1@rockstar> <5.1.0.14.2.20040719122445.00ac6058@mailhost.ripe.net> Message-ID: <20040719104648.GC3082@reifa-wave.karrenberg.net> On 19.07 12:41, Emma Bretherick wrote: > > Hey, > > We still prefer our last suggestions: > > Error Time Limit > Error Event Count > > We think they make a little more sense - at least to us! > > However in case you hate them, out of your suggestions we prefer: > > 'Min-Event-Duration' and 'Min-Event-Count' > > Ta muchly (and sorry for the delay in replying!) > > Cheers, > Emma I still think the "Minimum-" terms are most descriptive but both work for me. Daniel From matthew at ripe.net Mon Jul 19 13:03:09 2004 From: matthew at ripe.net (Matthew Williams) Date: Mon, 19 Jul 2004 13:03:09 +0200 Subject: [ris-int] Re: We need your fb again ;) In-Reply-To: <5.1.0.14.2.20040719122445.00ac6058@mailhost.ripe.net> Message-ID: <002601c46d7f$f9dfbb80$1f0200c1@rockstar> > Hey, > > We still prefer our last suggestions: > > Error Time Limit > Error Event Count > > We think they make a little more sense - at least to us! > :) > However in case you hate them, out of your suggestions we prefer: > > 'Min-Event-Duration' and 'Min-Event-Count' We're leaning towards above. The only thing I don't like is the short for 'Min-Event-Duration' becoming 'MED', which is also a bgp attribute. I rather like 'Alarm-Suppress-Limit' instead of 'Alarm-Suppress-Time'. Anyway, at some point, I guess that we'll just have to be content with getting rid of the previous terms ;) > > Ta muchly (and sorry for the delay in replying!) No worries :) Cheers, Matthew > > Cheers, > Emma > > At 14:11 06/07/2004 +0200, Matthew Williams wrote: > >Hi Comms, > > > >Please see explanations here: > http://www.ripe.net/ris/myasngls.html#50 > > > >And then think > about alternative terms for below: > > > >*Hold Down Time > >*Hold Down Event: > > > >'Min-Event-Duration' and 'Min-Event-Count' are our current > candidates. > > > >*Time To Live: > > > >We have two lines of thought here. One relates to > 'detection' of events > >building up to an alarm entry in the email sent to the user, > >while the other follows the line of 'suppression' of further > entries once > >the first entry has been triggered (based on exactly the > >same events). If we go along with the second concept, then this is a > >maximum time interval. In the first case, we're talking about a > >fixed 'window' (time interval). I hope all that made sense ;) > > > >Here come some suggestions: "Event-count Window", > >"Alarm-Suppress-Time", > >"Max-suppress-time", "Event-Suppress-Time', > >"max-detect-window", "alarm-detect-window"... Etc etc... We > could go on > >forever and ever. The question is: What works for you? > > > >The beta is more or less ready so we need to get this one out of the > >way > >once and for all... ;) > > > >Cheers, > >Matthew > > > > --- > > > Matthew Williams (MW243-RIPE) > > > Customer Liaison Engineer > > > RIPE NCC - http://www.ripe.net/np/ > > > ------------------------------------ > Emma Bretherick > RIPE NCC > http://www.ripe.net/ > From matthew at ripe.net Tue Jul 20 15:04:53 2004 From: matthew at ripe.net (Matthew Williams) Date: Tue, 20 Jul 2004 15:04:53 +0200 Subject: [ris-int] MSK-IX RRC Message-ID: <02ca01c46e5a$2639ca10$1f0200c1@rockstar> Just thinking out loud: In order to circumvent excessive $$$ at Russian customs, wouldn't it be smarter to have the IXP order a Dell PowerEdge to OPS requirements and ship your nifty little CD instead? Would that work or should we just go down the normal route. I will naturally have to ask the IXP as well. Cheers, Matthew From bruce.campbell at ripe.net Tue Jul 20 15:17:35 2004 From: bruce.campbell at ripe.net (Bruce Campbell) Date: Tue, 20 Jul 2004 15:17:35 +0200 (CEST) Subject: [ris-int] Re: MSK-IX RRC In-Reply-To: <02ca01c46e5a$2639ca10$1f0200c1@rockstar> References: <02ca01c46e5a$2639ca10$1f0200c1@rockstar> Message-ID: On Tue, 20 Jul 2004, Matthew Williams wrote: > Just thinking out loud: > > In order to circumvent excessive $$$ at Russian customs, wouldn't it be > smarter to have the IXP order a Dell PowerEdge to OPS requirements and > ship your nifty little CD instead? Would that work or should we just go > down the normal route. I will naturally have to ask the IXP as well. It would be far easier, as long as we know the IP configuration in advance. --==-- Bruce. From matthew at ripe.net Tue Jul 20 15:57:16 2004 From: matthew at ripe.net (Matthew Williams) Date: Tue, 20 Jul 2004 15:57:16 +0200 Subject: [ris-int] Re: MSK-IX RRC In-Reply-To: Message-ID: <02d601c46e61$77ea8dc0$1f0200c1@rockstar> Thanks for the swift reply :) Seems like I correctly anticipated her following question... She will get back to us about ordering a Dell in RU. Cheers, Matthew > -----Original Message----- > From: ris-int-admin at ripe.net [mailto:ris-int-admin at ripe.net] > On Behalf Of Bruce Campbell > Sent: 20 July 2004 15:18 > To: Matthew Williams > Cc: ris-int at ripe.net > Subject: [ris-int] Re: MSK-IX RRC > > > On Tue, 20 Jul 2004, Matthew Williams wrote: > > > Just thinking out loud: > > > > In order to circumvent excessive $$$ at Russian customs, > wouldn't it > > be smarter to have the IXP order a Dell PowerEdge to OPS > requirements > > and ship your nifty little CD instead? Would that work or should we > > just go down the normal route. I will naturally have to ask > the IXP as > > well. > > It would be far easier, as long as we know the IP > configuration in advance. > > --==-- > Bruce. > From alexis at ripe.net Tue Jul 20 19:48:35 2004 From: alexis at ripe.net (Alexis Yushin) Date: Tue, 20 Jul 2004 19:48:35 +0200 (CEST) Subject: [ris-int] Re: myASN transition on Wed, 14.00 In-Reply-To: <002301c46d75$f157f090$1f0200c1@rockstar> from "Matthew Williams" at Jul 19, 2004 11:51:20 AM Message-ID: <200407201748.i6KHmZO6021939@birch.ripe.net> Hi, I'm afraid I cannot make it to the meeting tomorrow, something came in between... What about Thursday? Alexis Once Matthew Williams wrote: >I'd like to meet Alexis before the SED meeting... > >Alexis, what suites you? > >Cheers, >Matthew > >> -----Original Message----- >> From: Arife Vural [mailto:arife at ripe.net] >> Sent: 19 July 2004 11:47 >> To: Matthew Williams; alex at ripe.net; Alexis Yushin >> Cc: ris-int at ripe.net >> Subject: myASN transition on Wed, 14.00 >> >> >> >> Hi guys, >> >> What about working myASN transition on Wed, 14.00? >> >> Arife >> > From matthew at ripe.net Tue Jul 20 20:07:55 2004 From: matthew at ripe.net (Matthew Williams) Date: Tue, 20 Jul 2004 20:07:55 +0200 Subject: [ris-int] RE: myASN transition on Wed, 14.00 In-Reply-To: <200407201748.i6KHmZO6021939@birch.ripe.net> Message-ID: <02d901c46e84$7b74b100$1f0200c1@rockstar> When does your contract _formally_ end? Cheers, Matthew > -----Original Message----- > From: Alexis Yushin [mailto:alexis at ripe.net] > Sent: 20 July 2004 19:49 > To: Matthew Williams > Cc: 'Arife Vural'; 'Alexis Yushin'; ris-int at ripe.net; alex at ripe.net > Subject: Re: myASN transition on Wed, 14.00 > > > Hi, > > I'm afraid I cannot make it to the meeting tomorrow, > something came in between... What about Thursday? > > Alexis > > Once Matthew Williams wrote: > >I'd like to meet Alexis before the SED meeting... > > > >Alexis, what suites you? > > > >Cheers, > >Matthew > > > >> -----Original Message----- > >> From: Arife Vural [mailto:arife at ripe.net] > >> Sent: 19 July 2004 11:47 > >> To: Matthew Williams; alex at ripe.net; Alexis Yushin > >> Cc: ris-int at ripe.net > >> Subject: myASN transition on Wed, 14.00 > >> > >> > >> > >> Hi guys, > >> > >> What about working myASN transition on Wed, 14.00? > >> > >> Arife > >> > > > From arife at ripe.net Wed Jul 21 10:52:02 2004 From: arife at ripe.net (Arife Vural) Date: Wed, 21 Jul 2004 10:52:02 +0200 Subject: [ris-int] Re: myASN transition on Wed, 14.00 In-Reply-To: <200407201748.i6KHmZO6021939@birch.ripe.net> References: <002301c46d75$f157f090$1f0200c1@rockstar> <200407201748.i6KHmZO6021939@birch.ripe.net> Message-ID: <20040721085202.GC32351@ripe.net> Hi Alexis, What about Friday morning? Alessandro from SED is not available on Thu. Arife On Tue, Jul 20, 2004 at 07:48:35PM +0200, Alexis Yushin wrote: > Hi, > > I'm afraid I cannot make it to the meeting tomorrow, something came in between... What about > Thursday? > > Alexis > > Once Matthew Williams wrote: > >I'd like to meet Alexis before the SED meeting... > > > >Alexis, what suites you? > > > >Cheers, > >Matthew > > > >> -----Original Message----- > >> From: Arife Vural [mailto:arife at ripe.net] > >> Sent: 19 July 2004 11:47 > >> To: Matthew Williams; alex at ripe.net; Alexis Yushin > >> Cc: ris-int at ripe.net > >> Subject: myASN transition on Wed, 14.00 > >> > >> > >> > >> Hi guys, > >> > >> What about working myASN transition on Wed, 14.00? > >> > >> Arife > >> > > From henk at ripe.net Wed Jul 21 14:39:50 2004 From: henk at ripe.net (Henk Uijterwaal (RIPE NCC)) Date: Wed, 21 Jul 2004 14:39:50 +0200 (CEST) Subject: [ris-int] Re: MSK-IX RRC In-Reply-To: References: <02ca01c46e5a$2639ca10$1f0200c1@rockstar> Message-ID: On Tue, 20 Jul 2004, Bruce Campbell wrote: > On Tue, 20 Jul 2004, Matthew Williams wrote: > > > Just thinking out loud: > > > > In order to circumvent excessive $$$ at Russian customs, wouldn't it be > > smarter to have the IXP order a Dell PowerEdge to OPS requirements and > > ship your nifty little CD instead? Would that work or should we just go > > down the normal route. I will naturally have to ask the IXP as well. > > It would be far easier, as long as we know the IP configuration in > advance. If they buy it, we'll have to reimburse them. Please check with Jochem about transferring the euro's. The ideal would be that they order it and we get the invoice from Dell. Perhaps ask Sonia to call her contact at Dell and figure out what would be the easiest approach. 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 ------------------------------------------------------------------------------ Process and Procedure are the last hiding place of people without the wit and wisdom to do their job properly. (David Brent). From henk at ripe.net Wed Jul 21 14:56:46 2004 From: henk at ripe.net (Henk Uijterwaal (RIPE NCC)) Date: Wed, 21 Jul 2004 14:56:46 +0200 (CEST) Subject: [ris-int] Today's RIS meeting minutes In-Reply-To: <20040719094308.GC15009@ripe.net> References: <20040719094308.GC15009@ripe.net> Message-ID: On Mon, 19 Jul 2004, Arife Vural wrote: > > Main points: > > - RIS budget issue is discussed. New RRC hardware and replacement > would be in OPS budget. Arife compiled the needs for RIS server > and sent it to Shane. Shane will discuss this with Henk/Andrei. > > Shane suggest to make an analysis how many RIS servers we like to > install and then do the installation at one go, rather than each > year putting 2 new RRCs in budget. > > Matthew mentioned installation of 2 new RRCs (Dubai, Moscow) are > in discussion. The 2 RRC's in the budget _are_ intended for Dubai and Moscow, to cover major gaps in the coverage of the RIPE region. After that, I do not see an immediate need for any more RRC's. We always said that something in the ballpark of 10-20 RRC's should give a fairly complete picture of the Internet. With Dubai and Moscow, we have 15 all over the world. > - This week Arife and Alessandro from SED will sit down with Alexis > to talk about myASN transition. > > - After RIS transition it seems a lot of thing is settle down, because > of that there is not much need to do RIS meeting every week. From now > on, there will be RIS meeting once in two week. Arife will update the > Ctime accordingly. I'll remove the meeting from CTime next, Arife, can you reschedule the meeting as bi-weekly starting from 25/7? (Shane and I think we should go over the transistion to-do-list next monday to make sure that everything is done or scheduled). Henk > > Any correction/addition/comments are welcome. > > Arife > ------------------------------------------------------------------------------ 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 ------------------------------------------------------------------------------ Process and Procedure are the last hiding place of people without the wit and wisdom to do their job properly. (David Brent). From arife at ripe.net Wed Jul 21 15:17:25 2004 From: arife at ripe.net (Arife Vural) Date: Wed, 21 Jul 2004 15:17:25 +0200 Subject: [ris-int] Today's RIS meeting minutes In-Reply-To: References: <20040719094308.GC15009@ripe.net> Message-ID: <20040721131725.GR32351@ripe.net> > I'll remove the meeting from CTime next, Arife, can you reschedule the > meeting as bi-weekly starting from 25/7? (Shane and I think we should go > over the transistion to-do-list next monday to make sure that everything > is done or scheduled). I reschedule the RIS meeting bi-weekly, it starts from next Monday. That means we have RIS meeting next Monday, after that we will have once in two weeks. I added the following people's agenda. If I missed anybody, please let me know. Shane, Arife, Vasco Henk, Matthew Ruud, Gerard, Bruce, James BTW, when we do those things, if anybody does not have any objection to move ris at ripe.net to Xrtt, I will ask OPS to the necessary changes. Arife From henk at ripe.net Wed Jul 21 15:26:38 2004 From: henk at ripe.net (Henk Uijterwaal (RIPE NCC)) Date: Wed, 21 Jul 2004 15:26:38 +0200 (CEST) Subject: [ris-int] Re: We need your fb again ;) In-Reply-To: <5.1.0.14.2.20040719122445.00ac6058@mailhost.ripe.net> References: <5.1.0.14.2.20040719122445.00ac6058@mailhost.ripe.net> Message-ID: Hi, Catching up on email. > > Hey, > > We still prefer our last suggestions: > > Error Time Limit > Error Event Count > > We think they make a little more sense - at least to us! > > However in case you hate them, out of your suggestions we prefer: > > 'Min-Event-Duration' and 'Min-Event-Count' I don't like Min-Event-Duration as it will be shortened to MED and that is already a known mnemonic in the BGP world. Also MED and MEC look very similar. That said, I think we shouldn't spend too much time on the names but rather on the explanation. If ETL and EEC, or MED and MEC for that matter, are explained properly then people should be able to understand what we mean by them in the context of this service. And that is the most important thing. Looking at the description, it might benefit from a drawing to illustrate the alarms: A 1 W 1 | | Time -----------------------------------------------> t=1 t=2 t=1+ETL A 1 W 1 | | Time -----------------------------------------------> t=1 t=1+ETL 5 minutes of xfig makes it clear for me. (And probably as clear as mud to the rest of the universe :-) Henk > > Ta muchly (and sorry for the delay in replying!) > > Cheers, > Emma > > At 14:11 06/07/2004 +0200, Matthew Williams wrote: > >Hi Comms, > > > >Please see explanations here: http://www.ripe.net/ris/myasngls.html#50 > > > >And then think about alternative terms for below: > > > >*Hold Down Time > >*Hold Down Event: > > > >'Min-Event-Duration' and 'Min-Event-Count' are our current candidates. > > > >*Time To Live: > > > >We have two lines of thought here. One relates to 'detection' of events > >building up to an alarm entry in the email sent to the user, > >while the other follows the line of 'suppression' of further entries once > >the first entry has been triggered (based on exactly the > >same events). If we go along with the second concept, then this is a > >maximum time interval. In the first case, we're talking about a > >fixed 'window' (time interval). I hope all that made sense ;) > > > >Here come some suggestions: "Event-count Window", "Alarm-Suppress-Time", > >"Max-suppress-time", "Event-Suppress-Time', > >"max-detect-window", "alarm-detect-window"... Etc etc... We could go on > >forever and ever. The question is: What works for you? > > > >The beta is more or less ready so we need to get this one out of the way > >once and for all... ;) > > > >Cheers, > >Matthew > > > > --- > > > Matthew Williams (MW243-RIPE) > > > Customer Liaison Engineer > > > RIPE NCC - http://www.ripe.net/np/ > > > ------------------------------------ > Emma Bretherick > RIPE NCC > http://www.ripe.net/ > ------------------------------------------------------------------------------ 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 ------------------------------------------------------------------------------ Process and Procedure are the last hiding place of people without the wit and wisdom to do their job properly. (David Brent). From henk at ripe.net Wed Jul 21 16:39:46 2004 From: henk at ripe.net (Henk Uijterwaal (RIPE NCC)) Date: Wed, 21 Jul 2004 16:39:46 +0200 (CEST) Subject: [ris-int] RE: myASN transition on Wed, 14.00 In-Reply-To: <02d901c46e84$7b74b100$1f0200c1@rockstar> References: <02d901c46e84$7b74b100$1f0200c1@rockstar> Message-ID: On Tue, 20 Jul 2004, Matthew Williams wrote: > When does your contract _formally_ end? When I sign off on the hand-over. Henk > > Cheers, > Matthew > > > -----Original Message----- > > From: Alexis Yushin [mailto:alexis at ripe.net] > > Sent: 20 July 2004 19:49 > > To: Matthew Williams > > Cc: 'Arife Vural'; 'Alexis Yushin'; ris-int at ripe.net; alex at ripe.net > > Subject: Re: myASN transition on Wed, 14.00 > > > > > > Hi, > > > > I'm afraid I cannot make it to the meeting tomorrow, > > something came in between... What about Thursday? > > > > Alexis > > > > Once Matthew Williams wrote: > > >I'd like to meet Alexis before the SED meeting... > > > > > >Alexis, what suites you? > > > > > >Cheers, > > >Matthew > > > > > >> -----Original Message----- > > >> From: Arife Vural [mailto:arife at ripe.net] > > >> Sent: 19 July 2004 11:47 > > >> To: Matthew Williams; alex at ripe.net; Alexis Yushin > > >> Cc: ris-int at ripe.net > > >> Subject: myASN transition on Wed, 14.00 > > >> > > >> > > >> > > >> Hi guys, > > >> > > >> What about working myASN transition on Wed, 14.00? > > >> > > >> Arife > > >> > > > > > > ------------------------------------------------------------------------------ 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 ------------------------------------------------------------------------------ Process and Procedure are the last hiding place of people without the wit and wisdom to do their job properly. (David Brent). From matthew at ripe.net Wed Jul 21 16:55:04 2004 From: matthew at ripe.net (Matthew Williams) Date: Wed, 21 Jul 2004 16:55:04 +0200 Subject: [ris-int] RE: myASN transition on Wed, 14.00 In-Reply-To: Message-ID: <045501c46f32$b4a49770$1f0200c1@rockstar> Ah, good. Needed to know that :) Cheers, Matthew > -----Original Message----- > From: Henk Uijterwaal (RIPE NCC) [mailto:henk at ripe.net] > Sent: 21 July 2004 16:40 > To: Matthew Williams > Cc: 'Alexis Yushin'; 'Arife Vural'; ris-int at ripe.net; alex at ripe.net > Subject: Re: [ris-int] RE: myASN transition on Wed, 14.00 > > > On Tue, 20 Jul 2004, Matthew Williams wrote: > > > When does your contract _formally_ end? > > When I sign off on the hand-over. > > Henk > > > > > > Cheers, > > Matthew > > > > > -----Original Message----- > > > From: Alexis Yushin [mailto:alexis at ripe.net] > > > Sent: 20 July 2004 19:49 > > > To: Matthew Williams > > > Cc: 'Arife Vural'; 'Alexis Yushin'; ris-int at ripe.net; > alex at ripe.net > > > Subject: Re: myASN transition on Wed, 14.00 > > > > > > > > > Hi, > > > > > > I'm afraid I cannot make it to the meeting tomorrow, > something came > > > in between... What about Thursday? > > > > > > Alexis > > > > > > Once Matthew Williams wrote: > > > >I'd like to meet Alexis before the SED meeting... > > > > > > > >Alexis, what suites you? > > > > > > > >Cheers, > > > >Matthew > > > > > > > >> -----Original Message----- > > > >> From: Arife Vural [mailto:arife at ripe.net] > > > >> Sent: 19 July 2004 11:47 > > > >> To: Matthew Williams; alex at ripe.net; Alexis Yushin > > > >> Cc: ris-int at ripe.net > > > >> Subject: myASN transition on Wed, 14.00 > > > >> > > > >> > > > >> > > > >> Hi guys, > > > >> > > > >> What about working myASN transition on Wed, 14.00? > > > >> > > > >> Arife > > > >> > > > > > > > > > > > -------------------------------------------------------------- > ---------------- > 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 > -------------------------------------------------------------- > ---------------- > > Process and Procedure are the last hiding place of people > without the wit > and wisdom to do their job properly. > (David Brent). > From arife at ripe.net Thu Jul 22 12:01:39 2004 From: arife at ripe.net (Arife Vural) Date: Thu, 22 Jul 2004 12:01:39 +0200 Subject: [ris-int] myASN SQL queries Message-ID: <20040722100138.GG21656@ripe.net> Hi Alexis, Today, when I looked at mySQL logs, I saw the one of myASN query and it returns almost all the entries in table. I do not know that was the intention or not. But, when we meet up for handover, I would like to go over those SQLs with you whether we can do any optimization or not. BTW, I hope tomorrow morning is OK for you. I have not got a reply from you yet. Arife From matthew at ripe.net Thu Jul 22 14:01:44 2004 From: matthew at ripe.net (Matthew Williams) Date: Thu, 22 Jul 2004 14:01:44 +0200 Subject: [ris-int] Other RIS things ... Message-ID: <035601c46fe3$a8134130$1f0200c1@rockstar> Hi Arife, Mae-West doesn't seem to be picking up in peers (4 - and according to Hong-Wei, no full feeds). It was some time ago since you tried to get their attention (nanog in miami?). After the good experiences at the NYIIX, shall we try LAIX? What do you think? BC thought that we should wait until the end of the year, but that requires giving gebert, bechly and pucik a little push (again). BTW, have you thought about cleaning up active bgp session or it that ops work? If they already have tools to monitor anycast and 3333 sessions then maybe the RIS could just plug into that. Cheers, Matthew +++ RRC00 ----- 195.66.224.112 4 3549 0 0 0 0 0 never Active | 195.69.144.85 4 3257 0 0 0 0 0 never Connect | RRC01 ----- 195.66.224.40 4 15861 0 0 0 0 0 never Active | 195.66.224.41 4 5604 0 0 0 0 0 never Active | 195.66.224.48 4 1299 0 0 0 0 0 never Active | 195.66.224.117 4 12513 0 0 0 0 0 never Active | 195.66.224.168 4 20940 0 10123 0 0 0 never Active | 195.66.226.10 4 2856 86 9 0 0 0 03w5d22h Connect | 195.66.226.11 4 2856 85 9 0 0 0 03w5d22h Connect | 195.66.226.40 4 15861 0 0 0 0 0 never Active | 195.66.226.47 4 8272 0 0 0 0 0 never Active | 195.66.226.103 4 2818 442 299 0 0 0 2d15h56m Active | 195.66.226.119 4 12390 0 0 0 0 0 never Connect | RRC02 ----- 194.68.129.164 4 13237 0 0 0 0 0 never Active | 194.68.129.173 4 6774 0 0 0 0 0 never Connect | 194.68.129.186 4 20766 356 355376 0 0 0 4d15h53m Idle | 194.68.129.225 4 5462 0 0 0 0 0 never Active | 194.68.129.252 4 2686 0 0 0 0 0 never Active | Etc.... From arife at ripe.net Thu Jul 22 15:04:37 2004 From: arife at ripe.net (Arife Vural) Date: Thu, 22 Jul 2004 15:04:37 +0200 Subject: [ris-int] Re: Other RIS things ... In-Reply-To: <035601c46fe3$a8134130$1f0200c1@rockstar> References: <035601c46fe3$a8134130$1f0200c1@rockstar> Message-ID: <20040722130437.GN21656@ripe.net> > Mae-West doesn't seem to be picking up in peers (4 - and according to Hong-Wei, no full feeds). It was some time ago since you tried > to get their attention (nanog in miami?). After the good experiences at the NYIIX, shall we try LAIX? What do you think? BC thought > that we should wait until the end of the year, but that requires giving gebert, bechly and pucik a little push (again). > I think we should decide where we like to re-locate rrc08. Pushing those guys do not help, after two of my try, we lost peer rather than getting more peers. One of the reason is most of their members are already left. At that point, they can not do much about to help us. About new location, be honest I do not know which would be best. I guess we are looking new place at West again, right? What are the options? and number of their members and do we have any contact person any of those locations? > BTW, have you thought about cleaning up active bgp session or it that ops work? If they already have tools to monitor anycast and It's SED. I have to talk with Vasco about arraning a time schedule for that one. Arife > 3333 sessions then maybe the RIS could just plug into that. > > Cheers, > Matthew > > +++ > > RRC00 > ----- > 195.66.224.112 4 3549 0 0 0 0 0 never Active | > 195.69.144.85 4 3257 0 0 0 0 0 never Connect | > > RRC01 > ----- > 195.66.224.40 4 15861 0 0 0 0 0 never Active | > 195.66.224.41 4 5604 0 0 0 0 0 never Active | > 195.66.224.48 4 1299 0 0 0 0 0 never Active | > 195.66.224.117 4 12513 0 0 0 0 0 never Active | > 195.66.224.168 4 20940 0 10123 0 0 0 never Active | > 195.66.226.10 4 2856 86 9 0 0 0 03w5d22h Connect | > 195.66.226.11 4 2856 85 9 0 0 0 03w5d22h Connect | > 195.66.226.40 4 15861 0 0 0 0 0 never Active | > 195.66.226.47 4 8272 0 0 0 0 0 never Active | > 195.66.226.103 4 2818 442 299 0 0 0 2d15h56m Active | > 195.66.226.119 4 12390 0 0 0 0 0 never Connect | > > RRC02 > ----- > 194.68.129.164 4 13237 0 0 0 0 0 never Active | > 194.68.129.173 4 6774 0 0 0 0 0 never Connect | > 194.68.129.186 4 20766 356 355376 0 0 0 4d15h53m Idle | > 194.68.129.225 4 5462 0 0 0 0 0 never Active | > 194.68.129.252 4 2686 0 0 0 0 0 never Active | > > Etc.... > > From matthew at ripe.net Thu Jul 22 17:41:38 2004 From: matthew at ripe.net (Matthew Williams) Date: Thu, 22 Jul 2004 17:41:38 +0200 Subject: [ris-int] Re: Other RIS things ... In-Reply-To: <20040722130437.GN21656@ripe.net> Message-ID: <037601c47002$605f7290$1f0200c1@rockstar> > -----Original Message----- > From: ris-int-admin at ripe.net [mailto:ris-int-admin at ripe.net] > On Behalf Of Arife Vural > Sent: 22 July 2004 15:05 > To: Matthew Williams > Cc: ris-int at ripe.net > Subject: [ris-int] Re: Other RIS things ... > > > > > Mae-West doesn't seem to be picking up in peers (4 - and > according to > > Hong-Wei, no full feeds). It was some time ago since you > tried to get > > their attention (nanog in miami?). After the good > experiences at the > > NYIIX, shall we try LAIX? What do you think? BC thought > that we should > > wait until the end of the year, but that requires giving gebert, > > bechly and pucik a little push (again). > > > > I think we should decide where we like to re-locate rrc08. > Pushing those guys do not help, after two of my try, we lost > peer rather than getting more peers. One of the reason is > most of their members are already left. At that point, they > can not do much about to help us. > > About new location, be honest I do not know which would be > best. I guess we are looking new place at West again, right? > What are the options? and number of their members and do we > have any contact person any of those locations? ISC (PAIX) offered assistance, route-views are already there though. Otherwise we have LAIIX (need to find transit though, f-root are there ;), not many members though, only a few IPv6. There is also Seattle (SIX,) and San Diego (SD-NAP, Caida). Seattle looks most promising... Any other ideas? Options: http://www.bgp4.as/internet-exchanges Cheers, Matthew > > > BTW, have you thought about cleaning up active bgp session > or it that > > ops work? If they already have tools to monitor anycast and > > It's SED. I have to talk with Vasco about arraning a time > schedule for that one. > > Arife > > > 3333 sessions then maybe the RIS could just plug into that. > > > > Cheers, > > Matthew > > > > +++ > > > > RRC00 > > ----- > > 195.66.224.112 4 3549 0 0 0 0 0 > never Active | > > 195.69.144.85 4 3257 0 0 0 0 0 > never Connect | > > > > RRC01 > > ----- > > 195.66.224.40 4 15861 0 0 0 0 0 > never Active | > > 195.66.224.41 4 5604 0 0 0 0 0 > never Active | > > 195.66.224.48 4 1299 0 0 0 0 0 > never Active | > > 195.66.224.117 4 12513 0 0 0 0 0 > never Active | > > 195.66.224.168 4 20940 0 10123 0 0 0 > never Active | > > 195.66.226.10 4 2856 86 9 0 0 0 > 03w5d22h Connect | > > 195.66.226.11 4 2856 85 9 0 0 0 > 03w5d22h Connect | > > 195.66.226.40 4 15861 0 0 0 0 0 > never Active | > > 195.66.226.47 4 8272 0 0 0 0 0 > never Active | > > 195.66.226.103 4 2818 442 299 0 0 0 > 2d15h56m Active | > > 195.66.226.119 4 12390 0 0 0 0 0 > never Connect | > > > > RRC02 > > ----- > > 194.68.129.164 4 13237 0 0 0 0 0 > never Active | > > 194.68.129.173 4 6774 0 0 0 0 0 > never Connect | > > 194.68.129.186 4 20766 356 355376 0 0 0 > 4d15h53m Idle | > > 194.68.129.225 4 5462 0 0 0 0 0 > never Active | > > 194.68.129.252 4 2686 0 0 0 0 0 > never Active | > > > > Etc.... > > > > > From james at ripe.net Thu Jul 22 17:57:42 2004 From: james at ripe.net (James Aldridge) Date: Thu, 22 Jul 2004 17:57:42 +0200 Subject: [ris-int] Re: Other RIS things ... In-Reply-To: <037601c47002$605f7290$1f0200c1@rockstar> References: <037601c47002$605f7290$1f0200c1@rockstar> Message-ID: <8C4589112A4639C9F76F9418@guest-wv-22.ripe.net> --On Thursday, 22 July, 2004 17:41 +0200 Matthew Williams wrote: > ISC (PAIX) offered assistance, route-views are already there though. > Otherwise we have LAIIX (need to find transit though, f-root are there > ;), not many members though, only a few IPv6. > > There is also Seattle (SIX,) and San Diego (SD-NAP, Caida). Seattle looks > most promising... Any other ideas? PAIX is probably now the largest exchange point on the U.S. West Coast: http://www.switchanddata.com/Solutions/PAIX/Customers/PaloAlto/ Our friends at Tiscali are there if we need transit ;-) James -- James Aldridge, Network Engineer, RIPE NCC Tel: +31 20 535 4421 Fax: +31 20 535 4445 GSM: +31 6 5247 6932 From matthew at ripe.net Thu Jul 22 18:17:42 2004 From: matthew at ripe.net (Matthew Williams) Date: Thu, 22 Jul 2004 18:17:42 +0200 Subject: [ris-int] Re: MSK-IX RRC In-Reply-To: Message-ID: <038201c47007$6a768250$1f0200c1@rockstar> > The ideal would be that they order it and we get the invoice > from Dell. Perhaps ask Sonia to call her contact at Dell and > figure out what would be the easiest approach. She did that, and they weren't too happy about above ("bad experiences with customs"). We will have to specify what we want and send specs to MSK-IX. Sonia was adamant about getting a quote on price (to be approved by us), before they go ahead with the order. 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: 21 July 2004 14:40 > To: Bruce Campbell > Cc: Matthew Williams; ris-int at ripe.net > Subject: Re: [ris-int] Re: MSK-IX RRC > > > On Tue, 20 Jul 2004, Bruce Campbell wrote: > > > On Tue, 20 Jul 2004, Matthew Williams wrote: > > > > > Just thinking out loud: > > > > > > In order to circumvent excessive $$$ at Russian customs, > wouldn't it > > > be smarter to have the IXP order a Dell PowerEdge to OPS > > > requirements and ship your nifty little CD instead? Would > that work > > > or should we just go down the normal route. I will > naturally have to > > > ask the IXP as well. > > > > It would be far easier, as long as we know the IP configuration in > > advance. > > If they buy it, we'll have to reimburse them. Please check > with Jochem about transferring the euro's. > > The ideal would be that they order it and we get the invoice > from Dell. Perhaps ask Sonia to call her contact at Dell and > figure out what would be the easiest approach. > > > 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 > -------------------------------------------------------------- > ---------------- > > Process and Procedure are the last hiding place of people > without the wit > and wisdom to do their job properly. > (David Brent). > From henk at ripe.net Fri Jul 23 11:13:21 2004 From: henk at ripe.net (Henk Uijterwaal (RIPE NCC)) Date: Fri, 23 Jul 2004 11:13:21 +0200 (CEST) Subject: [ris-int] Re: Other RIS things ... In-Reply-To: <8C4589112A4639C9F76F9418@guest-wv-22.ripe.net> References: <037601c47002$605f7290$1f0200c1@rockstar> <8C4589112A4639C9F76F9418@guest-wv-22.ripe.net> Message-ID: On Thu, 22 Jul 2004, James Aldridge wrote: > --On Thursday, 22 July, 2004 17:41 +0200 Matthew Williams > wrote: > > ISC (PAIX) offered assistance, route-views are already there though. > > Otherwise we have LAIIX (need to find transit though, f-root are there > > ;), not many members though, only a few IPv6. > > > > There is also Seattle (SIX,) and San Diego (SD-NAP, Caida). Seattle looks > > most promising... Any other ideas? > > PAIX is probably now the largest exchange point on the U.S. West Coast: > http://www.switchanddata.com/Solutions/PAIX/Customers/PaloAlto/ I think so too. Plus that Vixie has always been helpful with other requests for support from our side. Please bring up this topic in Monday's RIS meeting so we can decide. 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 ------------------------------------------------------------------------------ Process and Procedure are the last hiding place of people without the wit and wisdom to do their job properly. (David Brent). From henk at ripe.net Fri Jul 23 11:14:16 2004 From: henk at ripe.net (Henk Uijterwaal (RIPE NCC)) Date: Fri, 23 Jul 2004 11:14:16 +0200 (CEST) Subject: [ris-int] Re: MSK-IX RRC In-Reply-To: <038201c47007$6a768250$1f0200c1@rockstar> References: <038201c47007$6a768250$1f0200c1@rockstar> Message-ID: On Thu, 22 Jul 2004, Matthew Williams wrote: > > The ideal would be that they order it and we get the invoice > > from Dell. Perhaps ask Sonia to call her contact at Dell and > > figure out what would be the easiest approach. > > She did that, and they weren't too happy about above ("bad experiences > with customs"). We will have to specify what we want and send specs to > MSK-IX. Sonia was adamant about getting a quote on price (to be approved > by us), before they go ahead with the order. Tell them to get a quote then and send it to us. Henk > > 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: 21 July 2004 14:40 > > To: Bruce Campbell > > Cc: Matthew Williams; ris-int at ripe.net > > Subject: Re: [ris-int] Re: MSK-IX RRC > > > > > > On Tue, 20 Jul 2004, Bruce Campbell wrote: > > > > > On Tue, 20 Jul 2004, Matthew Williams wrote: > > > > > > > Just thinking out loud: > > > > > > > > In order to circumvent excessive $$$ at Russian customs, > > wouldn't it > > > > be smarter to have the IXP order a Dell PowerEdge to OPS > > > > requirements and ship your nifty little CD instead? Would > > that work > > > > or should we just go down the normal route. I will > > naturally have to > > > > ask the IXP as well. > > > > > > It would be far easier, as long as we know the IP configuration in > > > advance. > > > > If they buy it, we'll have to reimburse them. Please check > > with Jochem about transferring the euro's. > > > > The ideal would be that they order it and we get the invoice > > from Dell. Perhaps ask Sonia to call her contact at Dell and > > figure out what would be the easiest approach. > > > > > > 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 > > -------------------------------------------------------------- > > ---------------- > > > > Process and Procedure are the last hiding place of people > > without the wit > > and wisdom to do their job properly. > > (David Brent). > > > > ------------------------------------------------------------------------------ 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 ------------------------------------------------------------------------------ Process and Procedure are the last hiding place of people without the wit and wisdom to do their job properly. (David Brent). From wilhelm at ripe.net Fri Jul 23 13:16:24 2004 From: wilhelm at ripe.net (Rene Wilhelm) Date: Fri, 23 Jul 2004 13:16:24 +0200 Subject: [ris-int] RRC12 announcement on www.ripe.net Message-ID: <200407231116.i6NBGOjR015717@birch.ripe.net> I didn't keep track of it myself, but an external user noticed this announcement on www.ripe.net yesterday, JULY 22. The date seems wrong :( RIPE NCC Announcements [22 June 2004] RIPE NCC Remote Route Collector Deployed at German Internet Exchange (DE-CIX) I was also wondering if it wouldn't be better to make the link point to a page with the announcement that was send out to ris-users, (copied below) rather than jump deep down into the RIS web tree. The announcement puts things more into context with a paragraph summarizing the project and pointers to more RIS info at the end. The http://www.ripe.net/ris/rrc12.html page seems more targeted at people who already familiar with RIS and just want to learn where the box is, what the peering policy and peering details are. -- Rene > From: ris-users-admin at ripe.net > [mailto:ris-users-admin at ripe.net] On Behalf Of Matthew Williams > Sent: 07 July 2004 19:11 > To: ris-users at ripe.net > Subject: ANNOUNCEMENT: New RIS Remote Route Collector at > DE-CIX (RRC12) > > [Apologies for duplicate mails] > > Dear All, > > The RIPE NCC is pleased to announce that the RIS Project's > twelth* Remote Route Collector, RRC12, is now ready to peer > with members at the German Internet Exchange (DE-CIX). > > RRC12 is located at the German Internet Exchange (DE-CIX), > and has been operational since July 2004. The RRC has an > interface on the shared DE-CIX fabric, running both IPv4 and > IPv6, and collects routing information from all exchange > members, who are willing to peer with us. > > The use of TCP MD5 Signatures on IPv4 BGP sessions is > supported on all RIS Route Collectors. MD5, however, is not > supported on IPv6 sessions. > > Details: > -------- > - Peering address: 80.81.192.152 (IPv4); 2001:7f8::316e:0:1 (IPv6) > - Autonomous system: 12654 > - Policy: http://www.ripe.net/ris/rrc12.html > - Peering requests: > * Email: rispeering at ripe.net > * Web form at URL: http://www.ris.ripe.net/cgi-bin/peerreg.cgi > > The Routing Information Service (RIS), which started as a > modest RIPE NCC project in 1999, has gradually grown to over > 300 IPv4 and IPv6 peers at now twelve* data collection points > in Europe, Japan and North America. Our mission is to collect > BGP routing information over a function of time, and make it > available to the Internet community. In essence, this means > devising tools that can help ISPs debug problems over time > without being limited to one BGP view and providing RIS raw > data regarding the Internet's historical development. > > Useful Links: > ------------- > RIS Info: http://www.ripe.net/ris/ > RIS Tools: http://www.ripe.net/ris/query.html > List of RRC Locations: http://www.ris.ripe.net/cgi-bin/rrcstatus.cgi > > Please send your comments to ris-int at ripe.net. > > Best regards, > The RIS Team > > *) RRC09 has been decommissioned > > --- > > Matthew Williams (MW243-RIPE) > > Customer Liaison Engineer > > RIPE NCC - http://www.ripe.net/np/ From webmaster at ripe.net Fri Jul 23 13:25:10 2004 From: webmaster at ripe.net (RIPE NCC Webmaster) Date: Fri, 23 Jul 2004 13:25:10 +0200 Subject: [ris-int] Re: RRC12 announcement on www.ripe.net In-Reply-To: Your message of Fri, 23 Jul 2004 13:16:24 +0200. <200407231116.i6NBGOjR015717@birch.ripe.net> References: <200407231116.i6NBGOjR015717@birch.ripe.net> Message-ID: <200407231125.i6NBPAjR019608@birch.ripe.net> Rene Wilhelm writes: * * I didn't keep track of it myself, but an external user noticed * this announcement on www.ripe.net yesterday, JULY 22. The date * seems wrong :( Damn.. I changed it to 20 July. * * RIPE NCC Announcements * * [22 June 2004] * RIPE NCC Remote Route Collector Deployed at German Internet Exchange (DE-CIX * ) * * * I was also wondering if it wouldn't be better to make the link * point to a page with the announcement that was send out to ris-users, * (copied below) rather than jump deep down into the RIS web tree. * The announcement puts things more into context with a paragraph * summarizing the project and pointers to more RIS info at the end. * The http://www.ripe.net/ris/rrc12.html page seems more * targeted at people who already familiar with RIS and just * want to learn where the box is, what the peering policy and * peering details are. * OK, maybe you, Arife or Matthew can make a page in ris/news with the content of the announcement? We don't really want to link to messages in mail archives.. -J * * -- Rene * * * > From: ris-users-admin at ripe.net * > [mailto:ris-users-admin at ripe.net] On Behalf Of Matthew Williams * > Sent: 07 July 2004 19:11 * > To: ris-users at ripe.net * > Subject: ANNOUNCEMENT: New RIS Remote Route Collector at * > DE-CIX (RRC12) * > * > [Apologies for duplicate mails] * > * > Dear All, * > * > The RIPE NCC is pleased to announce that the RIS Project's * > twelth* Remote Route Collector, RRC12, is now ready to peer * > with members at the German Internet Exchange (DE-CIX). * > * > RRC12 is located at the German Internet Exchange (DE-CIX), * > and has been operational since July 2004. The RRC has an * > interface on the shared DE-CIX fabric, running both IPv4 and * > IPv6, and collects routing information from all exchange * > members, who are willing to peer with us. * > * > The use of TCP MD5 Signatures on IPv4 BGP sessions is * > supported on all RIS Route Collectors. MD5, however, is not * > supported on IPv6 sessions. * > * > Details: * > -------- * > - Peering address: 80.81.192.152 (IPv4); 2001:7f8::316e:0:1 (IPv6) * > - Autonomous system: 12654 * > - Policy: http://www.ripe.net/ris/rrc12.html * > - Peering requests: * > * Email: rispeering at ripe.net * > * Web form at URL: http://www.ris.ripe.net/cgi-bin/peerreg.cgi * > * > The Routing Information Service (RIS), which started as a * > modest RIPE NCC project in 1999, has gradually grown to over * > 300 IPv4 and IPv6 peers at now twelve* data collection points * > in Europe, Japan and North America. Our mission is to collect * > BGP routing information over a function of time, and make it * > available to the Internet community. In essence, this means * > devising tools that can help ISPs debug problems over time * > without being limited to one BGP view and providing RIS raw * > data regarding the Internet's historical development. * > * > Useful Links: * > ------------- * > RIS Info: http://www.ripe.net/ris/ * > RIS Tools: http://www.ripe.net/ris/query.html * > List of RRC Locations: http://www.ris.ripe.net/cgi-bin/rrcstatus.cgi * > * > Please send your comments to ris-int at ripe.net. * > * > Best regards, * > The RIS Team * > * > *) RRC09 has been decommissioned * > * > --- * > > Matthew Williams (MW243-RIPE) * > > Customer Liaison Engineer * > > RIPE NCC - http://www.ripe.net/np/ * From arife at ripe.net Fri Jul 23 13:57:04 2004 From: arife at ripe.net (Arife Vural) Date: Fri, 23 Jul 2004 13:57:04 +0200 Subject: [ris-int] ris@ripe.net e-mail are ticketized from now on. Message-ID: <20040723115704.GK13193@ripe.net> Hi guys, ris e-mails are ticketized from now on. ris is staying as mailinglist, and one copy of the e-mail is going to RIS ticketing que. People who are in the ris list will continue get the all ris e-mails. If you do not want, ask OPS to remove your e-mail address. But, please if you like to reply any of those e-mails, use XRTT. Otherwise, we loose control who replied which e-mail and so. Arife From henk at ripe.net Fri Jul 23 14:13:49 2004 From: henk at ripe.net (Henk Uijterwaal (RIPE NCC)) Date: Fri, 23 Jul 2004 14:13:49 +0200 (CEST) Subject: [ris-int] RIS move status Message-ID: Arife, Can I have a few minutes on Monday's agenda to go over the status of the move, see attached MPP file with details? Thx, 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 ------------------------------------------------------------------------------ Process and Procedure are the last hiding place of people without the wit and wisdom to do their job properly. (David Brent). -------------- next part -------------- A non-text attachment was scrubbed... Name: RIS_Move.mpp Type: application/octet-stream Size: 621056 bytes Desc: URL: From arife at ripe.net Fri Jul 23 14:23:59 2004 From: arife at ripe.net (Arife Vural) Date: Fri, 23 Jul 2004 14:23:59 +0200 Subject: [ris-int] RIS move status In-Reply-To: References: Message-ID: <20040723122359.GN13193@ripe.net> > Can I have a few minutes on Monday's agenda to go over the status of the > move, see attached MPP file with details? Thx, Sure. Agenda will be like that - RIS moving status - MyASN status - RRC08 re-location - Status of RRC13, Moscow Any other item? Arife - > > 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 > ------------------------------------------------------------------------------ > > Process and Procedure are the last hiding place of people without the wit > and wisdom to do their job properly. (David Brent). From matthew at ripe.net Fri Jul 23 14:44:04 2004 From: matthew at ripe.net (Matthew Williams) Date: Fri, 23 Jul 2004 14:44:04 +0200 Subject: [ris-int] Re: RRC12 announcement on www.ripe.net In-Reply-To: <200407231125.i6NBPAjR019608@birch.ripe.net> Message-ID: <002301c470b2$bc8b9390$1f0200c1@rockstar> > OK, maybe you, Arife or Matthew can make a page in ris/news > with the content of the announcement? We don't really want > to link to messages in mail archives.. Sure, we could do that. Mind you, what is Adrian up to nowadays? Great opportunity to dig into the RIS aspect of IS... ;) Cheers, Matthew > -----Original Message----- > From: ris-int-admin at ripe.net [mailto:ris-int-admin at ripe.net] > On Behalf Of RIPE NCC Webmaster > Sent: 23 July 2004 13:25 > To: Rene Wilhelm > Cc: ris-int at ripe.net > Subject: [ris-int] Re: RRC12 announcement on www.ripe.net > > > > Rene Wilhelm writes: > * > * I didn't keep track of it myself, but an external user noticed > * this announcement on www.ripe.net yesterday, JULY 22. The date > * seems wrong :( > > Damn.. I changed it to 20 July. > > * > * RIPE NCC Announcements > * > * [22 June 2004] > * RIPE NCC Remote Route Collector Deployed at German > Internet Exchange (DE-CIX > * ) > * > * > * I was also wondering if it wouldn't be better to make the link > * point to a page with the announcement that was send out to > ris-users, > * (copied below) rather than jump deep down into the RIS web tree. > * The announcement puts things more into context with a paragraph > * summarizing the project and pointers to more RIS info at the end. > * The http://www.ripe.net/ris/rrc12.html page seems more > * targeted at people who already familiar with RIS and just > * want to learn where the box is, what the peering policy and > * peering details are. > * > > OK, maybe you, Arife or Matthew can make a page in ris/news > with the content of the announcement? We don't really want > to link to messages in mail archives.. > > -J > > > * > * -- Rene > * > * > * > From: ris-users-admin at ripe.net > * > [mailto:ris-users-admin at ripe.net] On Behalf Of Matthew Williams > * > Sent: 07 July 2004 19:11 > * > To: ris-users at ripe.net > * > Subject: ANNOUNCEMENT: New RIS Remote Route Collector at > * > DE-CIX (RRC12) > * > > * > [Apologies for duplicate mails] > * > > * > Dear All, > * > > * > The RIPE NCC is pleased to announce that the RIS Project's > * > twelth* Remote Route Collector, RRC12, is now ready to peer > * > with members at the German Internet Exchange (DE-CIX). > * > > * > RRC12 is located at the German Internet Exchange (DE-CIX), > * > and has been operational since July 2004. The RRC has an > * > interface on the shared DE-CIX fabric, running both IPv4 and > * > IPv6, and collects routing information from all exchange > * > members, who are willing to peer with us. > * > > * > The use of TCP MD5 Signatures on IPv4 BGP sessions is > * > supported on all RIS Route Collectors. MD5, however, is not > * > supported on IPv6 sessions. > * > > * > Details: > * > -------- > * > - Peering address: 80.81.192.152 (IPv4); > 2001:7f8::316e:0:1 (IPv6) > * > - Autonomous system: 12654 > * > - Policy: http://www.ripe.net/ris/rrc12.html > * > - Peering requests: > * > * Email: rispeering at ripe.net > * > * Web form at URL: > http://www.ris.ripe.net/cgi-bin/peerreg.cgi > * > > * > The > Routing Information Service (RIS), which started as a > * > modest RIPE NCC project in 1999, has gradually grown to over > * > 300 IPv4 and IPv6 peers at now twelve* data collection points > * > in Europe, Japan and North America. Our mission is to collect > * > BGP routing information over a function of time, and make it > * > available to the Internet community. In essence, this means > * > devising tools that can help ISPs debug problems over time > * > without being limited to one BGP view and providing RIS raw > * > data regarding the Internet's historical development. > * > > * > Useful Links: > * > ------------- > * > RIS Info: http://www.ripe.net/ris/ > * > RIS Tools: http://www.ripe.net/ris/query.html > * > List of RRC Locations: > http://www.ris.ripe.net/cgi-> bin/rrcstatus.cgi > * > > * > > Please send your comments to > ris-int at ripe.net. > * > > * > Best regards, > * > The RIS Team > * > > * > *) RRC09 has been decommissioned > * > > * > --- > * > > Matthew Williams (MW243-RIPE) > * > > Customer Liaison Engineer > * > > RIPE NCC - http://www.ripe.net/np/ > * > From webmaster at ripe.net Fri Jul 23 15:49:04 2004 From: webmaster at ripe.net (RIPE NCC Webmaster) Date: Fri, 23 Jul 2004 15:49:04 +0200 Subject: [ris-int] Re: RRC12 announcement on www.ripe.net In-Reply-To: Your message of Fri, 23 Jul 2004 14:44:04 +0200. <002301c470b2$bc8b9390$1f0200c1@rockstar> References: <002301c470b2$bc8b9390$1f0200c1@rockstar> Message-ID: <200407231349.i6NDn4jR005134@birch.ripe.net> "Matthew Williams" writes: * > OK, maybe you, Arife or Matthew can make a page in ris/news * > with the content of the announcement? We don't really want * > to link to messages in mail archives.. * * Sure, we could do that. Mind you, what is Adrian up to nowadays? Great opportun * ity to dig into the RIS aspect of IS... ;) Talk to Adrian. BTW, if you want him to change RIS pages, make sure you add him to the projects group. -J * * Cheers, * Matthew * * > -----Original Message----- * > From: ris-int-admin at ripe.net [mailto:ris-int-admin at ripe.net] * > On Behalf Of RIPE NCC Webmaster * > Sent: 23 July 2004 13:25 * > To: Rene Wilhelm * > Cc: ris-int at ripe.net * > Subject: [ris-int] Re: RRC12 announcement on www.ripe.net * > * > * > * > Rene Wilhelm writes: * > * * > * I didn't keep track of it myself, but an external user noticed * > * this announcement on www.ripe.net yesterday, JULY 22. The date * > * seems wrong :( * > * > Damn.. I changed it to 20 July. * > * > * * > * RIPE NCC Announcements * > * * > * [22 June 2004] * > * RIPE NCC Remote Route Collector Deployed at German * > Internet Exchange (DE-CIX * > * ) * > * * > * * > * I was also wondering if it wouldn't be better to make the link * > * point to a page with the announcement that was send out to * > ris-users, * > * (copied below) rather than jump deep down into the RIS web tree. * > * The announcement puts things more into context with a paragraph * > * summarizing the project and pointers to more RIS info at the end. * > * The http://www.ripe.net/ris/rrc12.html page seems more * > * targeted at people who already familiar with RIS and just * > * want to learn where the box is, what the peering policy and * > * peering details are. * > * * > * > OK, maybe you, Arife or Matthew can make a page in ris/news * > with the content of the announcement? We don't really want * > to link to messages in mail archives.. * > * > -J * > * > * > * * > * -- Rene * > * * > * * > * > From: ris-users-admin at ripe.net * > * > [mailto:ris-users-admin at ripe.net] On Behalf Of Matthew Williams * > * > Sent: 07 July 2004 19:11 * > * > To: ris-users at ripe.net * > * > Subject: ANNOUNCEMENT: New RIS Remote Route Collector at * > * > DE-CIX (RRC12) * > * > * > * > [Apologies for duplicate mails] * > * > * > * > Dear All, * > * > * > * > The RIPE NCC is pleased to announce that the RIS Project's * > * > twelth* Remote Route Collector, RRC12, is now ready to peer * > * > with members at the German Internet Exchange (DE-CIX). * > * > * > * > RRC12 is located at the German Internet Exchange (DE-CIX), * > * > and has been operational since July 2004. The RRC has an * > * > interface on the shared DE-CIX fabric, running both IPv4 and * > * > IPv6, and collects routing information from all exchange * > * > members, who are willing to peer with us. * > * > * > * > The use of TCP MD5 Signatures on IPv4 BGP sessions is * > * > supported on all RIS Route Collectors. MD5, however, is not * > * > supported on IPv6 sessions. * > * > * > * > Details: * > * > -------- * > * > - Peering address: 80.81.192.152 (IPv4); * > 2001:7f8::316e:0:1 (IPv6) * > * > - Autonomous system: 12654 * > * > - Policy: http://www.ripe.net/ris/rrc12.html * > * > - Peering requests: * > * > * Email: rispeering at ripe.net * > * > * Web form at URL: * > http://www.ris.ripe.net/cgi-bin/peerreg.cgi * > * > * > * > The * > Routing Information Service (RIS), which started as a * > * > modest RIPE NCC project in 1999, has gradually grown to over * > * > 300 IPv4 and IPv6 peers at now twelve* data collection points * > * > in Europe, Japan and North America. Our mission is to collect * > * > BGP routing information over a function of time, and make it * > * > available to the Internet community. In essence, this means * > * > devising tools that can help ISPs debug problems over time * > * > without being limited to one BGP view and providing RIS raw * > * > data regarding the Internet's historical development. * > * > * > * > Useful Links: * > * > ------------- * > * > RIS Info: http://www.ripe.net/ris/ * > * > RIS Tools: http://www.ripe.net/ris/query.html * > * > List of RRC Locations: * > http://www.ris.ripe.net/cgi-> bin/rrcstatus.cgi * > * > * > * > * > Please send your comments to * > ris-int at ripe.net. * > * > * > * > Best regards, * > * > The RIS Team * > * > * > * > *) RRC09 has been decommissioned * > * > * > * > --- * > * > > Matthew Williams (MW243-RIPE) * > * > > Customer Liaison Engineer * > * > > RIPE NCC - http://www.ripe.net/np/ * > * * > * From matthew at ripe.net Fri Jul 23 16:08:11 2004 From: matthew at ripe.net (Matthew Williams) Date: Fri, 23 Jul 2004 16:08:11 +0200 Subject: FW: [ris-int] Re: RRC12 announcement on www.ripe.net Message-ID: <002401c470be$7d05dd50$1f0200c1@rockstar> Hi Adrian, Rene came up with the idea to link announcements to a little RIS intro page with a few links. Is that something you can help us with? Cheers, Matthew > -----Original Message----- > From: ris-int-admin at ripe.net [mailto:ris-int-admin at ripe.net] > On Behalf Of RIPE NCC Webmaster > Sent: 23 July 2004 15:49 > To: Matthew Williams > Cc: ris-int at ripe.net; 'Rene Wilhelm' > Subject: Re: [ris-int] Re: RRC12 announcement on www.ripe.net > > > > "Matthew Williams" writes: > * > OK, maybe you, Arife or Matthew can make a page in ris/news > * > with the content of the announcement? We don't really want > * > to link to messages in mail archives.. > * > * Sure, we could do that. Mind you, what is Adrian up to > nowadays? Great opportun > * ity to dig into the RIS aspect of IS... ;) > > Talk to Adrian. BTW, if you want him to change RIS pages, > make sure you add him to the projects group. > > -J > > * > * Cheers, > * Matthew > * > * > -----Original Message----- > * > From: ris-int-admin at ripe.net [mailto:ris-int-admin at ripe.net] > * > On Behalf Of RIPE NCC Webmaster > * > Sent: 23 July 2004 13:25 > * > To: Rene Wilhelm > * > Cc: ris-int at ripe.net > * > Subject: [ris-int] Re: RRC12 announcement on www.ripe.net > * > > * > > * > > * > Rene Wilhelm writes: > * > * > * > * I didn't keep track of it myself, but an external user noticed > * > * this announcement on www.ripe.net yesterday, JULY 22. The date > * > * seems wrong :( > * > > * > Damn.. I changed it to 20 July. > * > > * > * > * > * RIPE NCC Announcements > * > * > * > * [22 June 2004] > * > * RIPE NCC Remote Route Collector Deployed at German > * > Internet Exchange (DE-CIX > * > * ) > * > * > * > * > * > * I was also wondering if it wouldn't be better to make the link > * > * point to a page with the announcement that was send out to > * > ris-users, > * > * (copied below) rather than jump deep down into the > RIS web tree. > * > * The announcement puts things more into context with a > paragraph > * > * summarizing the project and pointers to more RIS info > at the end. > * > * The http://www.ripe.net/ris/rrc12.html page seems more > * > * targeted at people who already familiar with RIS and just > * > * want to learn where the box is, what the peering policy and > * > * peering details are. > * > * > * > > * > OK, maybe you, Arife or Matthew can make a page in ris/news > * > with the content of the announcement? We don't really want > * > to link to messages in mail archives.. > * > > * > -J > * > > * > > * > * > * > * -- Rene > * > * > * > * > * > * > From: ris-users-admin at ripe.net > * > * > [mailto:ris-users-admin at ripe.net] On Behalf Of > Matthew Williams > * > * > Sent: 07 July 2004 19:11 > * > * > To: ris-users at ripe.net > * > * > Subject: ANNOUNCEMENT: New RIS Remote Route Collector at > * > * > DE-CIX (RRC12) > * > * > > * > * > [Apologies for duplicate mails] > * > * > > * > * > Dear All, > * > * > > * > * > The RIPE NCC is pleased to announce that the RIS Project's > * > * > twelth* Remote Route Collector, RRC12, is now ready to peer > * > * > with members at the German Internet Exchange (DE-CIX). > * > * > > * > * > RRC12 is located at the German Internet Exchange (DE-CIX), > * > * > and has been operational since July 2004. The RRC has an > * > * > interface on the shared DE-CIX fabric, running both > IPv4 and > * > * > IPv6, and collects routing information from all exchange > * > * > members, who are willing to peer with us. > * > * > > * > * > The use of TCP MD5 Signatures on IPv4 BGP sessions is > * > * > supported on all RIS Route Collectors. MD5, however, is not > * > * > supported on IPv6 sessions. > * > * > > * > * > Details: > * > * > -------- > * > * > - Peering address: 80.81.192.152 (IPv4); > * > 2001:7f8::316e:0:1 (IPv6) > * > * > - Autonomous system: 12654 > * > * > - Policy: http://www.ripe.net/ris/rrc12.html > * > * > - Peering requests: > * > * > * Email: rispeering at ripe.net > * > * > * Web form at URL: > * > http://www.ris.ripe.net/cgi-bin/peerreg.cgi > * > * > > * > * > The > * > Routing Information Service (RIS), which started as a > * > * > modest RIPE NCC project in 1999, has gradually > grown to over > * > * > 300 IPv4 and IPv6 peers at now twelve* data > collection points > * > * > in Europe, Japan and North America. Our mission is > to collect > * > * > BGP routing information over a function of time, > and make it > * > * > available to the Internet community. In essence, this means > * > * > devising tools that can help ISPs debug problems over time > * > * > without being limited to one BGP view and providing RIS raw > * > * > data regarding the Internet's historical development. > * > * > > * > * > Useful Links: > * > * > ------------- > * > * > RIS Info: http://www.ripe.net/ris/ > * > * > RIS Tools: http://www.ripe.net/ris/query.html > * > * > List of RRC Locations: > * > http://www.ris.ripe.net/cgi-> bin/rrcstatus.cgi > * > * > > * > * > > * > Please send your comments to > * > ris-int at ripe.net. > * > * > > * > * > Best regards, > * > * > The RIS Team > * > * > > * > * > *) RRC09 has been decommissioned > * > * > > * > * > --- > * > * > > Matthew Williams (MW243-RIPE) > * > * > > Customer Liaison Engineer > * > * > > RIPE NCC - http://www.ripe.net/np/ > * > * > * > > * > From matthew at ripe.net Fri Jul 23 16:11:12 2004 From: matthew at ripe.net (Matthew Williams) Date: Fri, 23 Jul 2004 16:11:12 +0200 Subject: [ris-int] FW: NCC#2004073298 Re: rrc01:PEERING 8210 Message-ID: <002501c470be$e8ae2300$1f0200c1@rockstar> Peering requests hasn't worked very well in the past. Good work :) Cheers, Matthew > -----Original Message----- > From: RIPE NCC Acknowledgements [mailto:hm-ack at ripe.net] > Sent: 23 July 2004 14:48 > To: RIS Peering Request > Subject: NCC#2004073298 Re: rrc01:PEERING 8210 > > > Greetings, > > This message has been automatically generated in response to the > e-mail: > > To: RIS Peerings > From: RIS Peering Request > Date: Fri, 23 Jul 2004 12:47:44 GMT > Message-ID: <200407231247.i6NCli3U013164 at halfweg.ripe.net> > Subject: rrc01:PEERING 8210 > > There is no need to reply to this message right now. Your > ticket has been assigned an ID of "NCC#2004073298". Please > include this string in the subject line of any further > correspondence on this matter. > > For more information about the RIPE NCC RIS Project, please > refer to http://www.ripe.net/ris/. > > Thank you, > > RIPE NCC Software Department > From james at ripe.net Fri Jul 23 16:18:08 2004 From: james at ripe.net (James Aldridge) Date: Fri, 23 Jul 2004 16:18:08 +0200 Subject: [ris-int] FW: NCC#2004073298 Re: rrc01:PEERING 8210 In-Reply-To: <002501c470be$e8ae2300$1f0200c1@rockstar> References: <002501c470be$e8ae2300$1f0200c1@rockstar> Message-ID: <0825A1542E0CB1127EDB4B49@guest-wv-22.ripe.net> --On Friday, 23 July, 2004 16:11 +0200 Matthew Williams wrote: > Peering requests hasn't worked very well in the past. > Good work :) > > Cheers, > Matthew > >> -----Original Message----- >> From: RIPE NCC Acknowledgements [mailto:hm-ack at ripe.net] The mail should probably come from an address other than than hm-ack at ripe.net James From arife at ripe.net Fri Jul 23 16:39:26 2004 From: arife at ripe.net (Arife Vural) Date: Fri, 23 Jul 2004 16:39:26 +0200 Subject: [ris-int] FW: NCC#2004073298 Re: rrc01:PEERING 8210 In-Reply-To: <0825A1542E0CB1127EDB4B49@guest-wv-22.ripe.net> References: <002501c470be$e8ae2300$1f0200c1@rockstar> <0825A1542E0CB1127EDB4B49@guest-wv-22.ripe.net> Message-ID: <20040723143926.GB22606@ripe.net> > > > >>-----Original Message----- > >>From: RIPE NCC Acknowledgements [mailto:hm-ack at ripe.net] > > The mail should probably come from an address other than than > hm-ack at ripe.net As far as I know hm-ack at ripe.net goes to /dev/null and I did not see much point create another alias to /dev/null and used the available one. Arife From matthew at ripe.net Fri Jul 23 17:09:05 2004 From: matthew at ripe.net (Matthew Williams) Date: Fri, 23 Jul 2004 17:09:05 +0200 Subject: [ris-int] RIS move status In-Reply-To: <20040723122359.GN13193@ripe.net> Message-ID: <003201c470c6$fec511a0$1f0200c1@rockstar> I think we'll need to address rrc06 too. Cheers, Matthew > -----Original Message----- > From: ris-int-admin at ripe.net [mailto:ris-int-admin at ripe.net] > On Behalf Of Arife Vural > Sent: 23 July 2004 14:24 > To: Henk Uijterwaal (RIPE NCC) > Cc: ris-int at ripe.net > Subject: Re: [ris-int] RIS move status > > > > > Can I have a few minutes on Monday's agenda to go over the > status of > > the move, see attached MPP file with details? Thx, > > Sure. > > Agenda will be like that > > - RIS moving status > - MyASN status > - RRC08 re-location > - Status of RRC13, Moscow > > Any other item? > > Arife > > - > > > > 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 > > > ---------------------------------------------------------------------- > > -------- > > > > Process and Procedure are the last hiding place of people > without the wit > > and wisdom to do their job properly. > (David Brent). > From henk at ripe.net Fri Jul 23 17:17:12 2004 From: henk at ripe.net (Henk Uijterwaal (RIPE NCC)) Date: Fri, 23 Jul 2004 17:17:12 +0200 (CEST) Subject: [ris-int] FW: NCC#2004073298 Re: rrc01:PEERING 8210 In-Reply-To: <20040723143926.GB22606@ripe.net> References: <002501c470be$e8ae2300$1f0200c1@rockstar> <0825A1542E0CB1127EDB4B49@guest-wv-22.ripe.net> <20040723143926.GB22606@ripe.net> Message-ID: On Fri, 23 Jul 2004, Arife Vural wrote: > > > > > > >>-----Original Message----- > > >>From: RIPE NCC Acknowledgements [mailto:hm-ack at ripe.net] > > > > The mail should probably come from an address other than than > > hm-ack at ripe.net > > > As far as I know hm-ack at ripe.net goes to /dev/null and I did not > see much point create another alias to /dev/null and used the > available one. In that case, shouldn't the message come from "do not reply" and have a Reply-to: field? 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 ------------------------------------------------------------------------------ Process and Procedure are the last hiding place of people without the wit and wisdom to do their job properly. (David Brent). From arife at ripe.net Fri Jul 23 17:40:29 2004 From: arife at ripe.net (Arife Vural) Date: Fri, 23 Jul 2004 17:40:29 +0200 Subject: [ris-int] FW: NCC#2004073298 Re: rrc01:PEERING 8210 In-Reply-To: References: <002501c470be$e8ae2300$1f0200c1@rockstar> <0825A1542E0CB1127EDB4B49@guest-wv-22.ripe.net> <20040723143926.GB22606@ripe.net> Message-ID: <20040723154029.GJ22606@ripe.net> > > > >>From: RIPE NCC Acknowledgements [mailto:hm-ack at ripe.net] > > > > > > The mail should probably come from an address other than than > > > hm-ack at ripe.net > > > > > > As far as I know hm-ack at ripe.net goes to /dev/null and I did not > > see much point create another alias to /dev/null and used the > > available one. > > In that case, shouldn't the message come from "do not reply" and have a something like that I guess, do-not-reply at ripe.net. it sounds good to me. > Reply-to: field? Now, it looks we do not have Reply-to, I'm not sure it will make sense setting this one, since we do not want them reply for ACK. I will check with other guys and it would be useful or not. arife > > 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 > ------------------------------------------------------------------------------ > > Process and Procedure are the last hiding place of people without the wit > and wisdom to do their job properly. (David Brent). From henk at ripe.net Fri Jul 23 17:43:41 2004 From: henk at ripe.net (Henk Uijterwaal (RIPE NCC)) Date: Fri, 23 Jul 2004 17:43:41 +0200 (CEST) Subject: [ris-int] FW: NCC#2004073298 Re: rrc01:PEERING 8210 In-Reply-To: <20040723154029.GJ22606@ripe.net> References: <002501c470be$e8ae2300$1f0200c1@rockstar> <0825A1542E0CB1127EDB4B49@guest-wv-22.ripe.net> <20040723143926.GB22606@ripe.net> <20040723154029.GJ22606@ripe.net> Message-ID: On Fri, 23 Jul 2004, Arife Vural wrote: > > > > > >>From: RIPE NCC Acknowledgements [mailto:hm-ack at ripe.net] > > > > > > > > The mail should probably come from an address other than than > > > > hm-ack at ripe.net > > > > > > > > > As far as I know hm-ack at ripe.net goes to /dev/null and I did not > > > see much point create another alias to /dev/null and used the > > > available one. > > > > In that case, shouldn't the message come from "do not reply" and have a > > something like that I guess, do-not-reply at ripe.net. it sounds good to me. > > > Reply-to: field? > > Now, it looks we do not have Reply-to, I'm not sure it will make sense > setting this one, since we do not want them reply for ACK. I will check > with other guys and it would be useful or not. No, but people tend to reply to the last mail they have in their files, if you use something like hm-ack at r.n it looks as if a human will read it. 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 ------------------------------------------------------------------------------ Process and Procedure are the last hiding place of people without the wit and wisdom to do their job properly. (David Brent). From shane at ripe.net Fri Jul 23 18:01:24 2004 From: shane at ripe.net (Shane Kerr) Date: Fri, 23 Jul 2004 18:01:24 +0200 Subject: [ris-int] FW: NCC#2004073298 Re: rrc01:PEERING 8210 In-Reply-To: References: <002501c470be$e8ae2300$1f0200c1@rockstar> <0825A1542E0CB1127EDB4B49@guest-wv-22.ripe.net> <20040723143926.GB22606@ripe.net> <20040723154029.GJ22606@ripe.net> Message-ID: <41013654.4070609@ripe.net> Henk Uijterwaal (RIPE NCC) wrote: > On Fri, 23 Jul 2004, Arife Vural wrote: > > >>>>>>>From: RIPE NCC Acknowledgements [mailto:hm-ack at ripe.net] >>>>> >>>>>The mail should probably come from an address other than than >>>>>hm-ack at ripe.net >>>> >>>> >>>>As far as I know hm-ack at ripe.net goes to /dev/null and I did not >>>>see much point create another alias to /dev/null and used the >>>>available one. >>> >>>In that case, shouldn't the message come from "do not reply" and have a >> >>something like that I guess, do-not-reply at ripe.net. it sounds good to me. >> >> >>>Reply-to: field? >> >>Now, it looks we do not have Reply-to, I'm not sure it will make sense >>setting this one, since we do not want them reply for ACK. I will check >>with other guys and it would be useful or not. > > > No, but people tend to reply to the last mail they have in their files, > if you use something like hm-ack at r.n it looks as if a human will read > it. We have an address for this, called . Arife, can you change the autoresponder accordingly? TIA, -- Shane Kerr RIPE NCC From wilhelm at ripe.net Fri Jul 23 18:10:53 2004 From: wilhelm at ripe.net (Rene Wilhelm) Date: Fri, 23 Jul 2004 18:10:53 +0200 Subject: [ris-int] FW: NCC#2004073298 Re: rrc01:PEERING 8210 In-Reply-To: Message from Shane Kerr of "Fri, 23 Jul 2004 18:01:24 +0200." <41013654.4070609@ripe.net> Message-ID: <200407231610.i6NGArjR022749@birch.ripe.net> > > No, but people tend to reply to the last mail they have in their files, > > if you use something like hm-ack at r.n it looks as if a human will read > > it. > > We have an address for this, called . Why does the autoresponse have to come from an unread email account? If I were a user and needed to add info to a ticket or query it's status, it would be most convenient if I could reply to the first (auto)reply to my initial message, as that ensures I get the ticket number right. This is how the OPS & TT-OPS ticketing systems work. (ok the tt ticketing system, currently doesn't autoreply, but if it would, it would send one "From: tt-ops") -- Rene From henk at ripe.net Fri Jul 23 18:19:37 2004 From: henk at ripe.net (Henk Uijterwaal (RIPE NCC)) Date: Fri, 23 Jul 2004 18:19:37 +0200 (CEST) Subject: [ris-int] FW: NCC#2004073298 Re: rrc01:PEERING 8210 In-Reply-To: <200407231610.i6NGArjR022749@birch.ripe.net> References: <200407231610.i6NGArjR022749@birch.ripe.net> Message-ID: On Fri, 23 Jul 2004, Rene Wilhelm wrote: > > > No, but people tend to reply to the last mail they have in their files, > > > if you use something like hm-ack at r.n it looks as if a human will read > > > it. > > > > We have an address for this, called . > > Why does the autoresponse have to come from an unread email account? > > If I were a user and needed to add info to a ticket or query it's > status, it would be most convenient if I could reply to the > first (auto)reply to my initial message, as that ensures I get the ticket > number right. Can't we do that with a reply-to field? I don't really care where the mail comes from, as long as it is clear how to respond. 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 ------------------------------------------------------------------------------ Process and Procedure are the last hiding place of people without the wit and wisdom to do their job properly. (David Brent). From shane at ripe.net Fri Jul 23 18:27:26 2004 From: shane at ripe.net (Shane Kerr) Date: Fri, 23 Jul 2004 18:27:26 +0200 Subject: [ris-int] FW: NCC#2004073298 Re: rrc01:PEERING 8210 In-Reply-To: <200407231610.i6NGArjR022749@birch.ripe.net> References: <200407231610.i6NGArjR022749@birch.ripe.net> Message-ID: <41013C6E.2060703@ripe.net> Rene Wilhelm wrote: >>>No, but people tend to reply to the last mail they have in their files, >>>if you use something like hm-ack at r.n it looks as if a human will read >>>it. >> >>We have an address for this, called . > > > Why does the autoresponse have to come from an unread email account? For RIPE DBM we do this to avoid mail loops (I think - Oleg knows more about these mysteries than I do). For hostmasters, the "From:" is actually . I guess it makes sense for the "From:" to be in this case. > If I were a user and needed to add info to a ticket or query it's > status, it would be most convenient if I could reply to the > first (auto)reply to my initial message, as that ensures I get the ticket > number right. > > This is how the OPS & TT-OPS ticketing systems work. > > (ok the tt ticketing system, currently doesn't autoreply, > but if it would, it would send one "From: tt-ops") -- Shane Kerr RIPE NCC From wilhelm at ripe.net Fri Jul 23 18:58:15 2004 From: wilhelm at ripe.net (Rene Wilhelm) Date: Fri, 23 Jul 2004 18:58:15 +0200 Subject: [ris-int] FW: NCC#2004073298 Re: rrc01:PEERING 8210 In-Reply-To: Message from Shane Kerr of "Fri, 23 Jul 2004 18:27:26 +0200." <41013C6E.2060703@ripe.net> Message-ID: <200407231658.i6NGwFjR004203@birch.ripe.net> >> Why does the autoresponse have to come from an unread email account? > For RIPE DBM we do this to avoid mail loops (I think - Oleg knows more about > these mysteries than I do). ah, right! loops should indeed be avoided in automated response systems, mail servers could quickly come to a grinding halt. (IIRC, NCC has had it's shares of loop problems with the hostmaster robot in the past) > For hostmasters, the "From:" is actually . I guess it > makes sense for the "From:" to be in this case. If it cannot create loops, from (or reply-to for that matter) would be great for tickets coming in to ris. -- Rene From matthew at ripe.net Fri Jul 23 20:33:56 2004 From: matthew at ripe.net (Matthew Williams) Date: Fri, 23 Jul 2004 20:33:56 +0200 Subject: [ris-int] myASn status slide for Mon's meeting Message-ID: <003a01c470e3$9dee6530$1f0200c1@rockstar> Hi Gang, Discussion fodder? ;) Cheers, Matthew -------------- next part -------------- A non-text attachment was scrubbed... Name: myASn_status_230704.png Type: image/png Size: 25463 bytes Desc: not available URL: From oleg at ripe.net Sun Jul 25 14:16:18 2004 From: oleg at ripe.net (Oleg Muravskiy) Date: Sun, 25 Jul 2004 14:16:18 +0200 Subject: [ris-int] FW: NCC#2004073298 Re: rrc01:PEERING 8210 In-Reply-To: <41013C6E.2060703@ripe.net> References: <200407231610.i6NGArjR022749@birch.ripe.net> <41013C6E.2060703@ripe.net> Message-ID: <20040725121617.GC6980@cow.ripe.net> On Fri, Jul 23, 2004 at 06:27:26PM +0200, Shane Kerr wrote: > Rene Wilhelm wrote: > >>>No, but people tend to reply to the last mail they have in their files, > >>>if you use something like hm-ack at r.n it looks as if a human will read > >>>it. > >> > >>We have an address for this, called . > > > > > >Why does the autoresponse have to come from an unread email account? This is to prevent autoreplies to our autoreplies to create new tickets and replies). For this purpose we have 2 addresses: - hm-ack, which is alias to /dev/null, i.e. deliverable black hole address. There is no much reason to use it in autoreplies, it's current use is rather "historical". I prefer to use unread or <>. - unread - this is unexisting address, so delivery to it will result in bounce from MTA. > > For RIPE DBM we do this to avoid mail loops (I think - Oleg knows more > about these mysteries than I do). > > For hostmasters, the "From:" is actually . This is for human replies, not for autoreplies, except one case - when original message contains valid request. > > I guess it makes sense for the "From:" to be in this > case. For autoreplies, I'd rather not to use such address in From:, although it could be used in Reply-To:. > > >If I were a user and needed to add info to a ticket or query it's > >status, it would be most convenient if I could reply to the > >first (auto)reply to my initial message, as that ensures I get the ticket > >number right. > > > >This is how the OPS & TT-OPS ticketing systems work. > > > >(ok the tt ticketing system, currently doesn't autoreply, > > but if it would, it would send one "From: tt-ops") > > -- > Shane Kerr > RIPE NCC -- Oleg Muravskiy Software Engineer RIPE NCC From arife at ripe.net Mon Jul 26 09:04:36 2004 From: arife at ripe.net (Arife Vural) Date: Mon, 26 Jul 2004 09:04:36 +0200 Subject: [ris-int] Re: RIS Statistics Report In-Reply-To: References: <200407260651.i6Q6p8la030265@halfweg.ripe.net> Message-ID: <20040726070436.GB11263@ripe.net> It looks I missed to update Weekly Report, I will add it. Arife On Mon, Jul 26, 2004 at 08:53:28AM +0200, Henk Uijterwaal (RIPE NCC) wrote: > > I just noticed that RRC12 is not in the table yet. > > Henk > > > On Mon, 26 Jul 2004, Generic RIS account wrote: > > > > > RIS Statistics Report (20040719-20040726) > > > > This report was generated at Mon Jul 26 00:15:01 UTC 2004. It analyses the BGP > > Routing Tables which are collected by RIS Remote Collectors at different locations > > around the world. Check http://www.ris.ripe.net/weekly-report/ for more info. > > > > o Prefix Distribution > > > > RIS rrc00 rrc01 rrc02 rrc03 rrc04 rrc05 rrc06 rrc07 rrc08 rrc10 rrc11 > > APNIC 27343 26793 26079 15703 27061 20508 26186 26433 26368 13545 25282 19216 > > ARIN 62135 61390 59038 24057 61836 58807 60725 59804 60640 9111 58800 54355 > > LACNIC 7015 5982 5959 3310 6998 5664 5983 5976 5959 1455 5930 5215 > > RIPE NCC 31065 25503 24552 14214 30629 20246 24976 24851 24651 6889 24454 19356 > > OLD 31546 30909 29342 13460 31184 27157 29943 30174 29430 6630 29076 26023 > > IANA 1733 973 889 601 1714 796 909 882 915 166 881 689 > > RFC1918 4 0 0 0 4 0 0 0 0 0 0 0 > > OTHER 0 0 0 0 0 0 0 0 0 0 0 0 > > TOTAL 160841 151550 145859 71345 159426 133178 148722 148120 147963 37796 144423 124854 > > > > > > AS number distributions wrt RIR and single-homed/multi-homed. > > > > o ASes per RIR region > > > > RIS rrc00 rrc01 rrc02 rrc03 rrc04 rrc05 rrc06 rrc07 rrc08 rrc10 rrc11 > > ARIN 10119 10078 10000 254 10076 9838 10041 10020 9999 2982 9973 9218 > > APNIC 2051 2050 2028 35 2050 1706 2038 2030 2023 1242 2020 1543 > > RIPE NCC 5725 5702 5672 2322 5715 5029 5497 5664 5625 2130 5685 4877 > > LACNIC 62 62 57 7 61 61 62 62 57 25 57 56 > > IANA 1 1 1 0 1 1 1 1 1 1 1 1 > > Private 22 10 6 3 16 2 11 3 5 2 5 6 > > Others 1 0 0 1 1 0 0 0 0 0 0 0 > > Total 17981 17903 17764 2622 17920 16637 17650 17780 17710 6382 17741 15701 > > > > > > o Number of single-homed ASes. > > > > RIS rrc00 rrc01 rrc02 rrc03 rrc04 rrc05 rrc06 rrc07 rrc08 rrc10 rrc11 > > ARIN 2948 3675 4762 160 3266 4842 4068 5892 4086 1787 4781 4348 > > APNIC 526 612 706 28 593 673 704 1134 759 610 826 687 > > RIPE NCC 1586 1973 2113 1433 1739 2079 2058 3346 2106 1199 2481 2251 > > LACNIC 30 31 30 7 30 31 32 39 28 18 31 30 > > IANA 1 1 1 0 1 1 1 1 1 1 1 1 > > Private 15 10 6 1 13 2 9 3 5 2 4 6 > > Others 0 0 0 1 0 0 0 0 0 0 0 0 > > Total 5106 6302 7618 1630 5642 7628 6872 10415 6985 3617 8124 7323 > > > > > > o Number of multi-homed ASes. > > > > RIS rrc00 rrc01 rrc02 rrc03 rrc04 rrc05 rrc06 rrc07 rrc08 rrc10 rrc11 > > ARIN 7171 6403 5238 94 6810 4996 5973 4128 5913 1195 5192 4870 > > APNIC 1525 1438 1322 7 1457 1033 1334 896 1264 632 1194 856 > > RIPE NCC 4139 3729 3559 889 3976 2950 3439 2318 3519 931 3204 2626 > > LACNIC 32 31 27 0 31 30 30 23 29 7 26 26 > > IANA 0 0 0 0 0 0 0 0 0 0 0 0 > > Private 7 0 0 2 3 0 2 0 0 0 1 0 > > Others 1 0 0 0 1 0 0 0 0 0 0 0 > > Total 12875 11601 10146 992 12278 9009 10778 7365 10725 2765 9617 8378 > > > > IANA : AS65535 > > > > Others: AS65535 > > > > Distribution of AS number wrt Leaf, Transit. > > > > RIS rrc00 rrc01 rrc02 rrc03 rrc04 rrc05 rrc06 rrc07 rrc08 rrc10 rrc11 > > Leaf 14834 14916 14872 1980 14863 13925 14701 15177 14882 4960 14967 13148 > > Transit 3041 2885 2783 440 2956 2516 2823 2515 2719 927 2681 2293 > > Transit-only 106 102 109 202 101 196 126 88 109 495 93 260 > > Total 17981 17903 17764 2622 17920 16637 17650 17780 17710 6382 17741 15701 > > > > > > o Average ASPATH length. > > > > RIS rrc00 rrc01 rrc02 rrc03 rrc04 rrc05 rrc06 rrc07 rrc08 rrc10 rrc11 > > Avg 6.14 5.91 5.94 5.68 6.13 6.01 6.23 6.12 6.43 5.89 5.85 6.04 > > Std 2.73 2.65 2.81 3.20 2.76 2.42 2.85 2.37 2.63 2.82 2.44 2.24 > > > > o List of martians appearing throughout the week. > > > > Prefix Origin AS > > 192.168.90.0/24 5417 > > 192.168.91.0/24 5417 > > 192.168.191.0/24 5417 > > > > > > o List of hot-spots during the week. > > > > Prefix Origin AS Number of updates > > 209.182.81.0/24 19071 203706 > > 209.114.254.0/24 14359 157276 > > 195.239.204.0/24 3216 134771 > > 195.218.176.0/24 3216 132598 > > 139.91.40.0/24 8522 121002 > > 139.91.252.0/24 8522 110100 > > 202.140.156.0/22 9910 80133 > > 209.205.84.0/24 15066 73047 > > 209.205.81.0/24 15066 73044 > > 194.133.184.0/21 0 67260 > > > > > > Total number of RIS BGP peering sessions: 416 > > > > ------------------------------------------------------------------------------ > 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 > ------------------------------------------------------------------------------ > > Process and Procedure are the last hiding place of people without the wit > and wisdom to do their job properly. (David Brent). From alexis at ripe.net Mon Jul 26 13:40:06 2004 From: alexis at ripe.net (Alexis Yushin) Date: Mon, 26 Jul 2004 13:40:06 +0200 (CEST) Subject: [ris-int] myASn status slide for Mon's meeting In-Reply-To: <003a01c470e3$9dee6530$1f0200c1@rockstar> from "Matthew Williams" at Jul 23, 2004 08:33:56 PM Message-ID: <200407261140.i6QBe6lh029490@birch.ripe.net> Hello, Sorry for having disappeared - I just got back to Amsterdam, got stuff stolen in Nijmegen on Thursday, my mobile telephone is gone as well and my notebook I still have to pick up in Venlo :-( (Fortunately its not gone for good). If you need to reach me by phone its 020 670 7748 (my home number). I'm going to read my email now. Alexis From arife at ripe.net Mon Jul 26 13:46:52 2004 From: arife at ripe.net (Arife Vural) Date: Mon, 26 Jul 2004 13:46:52 +0200 Subject: [ris-int] myASn status slide for Mon's meeting In-Reply-To: <200407261140.i6QBe6lh029490@birch.ripe.net> References: <003a01c470e3$9dee6530$1f0200c1@rockstar> <200407261140.i6QBe6lh029490@birch.ripe.net> Message-ID: <20040726114652.GD11263@ripe.net> Hi Alexis, Me and Ziya like to sit down with you and do the handover on Wed afternoon, at 14.00. Is that OK with you? Arife > Hello, > > Sorry for having disappeared - I just got back to Amsterdam, got stuff > stolen in Nijmegen on Thursday, my mobile telephone is gone as well and > my notebook I still have to pick up in Venlo :-( (Fortunately its not > gone for good). > > If you need to reach me by phone its 020 670 7748 (my home number). > > I'm going to read my email now. > > Alexis From alexis at ripe.net Mon Jul 26 14:00:16 2004 From: alexis at ripe.net (Alexis Yushin) Date: Mon, 26 Jul 2004 14:00:16 +0200 (CEST) Subject: [ris-int] myASn status slide for Mon's meeting In-Reply-To: <20040726114652.GD11263@ripe.net> from "Arife Vural" at Jul 26, 2004 01:46:52 PM Message-ID: <200407261200.i6QC0Glc002626@birch.ripe.net> Once Arife Vural wrote: >Hi Alexis, > >Me and Ziya like to sit down with you and do the handover on Wed >afternoon, at 14.00. > >Is that OK with you? Yes, that's no problem. I can come to the office Wednessday morning to have a chat with Matthew. Alexis From arife at ripe.net Mon Jul 26 14:03:48 2004 From: arife at ripe.net (Arife Vural) Date: Mon, 26 Jul 2004 14:03:48 +0200 Subject: [ris-int] myASn status slide for Mon's meeting In-Reply-To: <200407261200.i6QC0Glc002626@birch.ripe.net> References: <20040726114652.GD11263@ripe.net> <200407261200.i6QC0Glc002626@birch.ripe.net> Message-ID: <20040726120347.GI11263@ripe.net> On Mon, Jul 26, 2004 at 02:00:16PM +0200, Alexis Yushin wrote: > Once Arife Vural wrote: > >Hi Alexis, > > > >Me and Ziya like to sit down with you and do the handover on Wed > >afternoon, at 14.00. > > > >Is that OK with you? > > Yes, that's no problem. I can come to the office Wednessday morning > to have a chat with Matthew. OK, I will shcedule smth on Ctime. Arife > > Alexis From henk at ripe.net Mon Jul 26 16:03:41 2004 From: henk at ripe.net (Henk Uijterwaal (RIPE NCC)) Date: Mon, 26 Jul 2004 16:03:41 +0200 (CEST) Subject: [ris-int] RIS work items Message-ID: Hi all, (By popular request in ASCII). Here is the list of to-do-items that are still open in the RIS move. All items that were completed (=80 to 90% of the work) are not on the list. Henk - - - - Integration with OPS (98% done) - Software Sync for RRC01-13 Few hours Bruce Procedures - Maintain operations draft Sep-Dec'04 Arife (background task) Routing Training - Stalled, looking for trainer. Ongoing work - MyASN handover 28/7 Matthew/Arife/Alexis/SED - MyASN documentation Now-R49 Matthew - RRC installation UAE ?? Matthew, Henk Integration with SED - Move III pages out of NP area 1 day Arife/James/Katie/Engin - Review docs on iii 1 week Arife/James/Katie/Engin Software move - Document existing software 4 weeks (50% done) Arife, James - Review documentation 2 weeks Engin, Katie - Prtraceroute with RISwhois 11/2004, 1 wk Katie - Maintain documents All Research Issues - Analysis of Beacon Data Fall'2004 Arife, Henk - BGP Stability Index Fall'2004 James - Website restructuring Summer Matthew, 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 ------------------------------------------------------------------------------ Process and Procedure are the last hiding place of people without the wit and wisdom to do their job properly. (David Brent). From matthew at ripe.net Tue Jul 27 03:00:08 2004 From: matthew at ripe.net (Matthew Williams) Date: Tue, 27 Jul 2004 03:00:08 +0200 Subject: [ris-int] RE: Fwd: Re: FW: [ripe.net #101517] R: please adrian bedford to the projects group In-Reply-To: Message-ID: <003901c47375$0fab02d0$aaa8a8c0@rockstar> Hi Henk, I decided to CTC* and play around with some text on my own: http://www.ripe.net/ris/risintro.html Will this do? Basic stuff... Feedback welcome though :) Cheers, Matthew *) VoS only ;) > -----Original Message----- > From: Henk Uijterwaal via RT [mailto:ops at ripe.net] > Sent: 26 July 2004 16:28 > To: matthew at ripe.net > Subject: Re: Fwd: Re: FW: [ripe.net #101517] R: please adrian > bedford to the projects group > > > Hi, > > > Otherwise add webmaster to np and/or tt groups. > > That won't allow you to edit RIS files :-) > > Seriously, there is a ris group for RIS, the ris is run by > different department these days, so simply putting the > webmaster in the RIS group and changing ownership of the > files, should solve the problem. > > 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 > -------------------------------------------------------------- > ---------------- > > Process and Procedure are the last hiding place of people > without the wit > and wisdom to do their job properly. > (David Brent). > From shane at ripe.net Tue Jul 27 10:15:44 2004 From: shane at ripe.net (Shane Kerr) Date: Tue, 27 Jul 2004 10:15:44 +0200 Subject: [ris-int] RE: Fwd: Re: FW: [ripe.net #101517] R: please adrian bedford to the projects group In-Reply-To: <003901c47375$0fab02d0$aaa8a8c0@rockstar> References: <003901c47375$0fab02d0$aaa8a8c0@rockstar> Message-ID: <41060F30.7090602@ripe.net> Matthew, We're working with Jeroen on updating the RIS pages for the new web server now, and I'd prefer not to have multiple people working on the site. What is the basic idea and/or scope behind this risintro page? Matthew Williams wrote: > Hi Henk, > > I decided to CTC* and play around with some text on my own: http://www.ripe.net/ris/risintro.html > > Will this do? Basic stuff... Feedback welcome though :) > > Cheers, > Matthew > > *) VoS only ;) > > >>-----Original Message----- >>From: Henk Uijterwaal via RT [mailto:ops at ripe.net] >>Sent: 26 July 2004 16:28 >>To: matthew at ripe.net >>Subject: Re: Fwd: Re: FW: [ripe.net #101517] R: please adrian >>bedford to the projects group >> >> >>Hi, >> >> >>>Otherwise add webmaster to np and/or tt groups. >> >>That won't allow you to edit RIS files :-) >> >>Seriously, there is a ris group for RIS, the ris is run by >>different department these days, so simply putting the >>webmaster in the RIS group and changing ownership of the >>files, should solve the problem. >> >>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 >>-------------------------------------------------------------- >>---------------- >> >>Process and Procedure are the last hiding place of people >>without the wit >>and wisdom to do their job properly. >>(David Brent). >> -- Shane Kerr RIPE NCC From henk at ripe.net Tue Jul 27 10:29:48 2004 From: henk at ripe.net (Henk Uijterwaal (RIPE NCC)) Date: Tue, 27 Jul 2004 10:29:48 +0200 (CEST) Subject: [ris-int] RE: Fwd: Re: FW: [ripe.net #101517] R: please adrian bedford to the projects group In-Reply-To: <41060F30.7090602@ripe.net> References: <003901c47375$0fab02d0$aaa8a8c0@rockstar> <41060F30.7090602@ripe.net> Message-ID: On Tue, 27 Jul 2004, Shane Kerr wrote: > Matthew, > > We're working with Jeroen on updating the RIS pages for the new web server > now, and I'd prefer not to have multiple people working on the site. > > What is the basic idea and/or scope behind this risintro page? This came up when the announcement for rrc12 was put online. The text there assumes that one knows what the RIS is. Somebody then suggested to have a short 1 page intro to the RIS for people who get the announcement but haven't heard of the project. Henk > > Matthew Williams wrote: > > Hi Henk, > > > > I decided to CTC* and play around with some text on my own: http://www.ripe.net/ris/risintro.html > > > > Will this do? Basic stuff... Feedback welcome though :) > > > > Cheers, > > Matthew > > > > *) VoS only ;) > > > > > >>-----Original Message----- > >>From: Henk Uijterwaal via RT [mailto:ops at ripe.net] > >>Sent: 26 July 2004 16:28 > >>To: matthew at ripe.net > >>Subject: Re: Fwd: Re: FW: [ripe.net #101517] R: please adrian > >>bedford to the projects group > >> > >> > >>Hi, > >> > >> > >>>Otherwise add webmaster to np and/or tt groups. > >> > >>That won't allow you to edit RIS files :-) > >> > >>Seriously, there is a ris group for RIS, the ris is run by > >>different department these days, so simply putting the > >>webmaster in the RIS group and changing ownership of the > >>files, should solve the problem. > >> > >>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 > >>-------------------------------------------------------------- > >>---------------- > >> > >>Process and Procedure are the last hiding place of people > >>without the wit > >>and wisdom to do their job properly. > >>(David Brent). > >> > > > -- > Shane Kerr > RIPE NCC > ------------------------------------------------------------------------------ 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 ------------------------------------------------------------------------------ Process and Procedure are the last hiding place of people without the wit and wisdom to do their job properly. (David Brent). From shane at ripe.net Tue Jul 27 10:41:31 2004 From: shane at ripe.net (Shane Kerr) Date: Tue, 27 Jul 2004 10:41:31 +0200 Subject: [ris-int] RE: Fwd: Re: FW: [ripe.net #101517] R: please adrian bedford to the projects group In-Reply-To: References: <003901c47375$0fab02d0$aaa8a8c0@rockstar> <41060F30.7090602@ripe.net> Message-ID: <4106153B.8060503@ripe.net> Henk Uijterwaal (RIPE NCC) wrote: > On Tue, 27 Jul 2004, Shane Kerr wrote: > > >>Matthew, >> >>We're working with Jeroen on updating the RIS pages for the new web server >>now, and I'd prefer not to have multiple people working on the site. >> >>What is the basic idea and/or scope behind this risintro page? > > > This came up when the announcement for rrc12 was put online. The text > there assumes that one knows what the RIS is. Somebody then suggested to > have a short 1 page intro to the RIS for people who get the announcement > but haven't heard of the project. While that makes some sense, I think we can safely assume that a lot of people who come to the RIS pages don't know what the project is - yet! ;) I'd rather have the main RIS page be a gentle introduction, with links to details. The new web page layout actually lends itself very nicely to this setup. Matthew, maybe you can stop by the SED room for a quick chat with Arife and me so we can co-ordinate revisions to the RIS pages? -- Shane Kerr RIPE NCC From henk at ripe.net Tue Jul 27 10:50:23 2004 From: henk at ripe.net (Henk Uijterwaal (RIPE NCC)) Date: Tue, 27 Jul 2004 10:50:23 +0200 (CEST) Subject: [ris-int] RE: Fwd: Re: FW: [ripe.net #101517] R: please adrian bedford to the projects group In-Reply-To: <003901c47375$0fab02d0$aaa8a8c0@rockstar> References: <003901c47375$0fab02d0$aaa8a8c0@rockstar> Message-ID: On Tue, 27 Jul 2004, Matthew Williams wrote: > Hi Henk, > > I decided to CTC* and play around with some text on my own: http://www.ripe.net/ris/risintro.html > > Will this do? Basic stuff... Feedback welcome though :) Looks fine to me though, as a quick attempt to support the announcement that is up there now. Henk > > Cheers, > Matthew > > *) VoS only ;) > > > -----Original Message----- > > From: Henk Uijterwaal via RT [mailto:ops at ripe.net] > > Sent: 26 July 2004 16:28 > > To: matthew at ripe.net > > Subject: Re: Fwd: Re: FW: [ripe.net #101517] R: please adrian > > bedford to the projects group > > > > > > Hi, > > > > > Otherwise add webmaster to np and/or tt groups. > > > > That won't allow you to edit RIS files :-) > > > > Seriously, there is a ris group for RIS, the ris is run by > > different department these days, so simply putting the > > webmaster in the RIS group and changing ownership of the > > files, should solve the problem. > > > > 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 > > -------------------------------------------------------------- > > ---------------- > > > > Process and Procedure are the last hiding place of people > > without the wit > > and wisdom to do their job properly. > > (David Brent). > > > ------------------------------------------------------------------------------ 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 ------------------------------------------------------------------------------ Process and Procedure are the last hiding place of people without the wit and wisdom to do their job properly. (David Brent). From shane at ripe.net Tue Jul 27 10:58:17 2004 From: shane at ripe.net (Shane Kerr) Date: Tue, 27 Jul 2004 10:58:17 +0200 Subject: [ris-int] RE: Fwd: Re: FW: [ripe.net #101517] R: please adrian bedford to the projects group In-Reply-To: References: <003901c47375$0fab02d0$aaa8a8c0@rockstar> Message-ID: <41061929.2020406@ripe.net> Henk Uijterwaal (RIPE NCC) wrote: > On Tue, 27 Jul 2004, Matthew Williams wrote: > > >>Hi Henk, >> >>I decided to CTC* and play around with some text on my own: http://www.ripe.net/ris/risintro.html >> >>Will this do? Basic stuff... Feedback welcome though :) > > > Looks fine to me though, as a quick attempt to support the announcement > that is up there now. Agreed. -- Shane Kerr RIPE NCC From matthew at ripe.net Tue Jul 27 12:06:35 2004 From: matthew at ripe.net (Matthew Williams) Date: Tue, 27 Jul 2004 12:06:35 +0200 Subject: [ris-int] RE: Fwd: Re: FW: [ripe.net #101517] R: please adrian bedford to the projects group In-Reply-To: <4106153B.8060503@ripe.net> Message-ID: <000601c473c1$667da850$aaa8a8c0@rockstar> > Matthew, maybe you can stop by the SED room for a quick chat > with Arife and > me so we can co-ordinate revisions to the RIS pages? Please set something up in ctime. Cheers, Matthew > -----Original Message----- > From: Shane Kerr [mailto:shane at ripe.net] > Sent: 27 July 2004 10:42 > To: Henk Uijterwaal (RIPE NCC) > Cc: Matthew Williams; ris-int at ripe.net > Subject: Re: [ris-int] RE: Fwd: Re: FW: [ripe.net #101517] R: > please adrian bedford to the projects group > > > Henk Uijterwaal (RIPE NCC) wrote: > > On Tue, 27 Jul 2004, Shane Kerr wrote: > > > > > >>Matthew, > >> > >>We're working with Jeroen on updating the RIS pages for the new web > >>server now, and I'd prefer not to have multiple people > working on the > >>site. > >> > >>What is the basic idea and/or scope behind this risintro page? > > > > > > This came up when the announcement for rrc12 was put > online. The text > > there assumes that one knows what the RIS is. Somebody then > suggested > > to have a short 1 page intro to the RIS for people who get the > > announcement but haven't heard of the project. > > While that makes some sense, I think we can safely assume > that a lot of > people who come to the RIS pages don't know what the project > is - yet! ;) > I'd rather have the main RIS page be a gentle introduction, > with links to > details. The new web page layout actually lends itself very > nicely to this > setup. > > Matthew, maybe you can stop by the SED room for a quick chat > with Arife and > me so we can co-ordinate revisions to the RIS pages? > > -- > Shane Kerr > RIPE NCC > From matthew at ripe.net Tue Jul 27 12:21:32 2004 From: matthew at ripe.net (Matthew Williams) Date: Tue, 27 Jul 2004 12:21:32 +0200 Subject: [ris-int] RE: Fwd: Re: FW: [ripe.net #101517] R: please adrian bedford to the projects group In-Reply-To: <41061929.2020406@ripe.net> Message-ID: <000801c473c3$7cc4b660$aaa8a8c0@rockstar> Hi Shane, Yup, it would be good to coordinate stuff with AV. I think we can conclude that there is a certain degree of overlap between promotional activities and the revised www pages. Cheers, Matthew > -----Original Message----- > From: Shane Kerr [mailto:shane at ripe.net] > Sent: 27 July 2004 10:58 > To: Henk Uijterwaal (RIPE NCC) > Cc: Matthew Williams; 'Henk Uijterwaal'; ris-int at ripe.net > Subject: Re: [ris-int] RE: Fwd: Re: FW: [ripe.net #101517] R: > please adrian bedford to the projects group > > > Henk Uijterwaal (RIPE NCC) wrote: > > On Tue, 27 Jul 2004, Matthew Williams wrote: > > > > > >>Hi Henk, > >> > >>I decided to CTC* and play around with some text on my own: > >>http://www.ripe.net/ris/risintro.html > >> > >>Will this do? Basic stuff... Feedback welcome though :) > > > > > > Looks fine to me though, as a quick attempt to support the > > announcement that is up there now. > > Agreed. > > -- > Shane Kerr > RIPE NCC > From wilhelm at ripe.net Tue Jul 27 13:49:52 2004 From: wilhelm at ripe.net (Rene Wilhelm) Date: Tue, 27 Jul 2004 13:49:52 +0200 Subject: [ris-int] RE: Fwd: Re: FW: [ripe.net #101517] R: please adrian bedford to the projects group In-Reply-To: Message from "Henk Uijterwaal (RIPE NCC)" of "Tue, 27 Jul 2004 10:29:48 +0200." Message-ID: <200407271149.i6RBnq1o020158@birch.ripe.net> > > Matthew, > > > > We're working with Jeroen on updating the RIS pages for the new web server > > now, and I'd prefer not to have multiple people working on the site. > > > > What is the basic idea and/or scope behind this risintro page? > > This came up when the announcement for rrc12 was put online. The text > there assumes that one knows what the RIS is. Somebody then suggested to > have a short 1 page intro to the RIS for people who get the announcement > but haven't heard of the project. Linking the news flash on www to the risintro page is fine with me, better than diving immediately to the RRC12 specific page, but to set the record straight, all I suggested was to have a page with text similar to the announcement that was send out to the ris-users mailing list. Visitors to www.ripe.net see a news flash "Route Collector deployed at xyz-IX" and when they want to read more on this, the link should bring them to a page with relevant information. (which, next to details on deployement at the specific location, could have some words on RIS in general too). As such a page can easily be reused when a next RRC comes online, maybe it's an idea to design some template in the context of the current RIS pages restructuring work? Cheers, -- Rene P.S. All this was triggered by an external user pointing out to me the date on the announcement at www.ripe.net was wrong :) From webmaster at ripe.net Tue Jul 27 14:51:51 2004 From: webmaster at ripe.net (RIPE NCC Webmaster) Date: Tue, 27 Jul 2004 14:51:51 +0200 Subject: [ris-int] RE: Fwd: Re: FW: [ripe.net #101517] R: please adrian bedford to the projects group In-Reply-To: Your message of Tue, 27 Jul 2004 13:49:52 +0200. <200407271149.i6RBnq1o020158@birch.ripe.net> References: <200407271149.i6RBnq1o020158@birch.ripe.net> Message-ID: <200407271251.i6RCpp1o008255@birch.ripe.net> Hi, Rene Wilhelm writes: * * > > Matthew, * > > * > > We're working with Jeroen on updating the RIS pages for the new web server * > > now, and I'd prefer not to have multiple people working on the site. * > > * > > What is the basic idea and/or scope behind this risintro page? * > * > This came up when the announcement for rrc12 was put online. The text * > there assumes that one knows what the RIS is. Somebody then suggested to * > have a short 1 page intro to the RIS for people who get the announcement * > but haven't heard of the project. * * Linking the news flash on www to the risintro page is fine with me, * better than diving immediately to the RRC12 specific page, but to set * the record straight, all I suggested was to have a page with text similar * to the announcement that was send out to the ris-users mailing list. * * Visitors to www.ripe.net see a news flash "Route Collector deployed at xyz-IX" * and when they want to read more on this, the link should bring them to a page * with relevant information. (which, next to details on deployement at the * specific location, could have some words on RIS in general too). * * As such a page can easily be reused when a next RRC comes online, * maybe it's an idea to design some template in the context of the current * RIS pages restructuring work? * The page that Matthew came up with is good as an 'about-ris' page. Adrian kindly revised it a little so maybe you can use the following: =================================================================== The Routing Information Service (RIS) started as a RIPE NCC project in 1999. Currently there are over 300 IPv4 and IPv6 peers at 12 data collection points in Europe, Japan and North America The project aims to collect and store Border Gateway Protocol (BGP) routing information and make it publicly available for the Internet community. Network operators can troubleshoot routing problems by looking at data collected over time without being limited to a single BGP view. Archived raw RIS data is also available, which can be used for research purposes. You can improve the RIS by providing a BGP feed. You can find a list of RIS peering locations at: http://www.ris.ripe.net/cgi-bin/rrcstatus.cgi Peering requests can be sent to or through a web form, you can find at: http://www.ris.ripe.net/cgi-bin/peerreg.cgi ============================================================ I agree with Rene that we can just copy the announcement for the link page. -J * Cheers, * * -- Rene * * P.S. All this was triggered by an external user pointing out to me * the date on the announcement at www.ripe.net was wrong :) * From matthew at ripe.net Tue Jul 27 15:17:43 2004 From: matthew at ripe.net (Matthew Williams) Date: Tue, 27 Jul 2004 15:17:43 +0200 Subject: [ris-int] RE: Fwd: Re: FW: [ripe.net #101517] R: please adrian bedford to the projects group In-Reply-To: <200407271251.i6RCpp1o008255@birch.ripe.net> Message-ID: <000601c473dc$19ecb880$1f0200c1@rockstar> Hi Webbies, After a quick cha(n)t with AV and SK, I made some modifications. Please check. ==>Comments below. > > The page that Matthew came up with is good as an 'about-ris' > page. Adrian kindly revised it a little so maybe you can use the > following: > > =================================================================== > > The Routing Information Service (RIS) started as a RIPE NCC > project in > 1999. Currently there are over 300 IPv4 and IPv6 peers at 12 data > collection points in Europe, Japan and North America > > The project aims to collect and store Border Gateway Protocol > (BGP) routing > information and make it publicly available for the Internet > community. > Network operators can troubleshoot routing problems by > looking at data > collected over time without being limited to a single BGP > view. Archived > raw RIS data is also available, which can be used for ==>"Can" is ambiguous. It is always/mainly used for research. I haven't heard of anyone (directly) using RIS raw data to debug route probs in their NW. > research purposes. > > You can improve the RIS by providing a BGP feed. You can find ==>"Improve" is wrong. > a list of RIS > peering locations at: > http://www.ris.ripe.net/cgi-bin/rrcstatus.cgi Peering requests can be sent to or through a web form, you can find at: http://www.ris.ripe.net/cgi-bin/peerreg.cgi ============================================================ => Rest is fine, meaning I don't want to hear anything more about it ;) If Adrian wants instructions, then he's welcome to call 405 in 15 mins. Cheers, Matthew From matthew at ripe.net Tue Jul 27 17:42:42 2004 From: matthew at ripe.net (Matthew Williams) Date: Tue, 27 Jul 2004 17:42:42 +0200 Subject: [ris-int] O: I need James or Bruce to come up with specs for PowerEdge 1750 intended as RRC13 at MSK-IX Message-ID: <200407271542.i6RFgg1o001031@birch.ripe.net> Hereby I wish to notify Operations of something uncategorised. Detailed description: --------------------- Pls see subline Cheers, Matthew Regards, Matthew Williams From matthew at ripe.net Wed Jul 28 14:05:58 2004 From: matthew at ripe.net (Matthew Williams) Date: Wed, 28 Jul 2004 14:05:58 +0200 Subject: [ris-int] myASn - Last check list Message-ID: <001c01c4749b$3e67f610$1f0200c1@rockstar> Fix errors, addtional features no in wp4. /Matthew - minED - minEC - ADW ++++ Clean out manual/auto - set dbase clean out time in alarm gr page ++++ You'll send email w/ xml example, import/export ++++ Optional: Experimental retromatch (not in wp4!) ++++ Breadcrumbs - Help ++++ Emails - change HDT, HDE, TTL ++++ Customer alarm - alarm 742 - no asns Customer alarm 742 (Default), 217.145.48.0/20 (exceptions not shown), MyASn: , Their ASn: , HDT: 60, HDE: 1, TTL: 3600 .=------+-----------------+--------------+--------------------------+-------------------------=. | RRC | Prefix | Peer | First Seen | Last Seen | |=------+-----------------+--------------+--------------------------+--- |----------------------=| | rrc10 | 217.145.48.0/20 | 217.29.66.65 | Wed Jul 7 02:02:01 2004 | Wed Jul 7 02:02:01 2004 | '=------+-----------------+--------------+--------------------------+-------------------------=' ++++ Add rrc12, tell SED about myasn.conf ++++ Remove alarms in uk.bt account ++++ Delete _all_ alarms in alarm groups ++++ Error handling when importing xml, cancel, fix error, try again --- > Matthew Williams (MW243-RIPE) > Customer Liaison Engineer > RIPE NCC - http://www.ripe.net/np/ From matthew at ripe.net Wed Jul 28 14:56:38 2004 From: matthew at ripe.net (Matthew Williams) Date: Wed, 28 Jul 2004 14:56:38 +0200 Subject: [ris-int] Three things... Message-ID: <002001c474a2$522de540$1f0200c1@rockstar> Hi Dave, 1. Flashing RIS (~we need peers etc etc) in K-anycast peering ack (SED do RIS peering reqs) 2. myASn accounts (also by SED in the future) sync w/ K-anycast peering requests (monitor no-export compliance) 3. When will you announce me to contacts ? ;) Cheers, Matthew --- > Matthew Williams (MW243-RIPE) > Customer Liaison Engineer > RIPE NCC - http://www.ripe.net/np/ From dknight at ripe.net Wed Jul 28 15:27:13 2004 From: dknight at ripe.net (Dave Knight) Date: Wed, 28 Jul 2004 15:27:13 +0200 Subject: [ris-int] Re: Three things... In-Reply-To: <002001c474a2$522de540$1f0200c1@rockstar> Message-ID: <5.2.1.1.2.20040728152220.0266e488@mailhost.ripe.net> Hi Matthew, At 14:56 28/07/2004 +0200, Matthew Williams wrote: >Hi Dave, > >1. Flashing RIS (~we need peers etc etc) in K-anycast peering ack (SED do >RIS peering reqs) We can do that. We can add your blurb to the bottom of: /home/kroot/doc/peer-info Let me know what you want to put there. I intend to do some work on making peerings management easier for RIPENCC,RIS,KROOT,AS112 following RIPE49. I will no doubt call a meeting when this gets started to look at everyones requirements before taking this to SED. >2. myASn accounts (also by SED in the future) sync w/ K-anycast peering >requests (monitor no-export compliance) I have been ignoring myASn stuff at the moment. We don't have time to do anything with it before RIPE49. I look forward to spending some time getting it all sorted shortly thereafter though :) When is it planned that the current development effort ends and goes into production? >3. When will you announce me to contacts ? ;) Heh, almost there. I have been getting all status up to date and reorganising things on the iii pages. I will shortly get to announcing you .. honest :) Cheers, dave From james at ripe.net Wed Jul 28 16:20:43 2004 From: james at ripe.net (James Aldridge) Date: Wed, 28 Jul 2004 16:20:43 +0200 Subject: [ris-int] Draft minutes from Monday's RIS meeting (apologies for the delay) Message-ID: <200407281420.i6SEKh1o022363@birch.ripe.net> RIS Meeting - 26 July 2004 Present: Matthew, Shane, Arife, James, Bruce, Ruud, Henk, Vasco Scribe: James Agenda: - RRC Status - RRC Moves/New RRCs - myASn - AOB RRC Status Q. Are there any existing tools to monitor BGP sessions? A. Not that are directly relevent to the RIS. The current tools compare BGP sessions against the registered peering policy (the AS3333 aut-num object). What to monitor? - percentage of peers up/down? - peer down for a "long time"? Should there be automatic or manual notification of peers when a session is down? Who to contact at peers? - We mostly use the IRR (RIPE, etc. databases) - encourage peers to keep their own information up to date - Current "addpeer" script records contact information in a log file - need to keep our own information up to date - useful for historical data (e.g. who was the responsible person at the peer when the peering was first established, etc.) Action: monitor peering sessions in Nagios (OPS) peering sessions which are neither up nor administratively disabled should generate alerts. Action: document procedure for handling peering sessions which are down. (SED) 1. Nagios notifies SED, SED contacts peer 2. After two weeks (?), session is administrively disabled ("neighbor ... shutdown"), (peer is contacted?) 3. After a peering session is down for a further period with no response from the peer then the peering is removed from the RRC ("no neighbor ...") RRC Moves/New RRCs * RRC08 (MAE West) has very few peers and more networks are pulling out of MAE West. We need to investigate alternative locations for a route collector on the US West Coast - PAIX - Seattle - LAIIX (Telehouse) - ... Action: compare member lists of each West Coast exchange point (Matthew) How to move RRC? Simply get MCI to ship box to new location (or wait for NCC staff to be in the vicinity of San Jose). * RRC06 (DIX-IE (NSPIXP2), Japan) - Not getting any new peerings. Action: Contact George Michaelson (APNIC). Henk and Shane will be at IETF and can meet up with him there. * RRC13 (new RRC in Moscow) - Matthew has been in touch with RIPN (Russian Institute for Public Networks). - To simplify customs issues, it may be better for the host organisation to order machine to our specification (see below) directly from Dell in Russia. We would want to see the quote before agreeing to the purchase. - We need to know the IP configuration for the box so we can configure and ship the installation CD once the box is ordered. - Recent RRCs have been specified as: Dell PowerEdge 1750 (1U server) 1 GByte RAM 3 x 73 GByte Disk (configured as RAID5) 2.4 GHz Xeon CPU myASn Meeting with Alexis last week didn't happen (Alexis out of town?) Action: contact Alexis to set up meeting (Arife) Matthew's slide "On the road to myASn v.1": - Automate account creation - bring together AS3333/K-Root/RIS peering setup and myASn account creation - For each peering confirmation, the peer should be made aware of the other RIPE NCC peering opportunities, etc. where appropriate. Action: Check with Dave Knight what, if anything, is mentioned about other NCC services when K-Root peering is established (Bruce) - Would be easier if all NCC peerings were handled by the same group. - K-Root peerings are more restrictive than RIS peerings. AOB RIPE49 (Manchester) RIS Update presentation myASn Tutorial Action: Speak to Shane and get back to Matthew et al. (Arife) [Shane had already left the meeting at this point] Inventory Ruud asks for Dell Service Tags for each RRC to add to the inventory. Ops Interaction Reminder to use as first point of contact instead of sending email to Bruce/James directly. From arife at ripe.net Wed Jul 28 17:06:31 2004 From: arife at ripe.net (Arife Vural) Date: Wed, 28 Jul 2004 17:06:31 +0200 Subject: [ris-int] myASN handover meeting Message-ID: <20040728150631.GK24006@ripe.net> Hi all, This is the summary of our meeting today: - Alexis will prepare the system maintenance documentation. This doc will include the following items, - User management, put e-mail template of user request - How to installation of myASN - Adding new RRC - Log files - Deamons that are running Alexis will get back to Ziya and Arife today about timeline, after his talk with Henk and Matthew. - Developers documentation will be written by Alexis and Ziya. It's a half-day work. This will be scheduled after system maintenance doc is ready. - Arife will look at the myASN SQLs, all in myasn-scan code. Beyond those issues, today Alexis gave Ziya and me introduction to myASN code, and also we created the master copy of the source and put into CVS. Arife From arife at ripe.net Wed Jul 28 17:45:08 2004 From: arife at ripe.net (Arife Vural) Date: Wed, 28 Jul 2004 17:45:08 +0200 Subject: [arife@ripe.net: [ris-int] myASN handover meeting] Message-ID: <20040728154508.GO24006@ripe.net> Alexis, Could you also add which modules are required for myASN in system maintenance doc? Just remembered. Arife ----- Forwarded message from Arife Vural ----- From: Arife Vural To: Matthew Williams , Ziya Suzen , Alexis Yushin Subject: [ris-int] myASN handover meeting Date: Wed, 28 Jul 2004 17:06:31 +0200 Cc: ris-int at ripe.net Hi all, This is the summary of our meeting today: - Alexis will prepare the system maintenance documentation. This doc will include the following items, - User management, put e-mail template of user request - How to installation of myASN - Adding new RRC - Log files - Deamons that are running Alexis will get back to Ziya and Arife today about timeline, after his talk with Henk and Matthew. - Developers documentation will be written by Alexis and Ziya. It's a half-day work. This will be scheduled after system maintenance doc is ready. - Arife will look at the myASN SQLs, all in myasn-scan code. Beyond those issues, today Alexis gave Ziya and me introduction to myASN code, and also we created the master copy of the source and put into CVS. Arife ----- End forwarded message ----- From arife at ripe.net Wed Jul 28 17:54:31 2004 From: arife at ripe.net (Arife Vural) Date: Wed, 28 Jul 2004 17:54:31 +0200 Subject: [arife@ripe.net: [ris-int] myASN handover meeting] In-Reply-To: <200407281551.i6SFp5e1009956@birch.ripe.net> References: <20040728154508.GO24006@ripe.net> <200407281551.i6SFp5e1009956@birch.ripe.net> Message-ID: <20040728155431.GP24006@ripe.net> > >Could you also add which modules are required for myASN in system > >maintenance doc? Just remembered. > > Uff... if i knew ;) Isnt it just find myasn -type f | xargs grep '^use' ?? Probably, but it's nice to put in the doc. Arife From matthew at ripe.net Wed Jul 28 18:16:08 2004 From: matthew at ripe.net (Matthew Williams) Date: Wed, 28 Jul 2004 18:16:08 +0200 Subject: [ris-int] RE: Three things... In-Reply-To: <5.2.1.1.2.20040728152220.0266e488@mailhost.ripe.net> Message-ID: <002801c474be$30dcc700$1f0200c1@rockstar> Hi Dave, See below: > > > >1. Flashing RIS (~we need peers etc etc) in K-anycast > peering ack (SED > >do > >RIS peering reqs) > > We can do that. We can add your blurb to the bottom of: > /home/kroot/doc/peer-info Let me know what you want to put there. > Something like this? Or is it too much? +++ DNS Monitoring (dnsmon) & Test Traffic Measurements (TTM) --------------------------------------------------------- - Home Page: http://dnsmon.ripe.net/ - Server View: http://dnsmon.ripe.net/dns-servmon/server/ - TTM General Information: http://www.ripe.net/ttm/ Routing Information Service (RIS) --------------------------------- - myASn beta: http://www.ris.ripe.net/myasn.html - Other Tools: http://www.ripe.net/ris/query.html - RIS General Information: http://www.ripe.net/ris/ You can support the RIS by donating a BGP feed. For a list of peering locations, see URL: http://www.ris.ripe.net/cgi-bin/rrcstatus.cgi Please send your peering request to rispeering at ripe.net. +++ > I intend to do some work on making peerings management easier for > RIPENCC,RIS,KROOT,AS112 Good move. As you know, SED will handle peering requests for the RIS. There should possibly be more coordination, especially RIS/myASn and K. > following RIPE49. I will no doubt call a meeting when this > gets started to > look at everyones > requirements before taking this to SED. > > >2. myASn accounts (also by SED in the future) sync w/ > K-anycast peering > >requests (monitor no-export compliance) > > I have been ignoring myASn stuff at the moment. We don't have > time to do anything with it before RIPE49. I look forward to > spending some time getting it all sorted shortly thereafter though :) > > When is it planned that the current development effort ends > and goes into production? SED will take over v.1 of myASn by the second week in Aug. I'd say announcement time would be around 1st of Sept, well before R49, but that's ultimately SED's call. > > >3. When will you announce me to contacts ? ;) > > Heh, almost there. I have been getting all status up to date > and reorganising things on the iii pages. I will shortly get > to announcing you .. honest :) Okay, just bug when you need me. I'll monitor mail exchanges as much as I can. Cheers, Matthew > > Cheers, > dave > From matthew at ripe.net Wed Jul 28 18:25:23 2004 From: matthew at ripe.net (Matthew Williams) Date: Wed, 28 Jul 2004 18:25:23 +0200 Subject: FW: [ris-int] Draft minutes from Monday's RIS meeting (apologies for the delay) Message-ID: <002a01c474bf$7b9b7e20$1f0200c1@rockstar> Hi James, > - Recent RRCs have been specified as: > > Dell PowerEdge 1750 (1U server) > 1 GByte RAM > 3 x 73 GByte Disk (configured as RAID5) > 2.4 GHz Xeon CPU Please send me a spec from Dell's web site that's intelligible for MSK-IX folk (should also give us an estimate on price excl BTW). Cheers Matthew > -----Original Message----- > From: ris-int-admin at ripe.net [mailto:ris-int-admin at ripe.net] > On Behalf Of James Aldridge > Sent: 28 July 2004 16:21 > To: ris-int at ripe.net > Subject: [ris-int] Draft minutes from Monday's RIS meeting > (apologies for the delay) > > > RIS Meeting - 26 July 2004 > > Present: Matthew, Shane, Arife, James, Bruce, Ruud, Henk, Vasco > > Scribe: James > > Agenda: > - RRC Status > - RRC Moves/New RRCs > - myASn > - AOB > > RRC Status > > Q. Are there any existing tools to monitor BGP sessions? > A. Not that are directly relevent to the RIS. The current tools > compare BGP sessions against the registered peering > policy (the > AS3333 aut-num object). > > What to monitor? > - percentage of peers up/down? > - peer down for a "long time"? > > Should there be automatic or manual notification of peers when a > session is down? > > Who to contact at peers? > - We mostly use the IRR (RIPE, etc. databases) > - encourage peers to keep their own information up to date > - Current "addpeer" script records contact information > in a log file > - need to keep our own information up to date > - useful for historical data (e.g. who was the > responsible person at > the peer when the peering was first established, etc.) > > Action: monitor peering sessions in Nagios (OPS) > > peering sessions which are neither up nor > administratively > disabled should generate alerts. > > Action: document procedure for handling peering > sessions which are > down. (SED) > > 1. Nagios notifies SED, SED contacts peer > 2. After two weeks (?), session is > administrively disabled > ("neighbor ... shutdown"), (peer is contacted?) > 3. After a peering session is down for a > further period with no > response from the peer then the peering is > removed from the > RRC ("no neighbor ...") > > > RRC Moves/New RRCs > > * RRC08 (MAE West) has very few peers and more networks > are pulling out > of MAE West. We need to investigate alternative > locations for a route > collector on the US West Coast > > - PAIX > - Seattle > - LAIIX (Telehouse) > - ... > > Action: compare member lists of each West Coast exchange point > (Matthew) > > How to move RRC? Simply get MCI to ship box to new > location (or wait > for NCC staff to be in the vicinity of San Jose). > > * RRC06 (DIX-IE (NSPIXP2), Japan) - Not getting any new > peerings. > > Action: Contact George Michaelson (APNIC). Henk and > Shane will be at > IETF and can meet up with him there. > > * RRC13 (new RRC in Moscow) > > - Matthew has been in touch with RIPN (Russian > Institute for Public > Networks). > > - To simplify customs issues, it may be better for the host > organisation to order machine to our specification (see below) > directly from Dell in Russia. We would want to see > the quote before > agreeing to the purchase. > > - We need to know the IP configuration for the box so > we can configure > and ship the installation CD once the box is ordered. > > - Recent RRCs have been specified as: > > Dell PowerEdge 1750 (1U server) > 1 GByte RAM > 3 x 73 GByte Disk (configured as RAID5) > 2.4 GHz Xeon CPU > > myASn > > Meeting with Alexis last week didn't happen (Alexis out > of town?) > > Action: contact Alexis to set up meeting (Arife) > > Matthew's slide "On the road to myASn v.1": > - Automate account creation > - bring together AS3333/K-Root/RIS peering setup and > myASn account > creation > - For each peering confirmation, the peer should be > made aware of > the other RIPE NCC peering opportunities, etc. > where appropriate. > > Action: Check with Dave Knight what, if anything, > is mentioned > about other NCC services when K-Root peering is > established (Bruce) > > - Would be easier if all NCC peerings were handled by the same > group. > - K-Root peerings are more restrictive than RIS peerings. > > AOB > > RIPE49 (Manchester) > > RIS Update presentation > myASn Tutorial > > Action: Speak to Shane and get back to Matthew > et al. (Arife) > [Shane had already left the meeting at > this point] > > Inventory > > Ruud asks for Dell Service Tags for each RRC to > add to the > inventory. > > Ops Interaction > > Reminder to use as first point of contact > instead of sending email to Bruce/James directly. > From dknight at ripe.net Wed Jul 28 18:59:17 2004 From: dknight at ripe.net (Dave Knight) Date: Wed, 28 Jul 2004 18:59:17 +0200 Subject: [ris-int] RE: Three things... In-Reply-To: <002801c474be$30dcc700$1f0200c1@rockstar> References: <5.2.1.1.2.20040728152220.0266e488@mailhost.ripe.net> Message-ID: <5.2.1.1.2.20040728185801.026c4c28@mailhost.ripe.net> At 18:16 28/07/2004 +0200, Matthew Williams wrote: >Hi Dave, > >See below: > > > > > > >1. Flashing RIS (~we need peers etc etc) in K-anycast > > peering ack (SED > > >do > > >RIS peering reqs) > > > > We can do that. We can add your blurb to the bottom of: > > /home/kroot/doc/peer-info Let me know what you want to put there. > > > >Something like this? Or is it too much? I don't really have an opinion ;) Here's what I did: Peering Details ---------------------------------------------------------------------------- Location IXP IP Route-Set Type --------------- --------------- --------------- --------------- ------- London XchangePoint 217.79.160.94 RS-KROOT-LINX Global Amsterdam AMS-IX 195.69.144.240 RS-KROOT-AMS-IX Global NL-IX 194.153.154.80 RS-KROOT-AMS-IX Global Athens AIX 195.130.89.220 RS-KROOT-GRNET Local Qatar QTEL 212.77.199.187 RS-KROOT Local ---------------------------------------------------------------------------- Peering Policy ---------------------------------------------------------------------------- We advertise only our own routes in AS25152. We will update our aut-num object in the RIPE Whois Database and kindly request you to update your aut-num object also. We will not to enter into a formal peering contract. At our Global mirror instances we accept any routes offered including transit. At our Local mirror instances we want to limit visibility of our advertisements and will likely use the well known no-export BGP community, if you would like to override this in order to advertise this route to your downstream customers let us know in advance. In the event of problems caused by leaked advertisements our policy is to shut down peerings and ask questions later. The remarks at the end of our AS25152 aut-num object hold the authoritative list of locations at which AS25152 is peering and which of those locations is considered Global or Local. ---------------------------------------------------------------------------- Contact Info ---------------------------------------------------------------------------- Support: | NOC Phone: +31 20 535 4400 Peering: | NOC Email: WWW: | ---------------------------------------------------------------------------- DNS Monitoring (dnsmon) & Test Traffic Measurements (TTM) ---------------------------------------------------------------------------- - Home Page: - Server View: - TTM General Information: ---------------------------------------------------------------------------- Routing Information Service (RIS) ---------------------------------------------------------------------------- - myASn beta: - Other Tools: - RIS General Information: You can support the RIS by donating a BGP feed. For a list of peering locations, see URL: Please send your peering request to rispeering at ripe.net. ---------------------------------------------------------------------------- > > I intend to do some work on making peerings management easier for > > RIPENCC,RIS,KROOT,AS112 > >Good move. As you know, SED will handle peering requests for the RIS. >There should possibly be more coordination, especially >RIS/myASn and K. That's the plan. > > following RIPE49. I will no doubt call a meeting when this > > gets started to > > look at everyones > > requirements before taking this to SED. > > > > >2. myASn accounts (also by SED in the future) sync w/ > > K-anycast peering > > >requests (monitor no-export compliance) > > > > I have been ignoring myASn stuff at the moment. We don't have > > time to do anything with it before RIPE49. I look forward to > > spending some time getting it all sorted shortly thereafter though :) > > > > When is it planned that the current development effort ends > > and goes into production? > >SED will take over v.1 of myASn by the second week in Aug. I'd say >announcement time would be around 1st of Sept, well before R49, >but that's ultimately SED's call. Fair enough. > > >3. When will you announce me to contacts ? ;) > > > > Heh, almost there. I have been getting all status up to date > > and reorganising things on the iii pages. I will shortly get > > to announcing you .. honest :) > >Okay, just bug when you need me. I'll monitor mail exchanges as much as I can. Cool beans :-) Cheers, dave From matthew at ripe.net Wed Jul 28 19:55:14 2004 From: matthew at ripe.net (Matthew Williams) Date: Wed, 28 Jul 2004 19:55:14 +0200 Subject: [ris-int] RE: Three things... In-Reply-To: <5.2.1.1.2.20040728185801.026c4c28@mailhost.ripe.net> Message-ID: <002d01c474cc$0903a240$1f0200c1@rockstar> 1. Excellent stuff. Much obliged. 2. Great that we're on the same page there :) 3. ACK Cheers, Matthew > -----Original Message----- > From: Dave Knight [mailto:dknight at ripe.net] > Sent: 28 July 2004 18:59 > To: Matthew Williams > Cc: ris-int at ripe.net; 'Arife Vural'; k-anycast at ripe.net > Subject: RE: Three things... > > > At 18:16 28/07/2004 +0200, Matthew Williams wrote: > >Hi Dave, > > > >See below: > > > > > > > > > >1. Flashing RIS (~we need peers etc etc) in K-anycast > > > peering ack (SED > > > >do > > > >RIS peering reqs) > > > > > > We can do that. We can add your blurb to the bottom of: > > > /home/kroot/doc/peer-info Let me know what you want to put there. > > > > > > >Something like this? Or is it too much? > > I don't really have an opinion ;) > Here's what I did: > > Peering Details > -------------------------------------------------------------- > -------------- > Location IXP IP Route-Set Type > --------------- --------------- --------------- > --------------- ------- > London XchangePoint 217.79.160.94 RS-KROOT-LINX Global > Amsterdam AMS-IX 195.69.144.240 RS-KROOT-AMS-IX Global > NL-IX 194.153.154.80 > RS-KROOT-AMS-IX Global > Athens AIX 195.130.89.220 RS-KROOT-GRNET Local > Qatar QTEL 212.77.199.187 RS-KROOT Local > -------------------------------------------------------------- > -------------- > > Peering Policy > -------------------------------------------------------------- > -------------- > We advertise only our own routes in AS25152. We will update > our aut-num object in the RIPE Whois Database and kindly > request you to update your aut-num object also. We will not > to enter into a formal peering contract. At our Global mirror > instances we accept any routes offered including transit. At > our Local mirror instances we want to limit visibility of our > advertisements and will likely use the well known no-export > BGP community, if you would like to override this in order to > advertise this route to your downstream customers let us know > in advance. In the event of problems caused by leaked > advertisements our policy is to shut down peerings and ask > questions later. The remarks at the end of our AS25152 > aut-num object hold the authoritative list of locations at > which AS25152 is peering and which of those locations is > considered Global or Local. > -------------------------------------------------------------- > -------------- > > Contact Info > -------------------------------------------------------------- > -------------- > Support: | NOC Phone: +31 20 535 4400 > Peering: | NOC Email: > WWW: | > -------------------------------------------------------------- > -------------- > > DNS Monitoring (dnsmon) & Test Traffic Measurements (TTM) > -------------------------------------------------------------- > -------------- > - Home Page: > - Server View: > - TTM General Information: > -------------------------------------------------------------- > -------------- > > Routing Information Service (RIS) > -------------------------------------------------------------- > -------------- > - myASn beta: > - Other Tools: > - RIS General Information: > > You can support the RIS by donating a BGP feed. For a list of > peering locations, see URL: > > Please send your peering request to rispeering at ripe.net. > -------------------------------------------------------------- > -------------- > > > > > I intend to do some work on making peerings management easier for > > > RIPENCC,RIS,KROOT,AS112 > > > >Good move. As you know, SED will handle peering requests for the RIS. > >There should possibly be more coordination, especially > >RIS/myASn and K. > > That's the plan. > > > > following RIPE49. I will no doubt call a meeting when this gets > > > started to look at everyones > > > requirements before taking this to SED. > > > > > > >2. myASn accounts (also by SED in the future) sync w/ > > > K-anycast peering > > > >requests (monitor no-export compliance) > > > > > > I have been ignoring myASn stuff at the moment. We don't > have time > > > to do anything with it before RIPE49. I look forward to spending > > > some time getting it all sorted shortly thereafter though :) > > > > > > When is it planned that the current development effort > ends and goes > > > into production? > > > >SED will take over v.1 of myASn by the second week in Aug. I'd say > >announcement time would be around 1st of Sept, well before R49, > >but that's ultimately SED's call. > > Fair enough. > > > > >3. When will you announce me to contacts ? ;) > > > > > > Heh, almost there. I have been getting all status up to date and > > > reorganising things on the iii pages. I will shortly get to > > > announcing you .. honest :) > > > >Okay, just bug when you need me. I'll monitor mail exchanges > as much as > >I can. > > Cool beans :-) > > Cheers, > dave > From wilhelm at ripe.net Wed Jul 28 20:40:25 2004 From: wilhelm at ripe.net (Rene Wilhelm) Date: Wed, 28 Jul 2004 20:40:25 +0200 Subject: [ris-int] FYI: RISwhois usage statistics Message-ID: <200407281840.i6SIeP1o006306@birch.ripe.net> RISwhois was announced early december 2003 and presented in the january 2004 RIPE47 meeting. After that we didn't do any marketing (other than provide pointers on ris webpages) I just had a rough look at the access statistics (as logged to /var/log/local.log and archived in /var/log/ARCHIVE/local.log*.gz) and found it nice to see there's continued intereset for RISwhois from external users. Excluding any of the RIPE NCC and RIPE meeting addresses (193.0.[0-9].*) RISwhois had 2,325,338 connections[*] from 815 distinct hosts. Top 10 users: IP #connections 213.19.146.13 932354 145.89.193.200 478159 128.223.6.40 363763 207.172.7.46 345502 213.186.35.102 58583 212.126.218.123 45000 202.12.29.252 37448 210.25.133.26 21005 146.115.9.21 15348 212.126.218.122 14242 halfweg.ripe.net made 16150 connections, which I take should all be attributed to the CGI web interface on www.ris.ripe.net So although started from a perspective of improving TTM's IP<>AS mapping, it seems we did add something useful/interesting to the RIS service portfolio. -- Rene [*] like whois.ripe.net, riswhoisd can keep a connection open on user request, thus #connections is not necessarily equal to #queries answered. From henk at ripe.net Wed Jul 28 22:14:50 2004 From: henk at ripe.net (Henk Uijterwaal (RIPE NCC)) Date: Wed, 28 Jul 2004 22:14:50 +0200 (CEST) Subject: [ris-int] Re: FYI: RISwhois usage statistics In-Reply-To: <200407281840.i6SIeP1o006306@birch.ripe.net> References: <200407281840.i6SIeP1o006306@birch.ripe.net> Message-ID: On Wed, 28 Jul 2004, Rene Wilhelm wrote: > RISwhois was announced early december 2003 and presented > in the january 2004 RIPE47 meeting. After that we didn't > do any marketing (other than provide pointers on ris webpages) > > I just had a rough look at the access statistics (as logged to > /var/log/local.log and archived in /var/log/ARCHIVE/local.log*.gz) > and found it nice to see there's continued intereset for RISwhois > from external users. > > Excluding any of the RIPE NCC and RIPE meeting addresses (193.0.[0-9].*) > RISwhois had 2,325,338 connections[*] from 815 distinct hosts. Nice :-) Henk > > Top 10 users: > > IP #connections > 213.19.146.13 932354 > 145.89.193.200 478159 > 128.223.6.40 363763 > 207.172.7.46 345502 > 213.186.35.102 58583 > 212.126.218.123 45000 > 202.12.29.252 37448 > 210.25.133.26 21005 > 146.115.9.21 15348 > 212.126.218.122 14242 > > > halfweg.ripe.net made 16150 connections, which I take should all > be attributed to the CGI web interface on www.ris.ripe.net > > So although started from a perspective of improving TTM's IP<>AS > mapping, it seems we did add something useful/interesting to > the RIS service portfolio. > > -- Rene > > [*] like whois.ripe.net, riswhoisd can keep a connection open > on user request, thus #connections is not necessarily equal > to #queries answered. > ------------------------------------------------------------------------------ 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 ------------------------------------------------------------------------------ Process and Procedure are the last hiding place of people without the wit and wisdom to do their job properly. (David Brent). From james at ripe.net Thu Jul 29 09:24:02 2004 From: james at ripe.net (James Aldridge) Date: Thu, 29 Jul 2004 09:24:02 +0200 Subject: FW: [ris-int] Draft minutes from Monday's RIS meeting (apologies for the delay) In-Reply-To: Message from "Matthew Williams" of "Wed, 28 Jul 2004 18:25:23 +0200." <002a01c474bf$7b9b7e20$1f0200c1@rockstar> Message-ID: <200407290724.i6T7O21o023858@birch.ripe.net> "Matthew Williams" wrote: > Hi James, > > > - Recent RRCs have been specified as: > > > > Dell PowerEdge 1750 (1U server) > > 1 GByte RAM > > 3 x 73 GByte Disk (configured as RAID5) > > 2.4 GHz Xeon CPU > > Please send me a spec from Dell's web site that's intelligible for MSK-IX fol k (should also give us an estimate on price excl BTW). Below. I'm not sure this is any more intelligible though ;-) James ---------- cut here ---------- ------------------------------------------------------------------------------- Dell Computer Corporation Limited - De Dell Store Samenvatting van het mandje gedownload op 7/29/2004 ------------------------------------------------------------------------------- De prijzen zijn alleen geldig tot en met het einde van de werkdag op de dag dat de samenvatting van het mandje was gedownload. ------------------------------------------------------------------------------- =============================================================================== Dell raadt Microsoft^? Windows^? XP Professional aan =============================================================================== -* PowerEdge? 1750 August Promotion *- ====================================== Aantal : 1 Totaal excl. : 2319.00 EUR Totaal incl. : 2759.61 EUR Standard Features ================= Serverworks Grand Champion LE chipset with 2:1 memory interleaving and a five peer PCI bus architecture for excellent I/O throughput Up to two Intel? Xeon Processors with NetBurst Micro-architecture with Hyper-Threading support. Up to 8GB ECC DDR SDRAM for expandable performance. Chipkill support Online Spare Row capabilities provide improved memory availability. Optional activation of PERC 4/di embedded dual channel Ultra 320 RAID controller with 128MB of battery backed cache to protect your data. Hot-plug hard drives, optional hot-plug redundant power supplies and hot plug non-redundant fans for high availability. Support for 3 hard drives, giving 438GB maximum internal data storage. Embedded dual channel Ultra320 SCSI controllers Tool-less chassis and cable-less motherboard design for ease of maintenance & upgrade Dual embedded Copper Gigabit NIC Rapid rack rail design for fast deployment in a rack. The Dell OpenManage suite to enable automated/rapid operating system installation, and complete network management with IT Assistant. Special Promotion ================= Promotion : 300- special promotional discount Premier Enterprise Support ========================== 3 Years Bronze On-Site Service with Next Business Day Response (-EUR - 700.00 EUR) Packaged Installation Services ============================== No installation Chassis ======= 3rd Party Rack Rails Kit (+ EUR 20.00 EUR) Processor ========= Single Intel? Xeon processor 2.4GHz with 512K cache, 533MHz Front Side Bus Memory - Special Promotion ========================== 1GB DDR SDRAM (2x512MB 266MHz DIMMs) - including promotional saving Hot-Plug Power Supplies ======================= One Non-Redundant Power Supply Riser ===== Riser 2X64-Bit/133MHz PCIX included Bezel ===== PE1750 Bezel Assembly Monitor ======= Not Included Storage Device and Recordable Media =================================== 24x Max IDE CD-ROM Keyboard ======== Not Included Mouse ===== Not Included 1st Hard Drive ============== 73GB 10,000rpm 1" U320 SCSI hard drive (+ EUR 100.00 EUR) 2nd Hard Drive ============== 73GB 10,000rpm 1" U320 SCSI hard drive (+ EUR 290.00 EUR) 3rd Hard Drive ============== 73GB 10,000rpm 1" U320 SCSI hard drive (+ EUR 290.00 EUR) 1st RAID or SCSI Controller Card ================================ PERC 4/Di embedded RAID (with 128MB of battery backed Cache). 2 channels (1 internal and 1 external) (+ EUR 220.00 EUR) 2nd RAID or SCSI Controller Card ================================ Not Included Internal Hard Drive RAID Configuration ====================================== RAID 5 - hard drives connected to PERC4/Di RAID controller (requires 3 identical drives) (+ EUR 50.00 EUR) External PowerVault Tape Backup enclosures ========================================== Not Included Tape BackUp Software ==================== None 2nd Network Card ================ Not Included Communications ============== Not Included Network PowerConnect Switch =========================== Not Included Uninterruptible Power Supplies (UPS) ==================================== Not Included OpenManage Subscription Service =============================== No OpenManage Subscription Factory Installed Operating System ================================== Not Included System Documentation ==================== Paper documents not included (electronic version on Dell OpenManage CD) Software & Storage Support ========================== No Software & Storage support included ------------------------------------------------------------------------------- System ====== Prijs excl. : 2319.00 EUR BTW tarief : 19% Prijs incl. : 2759.61 EUR Levering ======== Prijs excl. : 82.00 EUR BTW tarief : 19% Prijs incl. : 97.58 EUR =============================================================== Totaal excl. : 2401.00 EUR Totaal incl. : 2857.19 EUR Prijs exclusief B.T.W. : 2401.00 EUR Prijs inclusief B.T.W. : 2857.19 EUR =============================================================== Inhoud uitsluitend ontworpen en juist voor Nederland klanten en gebruikers. De voorwaarden van Dell zijn van toepassing. Alle systeemprijzen en -specificaties kunnen zonder voorafgaande vermelding worden gewijzigd. Afgebeelde foto's van producten kunnen afwijken van de op deze webpagina genoemde specificaties. Systemen getoond met optionele extra's. WEERGEGEVEN PRIJZEN BEVATTEN NIET DE CORRECTE LOKALE BTW, VRACHTKOSTEN, IMPORTHEFFINGEN EN BELASTINGEN VOOR LUXEMBURG en worden opnieuw bevestigd nadat uw internet order is ontvangen. Language : nl Currency : eur Store : nlpad From ziya at ripe.net Thu Jul 29 09:58:53 2004 From: ziya at ripe.net (Ziya Suzen) Date: Thu, 29 Jul 2004 09:58:53 +0200 Subject: [ris-int] Re: myASN handover meeting In-Reply-To: <20040728150631.GK24006@ripe.net> References: <20040728150631.GK24006@ripe.net> Message-ID: <20040729075853.GE24915@x33.ripe.net> On 2004-07-28 17:06:31 +0000, Arife Vural wrote: > > Hi all, > > This is the summary of our meeting today: > > - Alexis will prepare the system maintenance documentation. This doc > will include the following items, > > - User management, put e-mail template of user request > - How to installation of myASN > - Adding new RRC > - Log files > - Deamons that are running > > Alexis will get back to Ziya and Arife today about timeline, after his > talk with Henk and Matthew. > > - Developers documentation will be written by Alexis and Ziya. It's a > half-day work. This will be scheduled after system maintenance doc is > ready. - There is no test suit and it is not feasible to write one at this point. > > - Arife will look at the myASN SQLs, all in myasn-scan code. > > Beyond those issues, today Alexis gave Ziya and me introduction to > myASN code, and also we created the master copy of the source and > put into CVS. > > Arife From alexis at ripe.net Wed Jul 28 17:51:05 2004 From: alexis at ripe.net (Alexis Yushin) Date: Wed, 28 Jul 2004 17:51:05 +0200 (CEST) Subject: [arife@ripe.net: [ris-int] myASN handover meeting] In-Reply-To: <20040728154508.GO24006@ripe.net> from "Arife Vural" at Jul 28, 2004 05:45:08 PM Message-ID: <200407281551.i6SFp5e1009956@birch.ripe.net> Once Arife Vural wrote: >Alexis, > >Could you also add which modules are required for myASN in system >maintenance doc? Just remembered. Uff... if i knew ;) Isnt it just find myasn -type f | xargs grep '^use' ?? Alexis From alexis at ripe.net Wed Jul 28 19:33:42 2004 From: alexis at ripe.net (Alexis Yushin) Date: Wed, 28 Jul 2004 19:33:42 +0200 (CEST) Subject: [arife@ripe.net: [ris-int] myASN handover meeting] In-Reply-To: <20040728155431.GP24006@ripe.net> from "Arife Vural" at Jul 28, 2004 05:54:31 PM Message-ID: <200407281733.i6SHXgd2028517@birch.ripe.net> Alright, I'll do it! if all wasnt enough: I got a flat tire on my bike :( Alexis From alexis at ripe.net Thu Jul 29 00:15:13 2004 From: alexis at ripe.net (Alexis Yushin) Date: Thu, 29 Jul 2004 00:15:13 +0200 (CEST) Subject: [ris-int] myASn admin doc draft Message-ID: <200407282215.i6SMFDVN007096@birch.ripe.net> Hi, This is a draft of the admin doc. Any comments/suggestions/critique or unrelated remarks are welcome :) Alexis 1. Overview This overview implies that the reader has familirized her/himself with the myASn user documentation and frequently asked questions. http://www.ris.ripe.net/myasn/help.html http://www.ris.ripe.net/myasn/faq.html myASn system internally consists basically of three parts: - frontend (web interface presently running on halfweg.ripe.net ) - backend (two perl demon scripts running on weesp.ripe.net ) - database (presently resided on weesp.ripe.net) Frontend consist of collection of Mason enabled web pages and help files that use perl libraries to access myASn database to configure the system and view the results of the processing done by backend. There are two versions of frontend: standalone and LIR Portal. The LIR Portal version of the frontend is not deployed at this moment and will be documented elsewhere. Everything below applies to the standalone version. Backend consist of two perl demon scripts: myasn-scan - that does the processing of the data and generates alarms that are stored in the myasn database myasn-send - that send the email notifications of the alarms that are generated by myasn-scan Both frontend and backend use the same set of perl modules. 2. myASn Installation pre-required modules: Alzabo::MethodMaker Alzabo::Runtime::Schema Apache::DBI DBI Exception::Class IO::Socket Lingua::EN::Inflect Mail::RFC822::Address Net::IP Socket Text::ASCIITable URI XML::Parser myASn installation on both frontend and backend servers should be as simple as checking the myASn package out of master CVS repository. export CVS_RSH=ssh export CVSROOT :ext:cow.ripe.net:/ncc/cvsroot cvs co myasn Further updates of myasn system can be simply done by issuing cvs up in the myasn directory. (use cvs -n up first, to see what's about to happen :) myASn system should be installed on both frontend and backend server into /home/risops/myasn directory. This directory is hard-coded into use lib statements of the following files in the distribution: ./backend/myasn-scan.perl ./backend/myasn-send.perl ./lib/RIPE/NCC/myASn.pm ./www/syshandler as long as it might be specified in myasn.conf configuration file. Once myasn check out the following symbolic links should be made on frontend server (halfweg.ripe.net): ln -s /home/risops/myasn/www /home/risops/www/ris/myasn ln -s /home/risops/myasn/alzabo/schemas/myasn /var/www/alzabo/schemas/myasn XXX Arife might want to add here comments about ris.rc file she made. 3. Configuring myASn Once myASn is installed the configuration of myasn is done via master configuration file, /home/risops/myasn/etc/myasn.conf It basically consists of line with name = value, where in most cases name is the same as a command line arguement of myasn scripts without leading dashes. For example, one could put risdb-username = myasn which would be similar to issuing myasn-scan --risdb-username myasn There are a number of variables that are common to all myASn components, example values are given: risdb_hostname = 193.0.0.210 Hostname or ip address of the RIS database. risdb_username = myasn Username to use for connecting to RIS database. risdb_password = ticvdkjw Password to go with the username above. myasn_database = myasn Hostname or ip address of the myASn database. myasn_hostname = 193.0.0.210 myasn_username = myasn Username to use for connecting to myASn database. myasn_password = tiablkdfd;akj The password to use to connect to myASn datbase. myasn_port = 3306 Port to use to connect to myASn database. pidfile_dir = /home/risops/myasn/log The directory where all the pid/lockfiles will be created. Must be writable to myasn-scan and myasn-send invoking users. The pid files will be created in the format of: $pidfile_dir/myasn-scan.$rrc.pid $pidfile_dir/myasn-send.pid This option can be overwritten with pidfile option that doesnt do rrc name expansion like shown above. The same rules apply to logfile_dir and logfile variables. logfile_dir = /home/risops/myasn/log The directory where all the logfiles will be stored. Same requirement as above. rrc_list = rrc00 rrc01 rrc02 rrc03 rrc04 rrc05 rrc06 rrc07 rrc08 rrc10 rrc11 White-space separated list of the route collectors. Once a new RRC is added it should be added here as well and myasn related tables should be created. XXX Arife more on this? # wait these many seconds for myasn-send loop wait = 900 This one is myasn-send specific. myasn-send will wait this many seconds before starting sending a new serious of alarm notifications by email. # wait these many seconds for myasn-scan loop loop-wait = 300 This is a similar variable for myasn-scan. myasn-scan will wait this many seconds before processing new series of bgp updates. # delay this many seconds before forking next child fork-delay = 30 myasn-scan will wait this many seconds before forking another child process. This is done to desyncronize processing of rrc to avoid peak mysql workloads. To configure the frontend, the Apache's httpd.conf needs the following lines added: AuthType Basic AuthName "MyASN Login" AuthUserFile /home/risops/myasn/etc/myasn-passwords Require valid-user SetHandler perl-script PerlHandler HTML::Mason::ApacheHandler PerlSetVar MasonAllowGlobals $User PerlSetVar MasonAutohandlerName autohandler.html The first section is responsible for authenticating users, and the second one makes sure that the myASn files are handled by Mason. 4. Accounts and users myASn account in standalone version is the same thing as LIR registry in the original LIR portal version. myASn account might have a number of users that share the same alarm configuration and have access to the same information. As a matter of fact myASn doesn't know anything about users, it only cares about the accounts or registries. Usernames are used solely for access authorization purposes and welcome text. As far as user accounts are concerned they are created automatically based on the $User->username and $User->regid global variables. These variables are either initialized by LIR Portal (for LIR Portal version) or by syshandler in the standalone version. In standalone version $User->username and $User->regid are produced by splitting Apache username into username at regid parts. Therefore Apache username alexis at 55555 will result in $User->username = 'alexis' and $User->regid = '55555' If myasn account 55555 does not exist yet, it will be created automatically. Therefore to create a new myasn account a new user should be added into /home/risops/myasn/etc/myasn-passwords file. It can be done with htpasswd /home/risops/myasn/etc/myasn-passwords username at accountname password, for example: htpasswd /home/risops/myasn/etc/myasn-passwords alexis at 55555 alexis123 will create an account 55555 with username alexis that will have password 123 To change user password the same command as above should be used. XXX - User management, put e-mail template of user request XXX I'm not sure what kind of template I must provide?!? 5. Logging myASn logfiles go into the location specified by --logfile or --logfile-dir options specified either in myasn.conf configuration file or at command line. When myasn-scan is invoked with --logfile-dir, logfile name expansion is being made in a form of: $logfile_dir/myasn-scan.$rrc.log So ig logfile_dir is /home/risops/myasn/log, then for every rrc there will be a separate logfile created. For example for rrc05: /home/risops/myasn/log/myasn-scan.rrc05.log The same applies to --pidfile and --pidfile-dir directives. 6. Backend demon's invokation As mentioned above, two myasn demons are running on weesp.ripe.net (or whatever backend server is in use): myasn-scan myasn-send myasn-scan needs to know to which databases to connect and which credentials to use, location of its logfile and pidfile directory, and loop-wait, fork-delay. All of which is normally specified in myasn.conf file. The only command line myasn-scan should require if myasn.conf is properly setup is: myasn-scan.perl --fork --loop This command tells that myasn-scan should loop, that is keep on waiting on an processing incoming data, and that it should fork a separate process for every rrc. It is important that fork-delay variable is configured, so that not all the processes will be accessing the database exactly at the same time, but with some offset. myasn-send will fork by default so it doesn't require any command line. 7. Maintenance XXX To be developed From arife at ripe.net Thu Jul 29 16:39:18 2004 From: arife at ripe.net (Arife Vural) Date: Thu, 29 Jul 2004 16:39:18 +0200 Subject: [ris-int] RIS contact addresess Message-ID: <20040729143918.GH15323@ripe.net> Hi guys, What about changing RIS contact info from The contact persons for RIS Project are: * Arife Vural * Daniel Karrenberg * Henk Uijterwaal * James Aldridge * Matthew Williams To mail the whole group, please use ris at ripe.net. to something like that: Contact address for RIS Project: Peering: rispeering at ripe.net Questions/feedback/comments: ris at ripe.net Arife From matthew at ripe.net Thu Jul 29 16:53:33 2004 From: matthew at ripe.net (Matthew Williams) Date: Thu, 29 Jul 2004 16:53:33 +0200 Subject: [ris-int] RIS contact addresess In-Reply-To: <20040729143918.GH15323@ripe.net> Message-ID: <004d01c4757b$d203ad20$1f0200c1@rockstar> Fine with me. Cheers, Matthew > -----Original Message----- > From: ris-int-admin at ripe.net [mailto:ris-int-admin at ripe.net] > On Behalf Of Arife Vural > Sent: 29 July 2004 16:39 > To: ris-int at ripe.net > Subject: [ris-int] RIS contact addresess > > > > Hi guys, > > What about changing RIS contact info from > > The contact persons for RIS Project are: > > * Arife Vural > * Daniel Karrenberg > * Henk Uijterwaal > * James Aldridge > * Matthew Williams > > To mail the whole group, please use ris at ripe.net. > > to something like that: > > Contact address for RIS Project: > > Peering: rispeering at ripe.net > Questions/feedback/comments: ris at ripe.net > > Arife > From matthew at ripe.net Thu Jul 29 17:15:11 2004 From: matthew at ripe.net (Matthew Williams) Date: Thu, 29 Jul 2004 17:15:11 +0200 Subject: [ris-int] RE: RIS Info Page In-Reply-To: <5.2.1.1.2.20040729145307.046bb118@mailhost.ripe.net> Message-ID: <004f01c4757e$d753f7f0$1f0200c1@rockstar> This looks fine. Please link the rrc12 news flash to http://www.ripe.net/ris/risintro.html (page edited) Cheers, Matthew > -----Original Message----- > From: Adrian Bedford [mailto:adrian at ripe.net] > Sent: 29 July 2004 14:56 > To: Matthew Williams > Cc: webmaster at ripe.net > Subject: RIS Info Page > > > Hey Matthew > > Sorry for not getting back sooner. I'm really snowed under > right now again. > > The RIS Page text will be used on the new website, which is > supposed to be > launching at the end of August, but in the meantime, if you > want to use the > text we talked about, I've taken on board your comments and > this is the > definitive text...can you create/edit the page you talked > about. When the > new site goes live, we will be able to easily edit it anyway > and save you > the hassle.... > > > > The Routing Information Service (RIS) started as a RIPE NCC > project in > 1999. Currently there are over 300 IPv4 and IPv6 peers at 12* data > collection points in Europe, Japan and North America > > The project aims to collect and store Border Gateway Protocol > (BGP) routing > information and make it publicly available for the Internet > community. > Network operators troubleshoot routing problems by looking at data > collected over time without being limited to a single BGP > view. Archived > raw RIS data is also available, which can be used for > research purposes. > > You can support the RIS by providing a BGP feed. You can find > a list of RIS > peering locations at: > http://www.ris.ripe.net/cgi-bin/rrcstatus.cgi Peering requests can be sent to or through a web form, you can find at: http://www.ris.ripe.net/cgi-bin/peerreg.cgi * RRC09 was decommissioned in May, 2004 From alexis at ripe.net Sat Jul 31 16:54:42 2004 From: alexis at ripe.net (Alexis Yushin) Date: Sat, 31 Jul 2004 16:54:42 +0200 (CEST) Subject: [ris-int] new features Message-ID: <200407311454.i6VEsgBq022178@birch.ripe.net> Hi, I finished xml.html please try it out, the templates are now provided in the form. I also have an experimental version of retromatch but it still needs some premission granting action from Arife. Everything else that was on the wish-list is finished, plus some extra's like myasn-admin delete to delete an entire registry and deleting all alarms in a group. I'm pretty much done. Since the project is finished, as far as my contract is concerned, I'd like to invite everybody to have a Columbus beer with me at 't IJ brewery. Suggestions for a specific date? Alexis