- lir-wg - mailman.ripe.net

Re: Events of Tuesday, 27 October 1998.
by Petra Zeidler 30 Oct '98

30 Oct '98

Dear Mr. Kalogeras, Thus wrote Dimitrios Kalogeras (D.Kalogeras(a)noc.ntua.gr) [...] > > Mistakes are not improbable, however I can not condone your inadequate > backup procedures. Its totally out of imagination that you may have rouinned > the RIPE database. You have to keep yourself more dedicated to your work. > You forget that the RIPE DB is very much a moving target. There were backups, we (Xlink) even have a copy due to running a RIPE mirror, but what does that help? it took some time until the mass deletions were detected, and there were ample changes in the meantime. Re-enacting these would have been almost as much headache and also prone to oversights as repairing what was done and not interfering with standard operations. The only thing that /would/ have helped would have been a switch from take-first-free-handle to take-highest-existing+1, but that is not a trivial change either. kind regards, Petra Zeidler -- [X] Xlink Internet Service GmbH | | i.A. Petra Zeidler, Neukundenanschluss | zeidler(a)xlink.net | | Vincenz-Prie_nitz-Stra_e 3 [X] D-76131 Karlsruhe | Tel: 0721/9652-220 [X] Fax: 0721/9652-209 | | Geschdftsf|hrer: Michael Rotert. Amtsgericht Karlsruhe HRB 8161. | Auftrdge erledigen wir zu unseren Allgemeinen Geschdftsbedingungen. ---------------------------------------------------------------------[ ]

1 0

Objects affected by events of 27/10/1998.
by RIPE Database Administration 30 Oct '98

30 Oct '98

Dear Colleagues, We keep detailed logfiles of all updates to the RIPE Database. We processed these files to produce lists of all objects affected by the incidents earlier this week. We have decided to make these files public, to support you when ensuring that your data is consistent. These files contain only the name and nic-handle of affected person objects. These files may be obtained by anonymous ftp from: ftp://ftp.ripe.net/ripe/dbase/981027-incident.Delete ftp://ftp.ripe.net/ripe/dbase/981027-incident.New ftp://ftp.ripe.net/ripe/dbase/981027-incident.Update There are also gzip'ed versions available, using the same filenames, with the .gz extension. If you have any questions, please contact <ripe-dbm(a)ripe.net>. Regards, Ambrose Magee ----------------------- RIPE NCC Database Group

1 0

Big delays with <auto-dbm>.
by RIPE Database Administration 29 Oct '98

29 Oct '98

Dear Colleagues, Last night, there was a higher than usual number of messages to <auto-dbm(a)ripe.net>. Thus, there were some delays in processing these messages. This morning, we carried out some unrelated preventative maintenance and this has led to more delays. Your messages are being stored and will be processed as soon as possible. BTW, this maintenance was not linked to the recent actions of any user of the RIPE Database :-) If you have any questions, please contact <ripe-dbm>. It is either Murphy's Law, or Hallowe'en, or the Great Pumpkin, or whatever, that this happened this week. We thank you for your patience. Regards, --------------------------- The RIPE NCC Database Group.

1 0

ripe-141 web interface
by Paula Caslav 29 Oct '98

29 Oct '98

Hi, Thanks for the interest in and discussion about our proposed release of the web interface for ripe-141 forms. We think there is sufficient interest to proceed, and would like to clarify what we are planning: First, we will write and install a public web page at RIPE NCC which allows the entry of a ripe-141 form for *syntax* checking. The output will be a plain text page which can be pasted into an email. Second, we will release the source code of the above, with an added hook to allow sending of the output by email. LIRs will be able to install adaptations of this for use by their customers to check and submit their requests to the LIR, and by their hostmasters to check and submit their requests to RIPE NCC. The LIRs will be free to use this code in any other systems they have. We will implement a public page at RIPE NCC first to allow us to debug the software before it is made publicly available, and understand any problems the LIRS have in the implementation. We would hope to release the software soon after it is written. We cannot release the full code that we use here at the RIPE NCC, because it does some checks that we can only make available for requests that are within a registry's assignment window. These checks include looking for policy problems (as opposed to pure syntax problems) such as reserved addresses or inefficient address space usage. This is something that we'd like to be able to track. For example if a registry sends a request through the robot and it gives an error that the addresses are not being used efficiently, and then they decide to just increase the numbers everywhere to make it look more efficient, we'd like to be able to track this (yes, we have seen this happen). Therefore we will only make this part of the code available for the requests that are within a registry's assignment window and do not have to be sent to the RIPE NCC for approval. Therefore, we can only make this available on our web server (as part of the third stage). The third stage would be a public web page at RIPE NCC with some form of password authentication, which would allow LIRs to *fully* check assignments both smaller and larger than their assignment window, with larger assignments being sent on to the RIPE NCC hostmasters. We hope this meets most people's requirements. Inetnum database object submission thorugh a web page is being discussed in the db-wg. Therefore if you are interested in this topic, please get involved in that working group. To clarify the setup here at RIPE NCC: All mail to hostmaster(a)ripe.net is handled by the 'autohmdist' robot. This robot calls the 'autohm' robot to check and respond to ripe-141 requests, which we are discussing here. Both robots add messages to the hostmaster ticketing system, 'rtt'. Human hostmasters read and respond to messages through rtt. Paula Caslav Registration Services Manager RIPE NCC Maldwyn Morris Software Manager RIPE NCC

