From Daniel.Karrenberg at ripe.net Tue Nov 3 14:55:13 1992 From: Daniel.Karrenberg at ripe.net (Daniel Karrenberg) Date: Tue, 03 Nov 92 14:55:13 +0100 Subject: Common European Network Numebr Template Message-ID: <9211031355.AA00207@ncc.ripe.net> This is just to let you know that we are working on it. We are considering input from Harvard and the JNT at present. First draft should be out by the end of the week. Daniel From Daniel.Karrenberg at ripe.net Tue Nov 3 19:05:47 1992 From: Daniel.Karrenberg at ripe.net (Daniel Karrenberg) Date: Tue, 03 Nov 92 19:05:47 +0100 Subject: RIPE Database Deletions Automated Message-ID: <9211031805.AA00764@ncc.ripe.net> How to delete a RIPE database object? To delete an object from the RIPE database, please send in a normal database update for the object to be deleted including a delete attribute as the last attribute listed. In order to delete person: Daniel Karrenberg address: RIPE Network Coordination Centre (NCC) address: Kruislaan 409 address: NL-1098 SJ Amsterdam address: Netherlands phone: +31 20 592 5065 fax-no: +31 20 592 5090 e-mail: dfk at ripe.net nic-hdl: DK58 changed: ripe-dbm at ripe.net 920826 source: RIPE one would send in person: Daniel Karrenberg address: RIPE Network Coordination Centre (NCC) address: Kruislaan 409 address: NL-1098 SJ Amsterdam address: Netherlands phone: +31 20 592 5065 fax-no: +31 20 592 5090 e-mail: dfk at ripe.net nic-hdl: DK58 changed: ripe-dbm at ripe.net 920826 source: RIPE delete: karrenberg at moneymakers.inc.com person has moved The value of the delete attribute is a comment which can be used to record reasons for the deletion. It will be archived and can be used by database administrators to verify delte requests. In order to safeguard against unwanted deletions the object will only be deleted if all attributes in the delete request match those in the database. Otherwise a diagnostic will be returned to the requestor and the deletion refused. From Daniel.Karrenberg at ripe.net Thu Nov 12 12:19:07 1992 From: Daniel.Karrenberg at ripe.net (Daniel Karrenberg) Date: Thu, 12 Nov 92 12:19:07 +0100 Subject: Parts of blocks, FAQ Message-ID: <9211121119.AA13883@ncc.ripe.net> The question and answer below might be of general interest. ------- Forwarded Message Date: Wed, 11 Nov 92 16:25:11 +0100 From: Marten Terpstra Sender: Marten.Terpstra at ripe.net To: Havard.Eidnes at runit.sintef.no cc: nic at ripe.net Subject: Re: Block vs. single RIPE DB entries Havard.Eidnes at runit.sintef.no writes: * Hi, * * is it possible to both register a block and a single entry as an exception * within that block in the RIPE database, eg. * * inetnum: 192.51.0.0 - 192.51.15.0 * * and * * inetnum: 192.51.5.0 * * and the "right thing" will happen upon lookup using whois? Or is this * method of registration discouraged? It is possible, but when the database is queried for this network, both the block AND the individual entry will appear, causing confusion. The only way to solve this is by deleting the complete block, and sending in smaller blocks that have the right information. In your example if 192.51.5 has different information from all the others, what should happen is to delete the complete block, and send in updates for 192.51.0 - 192.51.4 and 192.51.5 and 192.51.6 - 192.51.15. Not very nice, but the only solution. Maybe in the future we can come up with a (even) more clever solution. - -Marten ------- End of Forwarded Message