- db-wg - mailman.ripe.net

Re: [db-wg] Notification message change
by Thor Kottelin 19 Jun '08

19 Jun '08

> Date: Wed, 18 Jun 2008 17:04:16 +0200 > From: Denis Walker <denis(a)ripe.net> > To: Database WG <db-wg(a)ripe.net>, > ncc-services-wg <ncc-services-wg(a)ripe.net> > With most updates to the RIPE Database, notification messages are sent > out. Many of these notifications are hitting users' ticketing > systems or arriving in mailboxes with auto-responders. The "Reply-to:" > address in these notifications was <ripe-dbm(a)ripe.net>. Our help desk > ticketing system was receiving hundreds of e-mails a month from these > auto-responders. This was causing a serious operational > problem for our > Customer Services Department. > > To solve this problem, we have changed the e-mail header in the > notification messages we send out. They now have the "From:" and > "Reply-to:" addresses set to <unread(a)ripe.net>. As the name suggests, > any replies to this address are not read by anyone and they are just > dropped from our mail system. Hello Denis, The local-part "unread" gives such a suggestion--at most--in English, and not because of any standard or other convention. The "Reply-To:" line, on the other hand, unequivocally (RFC 2822) states that replies are expected at the address it shows. As you probably know, localized mail clients often use it to display something along the lines of "your replies are invited to". While you are to thank for the heads-up, I would have expected RIPE NCC, of all organizations, to come up with a more stylish and exemplary solution to the problem. Also, assuming that "hundreds" stands for e.g. nine hundred, that would mean 900 / 30 = approximately 30 surplus messages per day. Does such a volume really cause serious operational issues on a departmental level? Some of us (tinu) receive hundreds of spurious messages every *day* into (or intended for) *personal* mailboxes, and are easily able to handle that noise, perhaps with a little help from filtering software. With regards, -- Thor Kottelin CISM, CISSP fax +358 102 961 064 thor(a)anta.net, PGP 0x327B7345 http://www.anta.net/

2 1

Notification message change
by Denis Walker 18 Jun '08

18 Jun '08

[Apologies for duplicates] Dear Colleagues, With most updates to the RIPE Database, notification messages are sent out. Many of these notifications are hitting users' ticketing systems or arriving in mailboxes with auto-responders. The "Reply-to:" address in these notifications was <ripe-dbm(a)ripe.net>. Our help desk ticketing system was receiving hundreds of e-mails a month from these auto-responders. This was causing a serious operational problem for our Customer Services Department. To solve this problem, we have changed the e-mail header in the notification messages we send out. They now have the "From:" and "Reply-to:" addresses set to <unread(a)ripe.net>. As the name suggests, any replies to this address are not read by anyone and they are just dropped from our mail system. We have also made a small change to the introductory text to make it clear that these e-mails are auto-generated. We also clearly show users the e-mail reply address to use if they have an issue with the notification. This change was implemented today. It should not affect any users unless they parse the mail headers or the introductory text in the notification. Examples of the old and new notification messages are shown below. Regards, Denis Walker Business Analyst RIPE NCC Database Group Old notification message ____________________________________________________ To: user(a)somewhere.com From: RIPE Database Notifications <bitbucket(a)ripe.net> Subject: Notification of RIPE Database changes Reply-To: ripe-dbm(a)ripe.net Precedence: bulk Auto-Submitted: auto-generated Dear Colleague, This is to notify you that some object(s) in RIPE database which you either maintain or are listed as to-be-notified have been added, deleted or changed. The update causing these changes had the following mail headers: > From: user(a)somewhereelse.com > Subject: > Date: Tue, 17 Jun 2008 00:00:18 +0200 (CEST) > Reply-To: user(a)somewhereelse.com > MsgId: <2008061622> For assistance or clarification please contact: RIPE Database Administration <ripe-dbm(a)ripe.net> New notification message ____________________________________________________ To: user(a)somewhere.com From: RIPE Database Notifications <unread(a)ripe.net> Subject: Notification of RIPE Database changes Reply-To: unread(a)ripe.net Precedence: bulk Auto-Submitted: auto-generated Dear Colleague, This is to notify you that some object(s) in RIPE database which you either maintain or are listed as to-be-notified have been added, deleted or changed. This message is auto-generated. Please DO NOT reply to this message. If you do not understand why we sent you this message, or for assistance or clarification please contact: RIPE Database Administration <ripe-dbm(a)ripe.net> The update causing these changes had the following mail headers: > From: user(a)somewhereelse.com > Subject: > Date: Tue, 17 Jun 2008 00:00:18 +0200 (CEST) > Reply-To: user(a)somewhereelse.com > MsgId: <2008061622>

