- db-wg - mailman.ripe.net

RADB mirror is not available over the weekend
by RIPE Database Administration 15 Nov '02

15 Nov '02

[Apologies for duplicate messages] Dear Colleagues, This is to announce that due to technical problems RADB mirror will not be available today and over the weekend on RIPE Whois Server. We hope to solve the problem and make it available again early next week. We are sorry for any inconvenience. Best regards, Engin Gunduz RIPE NCC Database Group

1 0

Re: [lir-wg] ERX of v4 address space proposal
by Wilfried Woeber, UniVie/ACOnet 13 Nov '02

13 Nov '02

--On 5. november 2002 10:00 +0100 Berislav Todorovic <beri(a)eurorings.net> wrote: > On Mon, 4 Nov 2002, Andrei Robachevsky wrote: > >>> Please find attached the proposal for the ERX of IPv4 address space for >>> your review. > > Most legacy IPv4 address space was assigned directly by InterNIC. Should > we read that all those addresses will have "PI" status? Given the fact that those address blocks were distributed before the RIR and NIR / LIR structure was devised, those blocks are _administratively_ PI, or maybe "unspecified" which I consider equivalent (much like the very early LIR blocks :-) Technically, and wirth regard to services rendered by LIRs and RIRs to the holders of those blocks, I'd venture to guess that they should be offered a chance to "opt-in" to an existing LIR or ISP environment. > Secondly, who will provide reverse delegation and how can users of these > blocks affect reverse delegation changes? I guess auto-inaddr will not > work since it requires a valid RegID. Actually this is one of the aspects that I would have liked to tackle in the ERX-TF, unfortunately it looks like I might be too late to have those ideas discussed and considered, due to overload on my end for a while. One of the things we should have learned from the ASN relocation is that those parties are not in touch with the most recent administartive procedures imposed by the RIR (and why should they?), and they simply get mixed up when they suddenly receive messages from the NCC :-( Wilfried.

1 0

Maintenance work on RIPE Whois Server 13.11.2002
by RIPE Database Administration 12 Nov '02

12 Nov '02

[Apologies for duplicate messages] Dear Colleagues, Tomorrow, 13 November 2002 Wednesday, we plan maintenance work for the whois server. As part of the maintenance work the server software will be upgraded to improve server query performance. We plan to start around 06:30 UTC and finish the work till 10:30 UTC. During this maintenance period, - mail updates will be queued and automatically processed after the maintenance work. - webupdates and syncupdates will not be possible. - queries will be answered by our secondary server. We apologise for any inconvenience. Please contact <ripe-dbm(a)ripe.net> for any questions/ comments. Best Regards, Engin Gunduz RIPE NCC Database Group

1 0

[Internet-Drafts@ietf.org: [Ietf-not43] I-D ACTION:draft-ietf-crisp-iris-areg-01.txt]
by Stephane Bortzmeyer 08 Nov '02

08 Nov '02

1 0

Webupdates Release
by Can Bican 07 Nov '02

07 Nov '02

Dear Colleagues, Web based graphical user interface for updating the RIPE database, is released, and accessible from the following urls: For updating RIPE database: http://www.ripe.net/webupdates or https://www.ripe.net/webupdates For updating RIPE TEST database: http://www.ripe.net/webupdates-test or https://www.ripe.net/webupdates-test Webupdates provides a web based graphical user interface, with the functionality for: * Adding/deleting/editing objects, * Adding/deleting/changing the order of attributes in an object, * Providing password based authentication for updating. Since the latest prototype, the following improvements have been introduced: * A help page for using the interface has been added. * source: fields of new objects are now prefilled. * It is now possible to add new fields more easily via the '+' icon. * It is now possible to manipulate multi-line fields. * There are now links for querying the database and the copyright information. Your feedback is important to us. Please send any comments, suggestions, questions and criticisms to dbtools(a)ripe.net . We also provide help via e-mail through working hours. You can communicate your problems and questions about the service to ripe-dbm(a)ripe.net . Regards, -- Can Bican Database Software Engineer RIPE NCC

