July 2004 - Ris-int - mailman.ripe.net

We need your fb again ;)
by Matthew Williams 21 Jul '04

21 Jul '04

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/

4 4

Today's RIS meeting minutes
by Arife Vural 21 Jul '04

21 Jul '04

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

2 2

myasn xml
by Alexis Yushin 15 Jul '04

15 Jul '04

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: <alarmgroup name="XML-Import"> <alarm type="origin" mec="1" med="1m" ast="1h"> <prefix>193.0.0.0/16</prefix> <exception>193.0.1.0/24</exception> <exception>193.0.2.0/24</exception> <myasn>12324 2344</myasn> </alarm> <alarm type="customer"> <prefix>193.0.0.0/16</prefix> <exception>193.0.1.0/24</exception> <exception>193.0.2.0/24</exception> <myasn>12324 2344</myasn> <theirasn>12324 2344</theirasn> </alarm> </alarmgroup> You get the idea... Alexis

1 0

Re: [staff] DHL: received goods
by James Aldridge 15 Jul '04

15 Jul '04

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

1 0

FW: ANNOUNCEMENT: New RIS Remote Route Collector at DE-CIX (RRC12)
by Matthew Williams 14 Jul '04

14 Jul '04

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@ripe.net] > Sent: 07 July 2004 19:11 > To: 'ris-users(a)ripe.net' > Subject: ANNOUNCEMENT: New RIS Remote Route Collector at > DE-CIX (RRC12) > > > > > *** PGP Signature Status: good > *** Signer: Matthew Williams-Bywater <matthew(a)ripe.net> > *** 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(a)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(a)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 *** >

1 0

Re: [ris-int] Reply-To forwarded to /dev/null in myASn messages
by Rene Wilhelm 14 Jul '04

14 Jul '04

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 <alexis(a)ripe.net> ----- > > From: Alexis Yushin <alexis(a)ripe.net> > To: matthew(a)ripe.net (Matthew Williams) > Subject: Re: [MAILER-DAEMON(a)ripe.net: Undelivered Mail Returned to Sender] > Date: Wed, 14 Jul 2004 13:17:01 +0200 (CEST) > Cc: alexis(a)ripe.net (Alexis Yushin), arife(a)ripe.net (Arife Vural), > ris-int(a)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 <MAILER-DAEMON(a)ripe.net> ----- > > > >X-Recipient: <risops(a)ripe.net> > >Date: Tue, 13 Jul 2004 23:43:50 +0200 (CEST) > >From: MAILER-DAEMON(a)ripe.net (Mail Delivery System) > >Subject: Undelivered Mail Returned to Sender > >To: risops(a)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 <postmaster> > > > >If you do so, please include this problem report. You can > >delete your own text from the message returned below. > > > > The Postfix program > > > ><asnalarm(a)linkey.ru>: 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(a)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 <myasn(a)ripe.net> > >To: asnalarm(a)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 ----- >

4 4

Re: [ris-int] Reply-To forwarded to /dev/null in myASn messages
by Rene Wilhelm 14 Jul '04

14 Jul '04

>> 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 > > ><MAILER-DAEMON(a)ripe.net> ----- > > > > > >X-Recipient: <risops(a)ripe.net> > > >Date: Tue, 13 Jul 2004 23:43:50 +0200 (CEST) > > >From: MAILER-DAEMON(a)ripe.net (Mail Delivery System) > > >Subject: Undelivered Mail Returned to Sender > > >To: risops(a)ripe.net

2 2

Re: [MAILER-DAEMON@ripe.net: Undelivered Mail Returned to Sender]
by Alexis Yushin 14 Jul '04

14 Jul '04

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 <MAILER-DAEMON(a)ripe.net> ----- > >X-Recipient: <risops(a)ripe.net> >Date: Tue, 13 Jul 2004 23:43:50 +0200 (CEST) >From: MAILER-DAEMON(a)ripe.net (Mail Delivery System) >Subject: Undelivered Mail Returned to Sender >To: risops(a)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 <postmaster> > >If you do so, please include this problem report. You can >delete your own text from the message returned below. > > The Postfix program > ><asnalarm(a)linkey.ru>: 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(a)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 <myasn(a)ripe.net> >To: asnalarm(a)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) >

3 4

[alexis@ripe.net: Re: [MAILER-DAEMON@ripe.net: Undelivered Mail Returned to Sender]]
by Arife Vural 14 Jul '04

14 Jul '04

Hi guys, Can we do this? Arife ----- Forwarded message from Alexis Yushin <alexis(a)ripe.net> ----- From: Alexis Yushin <alexis(a)ripe.net> To: matthew(a)ripe.net (Matthew Williams) Subject: Re: [MAILER-DAEMON(a)ripe.net: Undelivered Mail Returned to Sender] Date: Wed, 14 Jul 2004 13:17:01 +0200 (CEST) Cc: alexis(a)ripe.net (Alexis Yushin), arife(a)ripe.net (Arife Vural), ris-int(a)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 <MAILER-DAEMON(a)ripe.net> ----- > >X-Recipient: <risops(a)ripe.net> >Date: Tue, 13 Jul 2004 23:43:50 +0200 (CEST) >From: MAILER-DAEMON(a)ripe.net (Mail Delivery System) >Subject: Undelivered Mail Returned to Sender >To: risops(a)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 <postmaster> > >If you do so, please include this problem report. You can >delete your own text from the message returned below. > > The Postfix program > ><asnalarm(a)linkey.ru>: 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(a)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 <myasn(a)ripe.net> >To: asnalarm(a)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 -----

1 0

rrc12
by Matthew Williams 13 Jul '04

13 Jul '04

Hi Arife, Are we ready to announce RRC12? Cheers, Matthew

3 12