1 0

Re: Massive changed in the Ripe Database..
by Oliver J. Albrecht 28 Oct '98

28 Oct '98

[ Moderator note: changed local-ir(a)ripe.net -> lir-wg(a)ripe.net ] Hi, On Wed, Oct 28, 1998 at 05:34:20PM +0200, Pavel Golubev wrote: > I think PGP-signed request (Internic for example) - good way to stop > unauthorized access to database... That's probably the best approach, *if* it's done right. Internic PGP authentication has a really bad track record of (mostly) not working as expected. Those of you who with PGP enabled handles or readers of the guardian list are probably well aware of this :-) Just my $0.02... -- Oliver J. Albrecht AllCon GmbH http://www.allcon.net/ Network Administration Westerallee 139 Tel: +49 461 90393-0 olli(a)spike.allcon.net D-24941 Flensburg Fax: +49 461 90393-33

3 2

Re: Massive changed in the Ripe Database..
by Svetlana Tkachenko 28 Oct '98

28 Oct '98

[ Moderator note: changed local-ir(a)ripe.net -> lir-wg(a)ripe.net ] > > I think PGP-signed request (Internic for example) - good way to stop > unauthorized access to database... Why don't make "auth" attribute mandatory everywhere? Like in mntner object.

1 0

Re: Massive changed in the Ripe Database..
by IRIS-NIC 28 Oct '98

28 Oct '98

[ Moderator note: changed local-ir(a)ripe.net -> lir-wg(a)ripe.net ] On Oct 28, 4:32pm, Neil J. McRae wrote: > Subject: Re: Massive changed in the Ripe Database.. > On Tue, 27 Oct 1998 18:31:50 +0100 (CET) > Winfried Haug <haug(a)seicom.net> wrote: > > > Hello, > > > > today we noticed, that a *huge* number of Ripe Handles has been > > deleted or modified by > > > > - From: Trevor McBryan <tmcb(a)rain.fr> > > - Subject: longack > > - Date: Tue, 27 Oct 1998 13:33:35 +0000 > > - Msg-Id: <3635CBAF.2C707C44(a)rain.fr> > > > > We saw one change like this also. > We have seen other ten changes in our person objects too. -- +---------------------------------------------------------------+ | RedIRIS NIC | | Centro de Comunicaciones CSIC RedIRIS | | Serrano 142 Tel: + 34 915855150 | | 28006 Madrid Fax: + 34 915855146 | | SPAIN Email: iris-nic(a)rediris.es | +---------------------------------------------------------------+

1 0

RE: Massive changed in the Ripe Database..
by Basil V. Dolmatov 28 Oct '98

28 Oct '98