1 0

ANNOUNCEMENT: RIPE NCC Training Courses
by Training 26 May '08

26 May '08

[Apologies for duplicate e-mails] Dear Colleagues, The RIPE NCC invites you to register for one of our upcoming training courses: - The LIR Training Course This course teaches LIRs how to request Internet number resources and interact with the RIPE NCC. A course outline is available at: http://www.ripe.net/training/lir/outline.html - The Routing Registry Training Course This course teaches LIRs how to use the RIPE Database for routing. A course outline is available at: http://www.ripe.net/training/rr/outline.html - The DNS for LIRs Training Course This course teaches LIRs about the RIPE NCC's DNS-related services. A course outline is available at: http://www.ripe.net/training/dns/outline.html To see the location of upcoming courses and to register, please use the LIR Portal or complete the registration form on our website at: http://www.ripe.net/cgi-bin/trainingform.pl.cgi If you have any questions please do not hesitate to contact us at <training(a)ripe.net>. Kind regards, Rumy Kanis Training Services Manager RIPE NCC

1 0

RIPE56 DB-WG Draft Agenda V2
by Wilfried Woeber, UniVie/ACOnet 05 May '08

05 May '08

Dear DB-WG folks, Chairpersons, "Meeting"! This is the 2ndt draft of an agenda for the DB-WG at RIPE56 in Berlin, May 2008. For time slot allocations please refer to the most up-to-date meeting plan at http://www.ripe.net/ripe/meetings/ripe-56/meeting-plan.html Attention please: this time the DB-WG meeting is scheduled for *Thursday* at 4 PM in the afternoon! Please note that, for our convenience, the time slot map has become clickable for those sessions which have already submitted a (draft) agenda! Best regards, Wilfried. ________________________________________________________________________ A. Administrative Matters . Welcome . select scribe . finalise agenda . approval of minutes from RIPE 55 . review of action list B. Data Base Update (Jos I. B., RIPE NCC) [~40 min] . Actions from previous meetins . DB Terms & Conditions . modification proposals (maintainer required, ...) . retiring rev-srv: attribute C. Follow-Up on [~20 min] . Task-Force on Data Protection Issues [t.b.c.] . Contact Data Quality/Requirements Discussion [t.b.c.] . Resource Certification Project [t.b.c.] D. High Avalability SW Update for IRR (Yasuhiro Shirasaki, NTT) . using ripe-whois and our experimental syncronization trial Y. Input from other WGs and TFs Z. AOB ________________________________________________________________________

1 0

RIPE56 DB-WG Draft Agenda V1
by Wilfried Woeber, UniVie/ACOnet 29 Apr '08

29 Apr '08

Dear DB-WG folks, Chairpersons, "Meeting"! This is the (very rough) 1st draft of an agenda for the DB-WG at RIPE56 in Berlin, May 2008. For time slot allocations please refer to the most up-to-date meeting plan at http://www.ripe.net/ripe/meetings/ripe-56/meeting-plan.html Attention please: this time the DB-WG meeting is scheduled for *Thursday* at 4 PM in the afternoon! Please note that, for our convenience, the time slot map becomes clickable for those sessions which have already submitted a (draft) agenda! Best regards, Wilfried. ________________________________________________________________________ A. Administrative Matters . Welcome . select scribe . finalise agenda . approval of minutes from RIPE 55 . review of action list B. Data Base Update (N.N., RIPE NCC) [~20 min] C. Follow-Up on [~30 min] . Task-Force on Data Protection Issues [t.b.c.] . DB-Terms and Conditions [t.b.c.] . Contact Data Quality/Requirements Discussion [t.b.c.] . Resource Certification Project [t.b.c.] D. DB-Software Developmen Activities [~20 min] . modification proposals (maintainer required, ...) . retiring rev-srv: attribute Y. Input from other WGs and TFs Z. AOB ________________________________________________________________________

1 0

A request for more information about "person" objects
by Searcher Wang 25 Apr '08

25 Apr '08