1 0

Major power outage in Amsterdam
by Andrei Robachevsky 07 Nov '02

07 Nov '02

Dear Colleagues, Due to some explosion/fire in a power sub-system a large part of Amsterdam lost power last night around 21:30 UTC, 7 November. This influenced the AMS-IX sites at SARA and NIKHEF. This also caused an outage for some of our external services, mainly ns.ripe.net and whois.ripe.net. We apologise for the inconvenience this might have caused. Regards, Andrei Robachevsky Chief Technical Officer RIPE NCC

1 0

Hierarchical authorisation failed, request forwarded to maintaine r ???
by Harald.Singer＠tesion.de 05 Nov '02

05 Nov '02

Hello, i have the problem to create a route-object for a customer of me. The customer will transfer his PI-Network (192.109.176.0/24, I´m CNSPLUS-MNT) from another ISP into my AS. And of course a mnt-routes:CNSPLUS-MNT exists. I need to create the new route-object, but i get the error: "Hierarchical authorisation failed, request forwarded to maintainer." I think I should be able to create such an object without assistance from another ISP. - As the ISP and I are using Crypt-PW I don´t want to send a mail with my password to this ISP (like the proposal from Daniel in this WG). - Some time ago i was able to create such objects without any assistance, what was the reason to change this behaviour? - The discussion some weeks ago doesn´t have any hints for a solution, or i missed it. - Do you have any proposal to create the object? Regards Harald -- Harald Singer Telefon: +49 (0)711/2021-847 tesion )) Telekommunikation Telefax: +49 (0)711/2021-93-847 Systemingenieur / CCIE #7326 Mobil: +49 (0)178/2021-847 Kriegsbergstrasse 11 Mail: harald.singer(a)tesion.de D-70174 Stuttgart Web: http://www.tesion.de

4 6

Hierarchical authorisation failed, request forwarded to maintaine r ???
by Marcus.Ruchti＠colt.de 05 Nov '02

05 Nov '02

Hi all, can somebody tell me why this update failed? inet-num maintainer is NONE and AS maintainer is ours ! This is an ARIN /16 network, but the /22 part of it is announced in the RIPE region.. thanks for your help!! Marcus Ruchti New FAILED: [route] 143.58.120.0/22 Hierarchical authorisation failed, request forwarded to maintainer. route: 143.58.120.0/22 descr: MAYER, BROWN, ROWE & MAW GAEDERTZ descr: ***routed per request*** origin: AS8220 mnt-by: DE-COLT-MNT changed: markb(a)de.colt.net 20020813 source: RIPE inetnum: 0.0.0.0 - 255.255.255.255 netname: IANA-BLK descr: The whole IPv4 address space country: NL admin-c: IANA1-RIPE tech-c: IANA1-RIPE status: ALLOCATED UNSPECIFIED remarks: The country is really worldwide. remarks: This address space is assigned at various other places in remarks: the world and might therefore not be in the RIPE database. mnt-by: RIPE-NCC-HM-MNT mnt-lower: RIPE-NCC-HM-MNT mnt-routes: RIPE-NCC-NONE-MNT changed: bitbucket(a)ripe.net 20010529 changed: bitbucket(a)ripe.net 20020625 source: RIPE route: 143.58.120.0/22 descr: MBRG-FFM origin: AS3320 mnt-by: DTAG-RR changed: mbt(a)nic.dtag.de 20020619 source: RIPE route: 143.58.120.0/23 descr: MBRG-FFM origin: AS8354 notify: info(a)twinwave.net mnt-by: TWINWAVE-MNT changed: g.cipollone(a)twinwave.net 20020417 source: RIPE role: Internet Assigned Numbers Authority address: see http://www.iana.org. e-mail: bitbucket(a)ripe.net admin-c: IANA1-RIPE tech-c: IANA1-RIPE nic-hdl: IANA1-RIPE remarks: For more information on IANA services remarks: go to IANA web site at http://www.iana.org. mnt-by: RIPE-NCC-MNT changed: bitbucket(a)ripe.net 20010411 source: RIPE Marcus Ruchti Internet Systemingenieur mailto:marcus.ruchti@colt.de COLT TELECOM GmbH Herriotstr. 4 D-60528 Frankfurt Fon: +49 (0) 69 / 5 66 06 - 6351 Fax: +49 (0) 69 / 5 66 06 - 6350