[ Moderator note: changed local-ir(a)ripe.net -> lir-wg(a)ripe.net ] It is robot message... ;) All variants contain same typo "objectso"... ;) I think, that autoresponder is set on this address... -------------------------------------- Basil (Vasily) Dolmatov dol(a)east.ru +7-095-956-4951 East Connection ISP, Moscow, Russia. (http://www.east.ru) Nick handles ;) : BVD12, DOL1-RIPE, VVD2-RIPN On Wed, 28 Oct 1998, Pierre Reynes wrote: > Oliver, > > This is the answer we got from Trevor: > > ----BEGIN PASTE---- > Sorry for the error, > > All of the RIPE database objects associated with the addresses > managed by Global One are being transferred to their responsability. > > Unfortunately, I forgot part of a filter to overlook most of the > person objectso for the migration. > > Your object has NOT been deleted if there was a maintainer; otherwise, > the other objects are being recreated. > > The RIPE hostmaster/ncc is aware of the probleme and is working with > us for the corrections. > > Cordialement, > > Trevor McBryan > > ----END PASTE--- > > Best, > Pierre REYNES > -------------------------------------------------------------- > DNS TELECOM - Votre courtier en telecommunications > Imm. La Fayette 2, place des vosges 92051 Paris la Difense 5 > Tel: +33 (0)1 41 16 84 56 Fax: +33 (0)1 49 05 46 89 > Mobile: +33 (0)6 03 91 89 14 > Mailto:preynes@dnstelecom.fr > -------------------------------------------------------------- > Les Solutions Internet Intelligentes : > http://www.dnstelecom.fr/Solutions/Internet/ > > -----Original Message----- > From: Oliver J. Albrecht [mailto:olli@spike.allcon.net] > Sent: Wednesday, October 28, 1998 10:03 AM > To: haug(a)seicom.de; local-ir(a)ripe.net > Subject: Re: Massive changed in the Ripe Database.. > > > Hi, > > On Tue, Oct 27, 1998 at 06:31:50PM +0100, Winfried Haug wrote: > > > today we noticed, that a *huge* number of Ripe Handles has been > > deleted or modified by > > > > - From: Trevor McBryan <tmcb(a)rain.fr> > > - Subject: longack > > - Date: Tue, 27 Oct 1998 13:33:35 +0000 > > - Msg-Id: <3635CBAF.2C707C44(a)rain.fr> > > I don't know what this person is up to, but he also tried to > delete one of the handles maintained by us (SS1586-RIPE). > Shortly after it happened (yesterday around 18:00 GMT) , I > sent email asking for the reason, but received no reply yet. > Maybe someone in France would like to call this gentleman > on the phone: > > person: Trevor McBryan > address: CSI Transpac > address: 12 bis rue Campagne Premiere > address: 75014 Paris > phone: +33 1 43 35 82 05 > fax-no: +33 1 43 35 82 47 > e-mail: tmcb(a)rain.fr > nic-hdl: TMCB > mnt-by: RAIN-TRANSPAC > changed: mcbryan(a)innet.lu 961205 > source: RIPE > > -- > Oliver J. Albrecht AllCon GmbH http://www.allcon.net/ > Network Administration Westerallee 139 Tel: +49 461 90393-0 > olli(a)spike.allcon.net D-24941 Flensburg Fax: +49 461 90393-33 >

1 0

Re: Massive changed in the Ripe Database..
by Marc Roger 28 Oct '98

28 Oct '98

[ Moderator note: changed local-ir(a)ripe.net -> lir-wg(a)ripe.net ] Oliver, I have received the following answer this morning: > Date: Wed, 28 Oct 1998 11:22:13 +0100 (MET) > From: Trevor McBryan <tmcb(a)mason.rain.fr> > Message-Id: <199810281022.LAA15215(a)mason.rain.fr> > To: Marc.Roger(a)belnet.be > Subject: Re: Requested RIPE database object changes (fwd) > > Sorry for the error, > > All of the RIPE database objects associated with the addresses > managed by Global One are being transferred to their responsability. > > Unfortunately, I forgot part of a filter to overlook most of the > person objectso for the migration. > > Your object has NOT been deleted if there was a maintainer; otherwise, > the other objects are being recreated. > > The RIPE hostmaster/ncc is aware of the probleme and is working with > us for the corrections. > > Cordialement, > > Trevor McBryan I think it clarifies things a bit. On Wed, 28 Oct 1998, Oliver J. Albrecht wrote: > I don't know what this person is up to, but he also tried to > delete one of the handles maintained by us (SS1586-RIPE). > Shortly after it happened (yesterday around 18:00 GMT) , I > sent email asking for the reason, but received no reply yet. > Maybe someone in France would like to call this gentleman > on the phone: -- Marc.Roger(a)belnet.be, BELNET

1 0

New Document available: RIPE-185
by RIPE NCC Document Annoucement Service 28 Oct '98

28 Oct '98

New/Revised RIPE Document Announcement -------------------------------------- A revised/new document is available from the RIPE document store. Ref: ripe-185 Title: European Internet Registry Policies and Procedures Author: RIPE Local Internet Registry Working Group Date: 26 October 1998 Obsoletes: ripe-159 Obsoleted by: Updates: Updated by: Short content description ------------------------- This document is an update to ripe-159, the European Internet Registry Policies and Procedures document. It includes policy changes agreed upon by the LIR working group and the local-ir mailing list. The main change is that an allocation only needs to be 80% used up before requesting a new one (used to be 90%). There are also minor changes to make the text in the document clearer, and to include better examples. These changes were circulated to the local-ir list several weeks ago. Accessing the RIPE document store --------------------------------- The RIPE document store is available via anonymous FTP to ftp.ripe.net, in the directory ripe/docs. The URLs for the new documents on the FTP-server are: ftp://ftp.ripe.net/ripe/docs/ripe-185.ps PostScript version ftp://ftp.ripe.net/ripe/docs/ripe-185.txt plain text version You can also access the RIPE documents in HTML format via WWW: http://www.ripe.net/docs/ripe-185.html Documents can also be retrieved from the RIPE document store using a mail server program. For more information on how to use the program, send email to <mail-server(a)ripe.net> with "send HELP" in the body text.

1 0