Dear DatabaseMaster: Thank you for reading my letter. I am a Ph.D student in Computer Science. Recently, I am working on how to validate the origins of BGP routes with the information exploited from RIRs. As well-known, the database of RIPE is famous for its accuracy. Thanks for the public access services of ripe database, I have built a prototype. However, some information of "person" objects that can be got from ftp://www.ripe.net has been taken out. I think you are trying to prevent spam. I do not intend to get the personal information of the person objects such as email, address and so on, but the relations among them are important for me. What I really want is the person objects' admin-c, tech-c, mnt-by attributes. I have done many experiments, in which there is a high false positive rate with my prototype. It seems that it is difficult to bypass this barrier. So I beg for your help to get more information about person objects. Could you please tell me how to get the entire information? Thanks for your reading again. Best Wishes! Sincerely Xiaoqiang <db-wg(a)ripe.net>

1 0

Outage report for mail updates to the RIPE Database
by Katie Petrusha 18 Apr '08

18 Apr '08

[ Apologies for duplicate mails ] Dear colleagues, From approximately 14:15 (UTC) on Thursday, 17 April 2008 to 09:00 (UTC) on Friday, 18 April 2008, some e-mail update messages to the RIPE Database service, <auto-dbm(a)ripe.net>, were not processed due to a problem with our system. All the messages received by <auto-dbm(a)ripe.net> were stored on our mail server and the problem has now been resolved. All the saved update messages are currently being processed. If you sent an e-mail update to the RIPE Database service during this period, you will receive an acknowledgement message shortly. There is no need to re-send any update messages. We apologise for any inconvenience that this may have caused. Regards, Katie Petrusha Senior Software Engineer RIPE NCC

1 0

Call for agenda items, DB-WG Meeting during RIPE56, Berlin, DE
by Wilfried Woeber, UniVie/ACOnet 16 Apr '08

16 Apr '08

Dear DB-WG folks, planning activities for the next RIPE Meeting - RIPE56 in Berlin - have already started, thus this call for agenda items. Please submit (to the WG list or to me personally) your item requests or suggest topics for discussion to be included in the draft agenda! (I plan to distribute the 1st version of the draft agenda in about one week from now.) Please note that the DataBase-WG meeting is, this time, scheduled for *Thursday* afternoon. The overall RIPE 56 meeting outline is already available at http://www.ripe.net/ripe/meetings/ripe-56/meeting-plan.html The list of plenary presentations and the session archive may eventually become available at [- this page does not exist yet -] http://www.ripe.net/ripe/meetings/ripe-56/presentations/ or a different URL. See you soon in Berlin, Wilfried.

1 0

Announcement: Maintenance on 12-13 April 2008
by James Aldridge 09 Apr '08

09 Apr '08

[Apologies for duplicates] Dear Colleagues, The RIPE NCC will migrate a number of servers to new racks at NIKHEF between 08:00 and 18:00 (UTC) on the following dates: - Saturday, 12 April 2008 - Sunday, 13 April 2008 Aspects of the following services will be affected at various times during the migration periods: - BGP peering sessions will be down - nikrtr.ripe.net - AS3333 (217.79.172.5; 195.69.144.69; 2001:7f8:1::a500:3333:1) - K-Root (AS25152) at AMS-IX, NL-IX and XPE - AS112 (AS112) at AMS-IX - RIS (AS12654) at AMS-IX, NL-IX and GN-IX - DNS services: - The AMS-IX/XPE/NL-IX K-Root instance and the AS112 server at AMS-IX will be unavailable - WWW/FTP/Hostcount/E-Learning - LIR-Portal - WHOIS: - Syncupdates of the RIPE Database will be down - Mail updates will be queued and executed after the maintenance - RIPE DB-related CGIs on WWW will be down - Test Traffic Measurements (tt01) We apologise for any inconvenience that this may cause. If you have any questions about this, please send an e-mail to <ops(a)ripe.net> Regards, James Aldridge Senior Systems Engineer, RIPE NCC

1 0

RIPE Database (IPV6) outage on 2 April 2008
by RIPE Database Administration 31 Mar '08

31 Mar '08

[Apologies for duplicate messages] Dear Colleagues, On Wednesday, 2 April 2008, querying the RIPE Database via IPv6 will not be possible from 10:00-13:00 (UTC) due to maintenance. During this period, the RIPE Database will be accessible via IPv4 as usual. We apologise for any inconvenience this may cause. If you have any questions or concerns about this, please send an e-mail to <ripe-dbm(a)ripe.net> Regards, Katie Petrusha RIPE Database Administration RIPE NCC

1 0