5 10

RE: Hierarchical authorisation failed, request forwarded to maint aine r ???
by Koepp, Karsten 05 Nov '02

05 Nov '02

Hi Harald, The database checks for matching and less specific routes first. If such a route exists (that's the case here), mnt-routes is required in this route object. And the mntners in the inetnum are being ignored. There was a lenghty discussion about the reasons of this procedure. I don't find that appropriate but maybe others can summarize why not to check the inetnum first. The outcome for me is, that whenever you want to give mnt-routes to somebody else, only do it in a route with your own AS as origin, but that's not applicable for PI. Regards Karsten > -----Original Message----- > From: Harald.Singer(a)tesion.de [mailto:Harald.Singer@tesion.de] > Sent: Monday, November 04, 2002 5:59 PM > To: db-wg(a)ripe.net > Subject: Hierarchical authorisation failed, request forwarded to > maintaine r ??? > > > Hello, > > i have the problem to create a route-object for a customer of me. The > customer will transfer his PI-Network (192.109.176.0/24, I´m > CNSPLUS-MNT) > from another ISP into my AS. And of course a > mnt-routes:CNSPLUS-MNT exists. > I need to create the new route-object, but i get the error: > "Hierarchical > authorisation failed, request forwarded to maintainer." I > think I should be > able to create such an object without assistance from another ISP. > > - As the ISP and I are using Crypt-PW I don´t want to send a > mail with my > password to this ISP (like the proposal from Daniel in this WG). > > - Some time ago i was able to create such objects without any > assistance, > what was the reason to change this behaviour? > > - The discussion some weeks ago doesn´t have any hints for a > solution, or i > missed it. > > - Do you have any proposal to create the object? > > Regards > > Harald > > -- > Harald Singer Telefon: +49 (0)711/2021-847 > tesion )) Telekommunikation Telefax: +49 (0)711/2021-93-847 > Systemingenieur / CCIE #7326 Mobil: +49 (0)178/2021-847 > Kriegsbergstrasse 11 Mail: harald.singer(a)tesion.de > D-70174 Stuttgart Web: http://www.tesion.de >

1 0

IRT object and authentication schemes
by Havard Eidnes 31 Oct '02

31 Oct '02

Hi, someone's prodded me wrt. the IRT object registration. This finally made me take a closer look at the available documentation defining this object type. I have one question (well, I may have more, but this one is the most important one, I think): In section 5 of http://www.ripe.net/ripe/docs/irt-object.html I find the following text: When adding a reference to an irt object the update of an inet[6]num should pass the following authorisation checks: * from the irt object itself as specified in one of the "auth:" attribute * from any of the mntner objects that protect the inet[6]num object (i.e. referenced using "mnt-by:" attribute). Is there a logical AND between these two items? (I think there is, but it really ought to be said explicitly, and the "should pass" phrase should be replaced by "must pass both of".) This is pretty crucial when evaluating what should be registered in the IRT object, as unwise choices (no overlap between irt auth: and mntnr auth:) on this front will at best make it very cumbersome to add IRT references to inetnum / inet6num objects, requiring nested signatures (I wonder, does the RIPE DB support that?). Oh, yes, I also think the IRT definition document needs to say a few words about what specific roles the admin-c and tech-c of an IRT object is supposed to fill. Regards, - Håvard

2 1