- db-wg - mailman.ripe.net

Updated proposal for clean-up of references by name
by Engin Gunduz 16 Jan '03

16 Jan '03

[Apologies for duplicate messages] Dear Colleagues, I'm attaching the updated proposal for automatically cleaning up the references by name in RIPE Whois Database. We have incorporated Janos's suggestions to the proposal. If no more comments come, we plan to apply the procedure described in the proposal in the first half of January, 2003. The operation should not take more than a day. We will notify the community about the actual date of the operation. Regards, Engin Gunduz ____________________________ RIPE NCC Database Group -------------- Proposed solution for cleaning up references by name and other invalid references in RIPE Whois Database Motivation: References by name and invalid references cause two main problems: 1. One reference by name in a single object locks all person and role objects with that name, that is, they cannot be deleted, because of referential integrity checks. 2. Having anything other than a NIC handle as a reference makes the implementation of whois database software considerably more complex, since the software needs to deal with these exceptions. This increases the coding time, maintenance time and testing time of the software. Classification of the inconsistencies we need to solve and proposed solutions: 1. Objects that refer to a person or role object by name. a. There is only one object with this name. 1. The referring inconsistent object is not maintained, or the maintainers of referring inconsistent object and the person/role object with this name are the same. Solution: Update the referring inconsistent object so that it will contain the NIC handle instead of the name. Add appropriate remarks and changed attributes to the object to explain the reason for update. 2. The referring object is maintained, and the maintainers are different from the maintainers of the object with the referred name (If the latter object is not maintained, then the maintainers are by definition different.) Solution: Create a role object with this name. It will list the role or person object with this name in its admin-c and tech-c attributes. Update the inconsistent object to refer to the NIC handle of this new role object. Add appropriate remarks and changed attributes to the object to explain the reason for update. b. There is no person or role object with this name: Solution: Create a person object with this name. Clearly mark this new object putting appropriate remarks attributes so that users will see it is actually a dummy object. Update the inconsistent object to refer to the NIC handle of this new person object. Add appropriate remarks and changed attributes to the object to explain the reason for update. Protect it with the inconsistent object's maintainer(s). c. There are multiple person and role objects with this name. Solution: Create a role object with this name. It will list all the other role and person objects with the same name in its admin-c and tech-c attributes. Update the inconsistent object to refer to the NIC handle of this new role object. Add appropriate remarks and changed attributes to the object to explain the reason for update. 2. Objects that refer to a non-existent NIC handle. Solution: Create a person object with that NIC handle. Clearly mark this new object so that users will see it is actually a dummy object. Name it "person: Place Holder Object". Protect it with the inconsistent object's maintainer(s). Note that there is no need to update the inconsistent object itself. 3. Objects that refer to a string which is neither a name, nor a NIC handle. For example, it might be a phone number in admin-c attribute, or it might be 'Gunduz', a string that can't be a NIC handle, as it's longer than 4 letters, nor can it be a name as it has only one word. Another example could be "Mr. Gunduz", which enters this category because "Mr" can't appear in a name of person/role object. Solution: Create a person object for each such reference. Name the object "person: Place Holder Object" and list the object that refers to it in its remarks attribute. Protect it with inconsistent object's maintainer(s). Then update the inconsistent object to refer to the NIC handle of this new place holder person object. In each case an object is updated, or created, send appropriate notifications (determined by "mnt-by" and "notify" attributes, as with all other updates). Please note that this proposal does not actually solve the problem of invalid contact information-- rather, it makes the data set more uniform, thus decreases the administration and development time of the whois database.

1 2

RE: [lir-wg] should aut-num object for IPv4 & IPv6 be the same?
by adrian.pauling＠bt.com 15 Jan '03

15 Jan '03

we have 'inet6num' objects separate to 'inetnum' to distinguish IPv6 address assignments from IPv4. Is the question should different 'peering-set' 'route' objects etc reflect different peerings for IPv6 from IPv4 that an assigned AS can have? This scenario is real as I can easily give a current (enterprise LIR) example. Regards, Adrian F Pauling BT Ignite Solutions

2 1

Implementing additional IPV4 Table into RIPEDB-Software (local use only)
by Arnd Vehling 08 Jan '03

08 Jan '03

Hello, i need to introduce a new IP V4 Table into the current release of the ripe-db software for a local project at Cable&Wireles. The best starting point for impletenting this is probably the definition of the current ipv4 definition of "inetnum" in attributes.xml. Befor i go ahead and start reading through tons of sourcecode, especially the one used for radix-tree operations, i thought i might ask here if someone has any general tips on what to change/not to change. Comment on the current definition if the inetnum object would also be of great help to me. I.e. which attributes to copy and which need to be changed etc. best regards, Arnd Vehling -- NetHead Network Design and Security Arnd Vehling av(a)nethead.De Gummersbacherstr. 27 Phone: +49 221 8809210 50679 Köln Fax : +49 221 8809212

1 0

ANNOUNCEMENT: ROUTING REGISTRY TRAINING COURSES
by RIPE NCC Training 20 Dec '02

20 Dec '02

Dear colleagues, [apologies for duplicate postings] As a new service to its members the RIPE NCC offers the "Routing Registry Training Courses". The main objective of the "Routing Registry Training Course" is to familiarise the LIRs with the features of the Routing Registry, while introducing the relevant tools and services of the RIPE NCC. The course also offers practical exercises. OVERVIEW OF TOPICS COVERED IN THE COURSE: - Routing Registry as a part of the RIPE Whois Database and the Internet Routing Registry (IRR) - Specifying routing policies using RPSL (Routing Policy Specification Language) and the RtConfig tool - IRRToolSet - Routing Information Service (RIS) - Routing Registry Consistency Check Project Please note that this is an advanced course, it will: - NOT teach the basics of routing. - NOT describe how to receive Internet resources from the RIPE NCC, nor how to operate a Local Internet Registry (LIR) The target audience of the course are technical staff of LIRs: e.g. network operators, engineers etc. This course is not intended for administrative or management staff (e.g. hostmasters) . It is assumed that all attendees will be familiar with BGP routing and with the RIPE DB (creating/modifying objects). This course is based on interactive exercises in a local network set-up. Please bring your laptops equipped with: - Working Ethernet card, - 3 meters of Ethernet cable, - Secure connection client, - Web browser. Please be prepared to share your laptop (or at least allow another attendee to "look over your shoulder") if necessary. The Routing Registry Training Course is conducted in the English language and is free of charge, since it is covered by the membership contribution. More information about the Routing Registry Training Courses can be found at: http://www.ripe.net/training/rr/ REGISTRATION: You can register for a course at the following URL: http://www.ripe.net/cgi-bin/trainingform.pl.cgi Or by completing the registration form at the end of this email and replying to <training(a)ripe.net> . In order to register for a Routing Registry Training Course you must be an employee of an LIR and either : - be an LIR contact - be confirmed by an LIR contact. LIR contacts are those employees of an LIR who are registered with RIPE NCC as authoritative contact persons. It is expected that most of those interested in the "Routing Registry Training Course" will not be an authoritative contact persons for their LIR, therefore will be refused by the course registration "robot". In order to be admitted to the course, confirmation email need to be send to <training(a)ripe.net> . Please approach the LIR contacts from your organisation personally, since the identity of LIR contacts is confidential, and the RIPE NCC is unable to divulge contact persons for any given LIR. Kind Regards, The RIPE NCC Training Team ----------------------------------------------------------------------- COURSE DATES AND VENUES ======================== Date: Friday 24th Janaury 2003 Time: 0900 - 1700 Location: Amsterdam, Netherlands AND: Date: Wednesday 12th March 2003 Time: 0900 - 1700 Location: London, United Kingdom ------------------------------------------------------------------------ REGISTRATION FORM ================= %START PART 1 - Registration 1) Your name Enter First name, Last name in full e.g. John Doe Mary-Beth Walton # NAME [ ] 2) Your Registry ID (format: country-code.<name of registry>) # REG [ ] 3) Your e-mail address # EMAIL [ ] 4) Your NIC handle (optional) # NICHANDLE [ ] 5) The Course you plan to attend (date and location) # COURSE [ ] %END

2 2

Proposal: key-cert update procedure change
by Dmitry Morozovsky 17 Dec '02

17 Dec '02

Dear colleagues, changing today our key-cert objects, I'd encounter a bit of inconvenience: one can't cut'n'paste key-cert object from whois request: [s]he should manually delete method/owner/fingerpr attributes. My suggestion is: if one of r/o attributes exists in the object processed, DB should check whether auto-computed value of the attribute matches supplied value; - if yes, no error/warning should be produced - if no -- it should of course be reported; I think, it's up to the community to decide whether this condition should be treated as error or simply as warning. I think, the same procedure should be also applied to other de-facto read-only attributes, such as person name in person object. Sincerely, D.Marck [DM5020, DM268-RIPE, DM3-RIPN] ------------------------------------------------------------------------ *** Dmitry Morozovsky --- D.Marck --- Wild Woozle --- marck(a)rinet.ru *** ------------------------------------------------------------------------

2 2

Re: [db-wg] Proposal for automated clean-up of references by name
by Janos Zsako 05 Dec '02

05 Dec '02

> From db-wg-admin(a)ripe.net Thu Dec 5 11:08:46 2002 > From: Gert Doering <gert(a)space.net> > On Thu, Dec 05, 2002 at 10:42:53AM +0100, Engin Gunduz wrote: > > We have prepared a proposal to automatically clean-up references > > by name and other invalid references in RIPE Whois Database. > > I like the proposal. Go ahead! Yes, I agree too. > (Yes, it will potentially create lots of "ugly looking" objects - but > the situation right now, where you're not able to delete person objects > because they are locked by a reference-by-name, is much worse) I have one question though: who will be the maintainer of the new "ugly" object created? I have the feeling it could/should be the maintainer of the object that will reference it. Janos

1 0

Proposal for automated clean-up of references by name
by Engin Gunduz 05 Dec '02

05 Dec '02

[Apologies for duplicate messages] Dear Colleagues, We have prepared a proposal to automatically clean-up references by name and other invalid references in RIPE Whois Database. The proposal aims at fixing objects like (as an hypothetical example): inetnum: 58.210.0.0 - 58.210.255.255 netname: EXAMPLE-OBJECT descr: Example inconsistent object country: EU admin-c: Engin Gunduz tech-c: Engin Gunduz status: ASSIGNED PA mnt-by: RIPE-NCC-NONE-MNT changed: engin(a)ripe.net 19940508 source: RIPE Note that in admin-c and tech-c attributes there are names, instead of NIC handles, which is currently regarded as a syntax error. Such objects were introduced into RIPE Whois Database when the syntax checks were not as strict as today. There are 2114 (out of approximately 2 million references) such invalid references as of December 2nd, 2002. The proposal will affect only the objects that have invalid references where a NIC handle should be used. Please see http://www.ripe.net/db/dbconstat/ for more information on Database Consistency and Statistics Project which deals with this and other types of inconsistencies in RIPE Database. Please find our proposal below. We would like to discuss the proposal until December 20th, 2002, at which date we will sum up the discussion, and perhaps begin to implement the resulting solution. Regards, Engin Gunduz RIPE NCC Database Group -------------- Proposed solution for cleaning up references by name and other invalid references in RIPE Whois Database Motivation: References by name and invalid references cause two main problems: 1. One reference by name in a single object locks all person and role objects with that name, that is, they cannot be deleted, because of referential integrity checks. 2. Having anything other than a NIC handle as a reference makes the implementation of whois database software considerably more complex, since the software needs to deal with these exceptions. This increases the coding time, maintenance time and testing time of the software. Classification of the inconsistencies we need to solve and proposed solutions: 1. Objects that refer to a person or role object by name. a. There is only one object with this name. Solution: Update the inconsistent object so that it will contain the NIC handle instead of the name. Add appropriate remarks and changed attributes to the object to explain the reason for update. b. There is no person or role object with this name: Solution: Create a person object with this name. Clearly mark this new object putting appropriate remarks attributes so that users will see it is actually a dummy object. Update the inconsistent object to refer to the NIC handle of this new person object. Add appropriate remarks and changed attributes to the object to explain the reason for update. c. There are multiple person and role objects with this name. Solution: Create a role object with this name. It will list all the other role and person objects with the same name in its admin-c and tech-c attributes. Update the inconsistent object to refer to the NIC handle of this new role object. Add appropriate remarks and changed attributes to the object to explain the reason for update. 2. Objects that refer to a non-existent NIC handle. Solution: Create a person object with that NIC handle. Clearly mark this new object so that users will see it is actually a dummy object. Name it "person: Place Holder Object". Note that there is no need to update the inconsistent object itself. 3. Objects that refer to a string which is neither a name, nor a NIC handle. For example, it might be a phone number in admin-c attribute, or it might be 'Gunduz', a string that can't be a NIC handle, as it's longer than 4 letters, nor can it be a name as it has only one word. Another example could be "Mr. Gunduz", which enters this category because "Mr" can't appear in a name of person/role object. Solution: Create a person object for each such reference. Name the object "person: Place Holder Object" and list the object that refers to it in its remarks attribute. Then update the inconsistent object to refer to the NIC handle of this new place holder person object. In each case an object is updated, send appropriate notifications (determined by "mnt-by" and "notify" attributes, as with all other updates). Please note that this proposal does not actually solve the problem of invalid contact information-- rather, it makes the data set more uniform, thus decreases the administration and development time of the whois database.

2 1

Re: [lir-wg] Re: ERX of v4 address space proposal
by Andrei Robachevsky 20 Nov '02

20 Nov '02

Peter Galbavy wrote: > 192.0.0.0/8 ? > > The swamp is coming to RIPE or which poor RIR ? Our current data shows that around 753 networks will go to APNIC, 9072 stay with ARIN, 92 will go to LACNIC and 3176 to RIPE NCC. 192/8 will be processed as last and sweet piece, and statistics will be updated. > > Peter Regards, Andrei > > ----- Original Message ----- > From: "Andrei Robachevsky" <andrei(a)ripe.net> > To: <db-wg(a)ripe.net>; <lir-wg(a)ripe.net> > Sent: Wednesday, November 20, 2002 1:54 PM > Subject: [lir-wg] Re: ERX of v4 address space proposal > > > >>Dear Colleagues, >> >>You may find a list of networks (/8's) containing allocations that will >>be transferred by the ERX project at the following URL: >>http://www.ripe.net/db/erx/erx-ip/ >> >>A detailed list of which networks will be transferred, and to which RIR, >>will be posted before each /8 is transferred. A full schedule for each >>network will also be published for each /8. >> >>Regards, >> >>Andrei Robachevsky >>CTO, RIPE NCC >> >> >

1 0

ERX of v4 address space proposal
by Andrei Robachevsky 20 Nov '02

20 Nov '02

Dear Colleagues, Please find attached the proposal for the ERX of IPv4 address space for your review. This proposal was reviewed by the ERX-Taskforce that was set-up at the RIPE 43 meeting. Comments received were summarised and sent to both Database and LIR Working Group mailing lists. We would appreciate your feedback on this proposal no later than Wednesday, 13 November 2002. A timeline for this project will be issued along with final project description. Regards, Andrei Robachevsky RIPE NCC ERX of v4 address space ----------------------- INTRODUCTION When ARIN began operations, it inherited classful blocks of addresses ("legacy" space) that were issued to organisations not in ARIN's region. The Regional Internet Registries (RIRs) are co-ordinating the transfer of these records from the ARIN Database to RIPE Database or APNIC Database, as appropriate. This is based on geographic location of each resource holder. The affected records include class B networks and class C ranges, particularly those issued from 192/8. ARIN also maintains reverse delegation for all legacy address space. Once the transfer is complete, this responsibility will be distributed among the RIRs according to their respective regions. BENEFITS This will enable resource holders to maintain all their records in one database and End Users to interface with just one RIR for all database and reverse delegation matters. This effort will also help to locate address holders and recover unused or underutilised address space. IMPACT ON RESOURCE HOLDERS Entities holding legacy space to be transferred can expect the process to be largely transparent. While it will not affect network status in any way, resource holders might be required to create contact identifiers with the proper registry if they do not already exist. Queries made in WHOIS for an IP block that has been transferred to another RIR will be directed to the appropriate RIR. APPROACH The plan is to perform the transfer by /8. For each /8 the following tasks have to be performed: 1. Conflicts (contacts and description) to be resolved 2. Records and associated documentation to be transferred 3. Reverse delegation to be set up A total of 47 /8's with 8030 records have to be transferred. CONFLICTS The following types of conflicts have been identified: C1. Record exists in ARIN DB only. There is no exact matching (range wise) record in the RIPE DB. Proposal: to update internal documentation, create the record in the RIPE DB and protect with a unique generated mntner. C2. Range matches records in both ARIN and RIPE DBs. Meaning that contact and description may be different. Most cases indicate out of date information in one of the Databases, not real conflicts or attempts to hijack address space. What happened in most cases is that people started maintaining their allocation or assignement in the RIPE DB, especially since RIPE DB started to support the Routing Registry. Proposal: Notify conflicts and give time to reach consensus. After the deadline merge those who haven't responded, but _do_not_lock_ (keep the same mntner). C3.0 Record exists in the RIPE DB only. C3.1. One reason why such situation may exist is that this is a valid RIPE NCC allocation. Proposal: To preserve information in the RIPE DB. C3.2 Another situation is that the registration data are simply garbage. Proposal: Notify, give time for explanations and clean up in the end. PROCEDURE for a /8 1. Pre transfer 1.1 Initial dump is prepared for transfer by ARIN 1.2 Announcement is sent to ARIN's contacts 1.3 Reverese delegation domain space is cleaned up in the RIPE DB (reverse domain objects for which no delegation was provided are deleted) 2. Transfer 2.1 Final dump is prepared by ARIN 2.2 C1 group: database records are imported, documentation is updated, contacts are notified 2.3 C2 group: contacts (ARIN+RIPE) are asked to reach consensus. 2.4 C3.2 group: contacts are notified of possible deletion. 2.5 DNS is updated: domain objects are generated, zone (full or partial) is generated. 3. Conflict resolution 3.1 C2 group: non responding records are merged but _not_locked_. 3.2 C3.2 group: records without good reasons are deleted. -------

4 7

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

Summary of ERX-TF discussion
by leo vegoda 29 Oct '02

29 Oct '02

Dear Colleagues, As promised, here is a summary of the short discussion had on the <erx-tf(a)ripe.net> mailing list over the last few weeks. There have been about 15 messages in total. On 10 October we published the RIPE NCC's proposed ERX process for IPv4 to the Task Force. There were two technical queries: a request for confirmation that all contacts in both databases be e-mailed. Also, there was a request for confirmation on how reverse delegations would be handled. Substantive issues included a question on how early registrations would be handled from a policy point of view. The RIPE NCC confirmed that in the past, the majority of registrants have agreed to meet the current policy requirements for registration. However, we also noted that previous registrations have tended to be done for organisations who place a value on registration data. It was argued that the policy issues were less important than the accuracy of the registration data transferred/updated. No other issues on the transfer process were raised. It appears that the Task Force is happy with the proposed transfer process. As such, we would like to publish the proposed process in the next few days. Regards, -- leo vegoda RIPE NCC Registration Services

1 0

Improved Query Processing on RIPE Database Serve
by RIPE Database Administration 24 Oct '02

24 Oct '02

[ Apologies for multiple copies. ] Colleagues, Whois query processing for the RIPE Database Server has been revised to be more consistent and helpful to users. In the past, the server would make a number of changes to the user query without telling the user, for example removing characters that it did not understand or truncating the query. The new implementation will perform exactly the query the user requested, if possible, and give errors when not. Warnings are now returned where appropriate. A full description of the changes may be found here: http://www.ripe.net/db/whois-query-2002.html In general, all correct queries will provide exactly the same results as on the previous version of the server. If you have any questions please send them to <ripe-dbm(a)ripe.net>. Suggestions may be sent to <ripe-dbm(a)ripe.net>, or discussed on the RIPE Database working group mailing list, details of which may be found here: http://www.ripe.net/ripe/wg/db/index.html -- Shane Kerr RIPE NCC

1 0

[Ted.Hardie@nominum.com: [Ietf-not43] Working Group Last Call: draft-ietf-crisp-requirements-01.txt]
by Stephane Bortzmeyer 16 Oct '02

16 Oct '02

This is also for address registries like RIPE-NCC so I believe everybody should read this post-whois document and comment before the Atlanta meeting.

1 0

RE: FAILED update.
by Pieterjan d'Hertog 14 Oct '02

14 Oct '02

> > -----Mensaje original----- > > De: Iglesias Fuente, Jesus > > Enviado el: viernes 11 de octubre de 2002 13:09 > > Para: 'auto-rpsl(a)ripe.net' > > Asunto: longack > > > > password: 7djsfy25ddn > > Please change your update password :-) --- Pieterjan d'Hertog, Senior Network Engineer Belgacom Skynet NV/SA, 2 Rue Carli, B-1140 Brussels Phone +3227061311 Fax +3227061150 http://www.skynet.be PGP fingerprint: D9AB CD6A 2A78 73CC 68BF 0AFA 8FB3 5821 E4BB 9D2E

1 0

Re: NCC#2002102136 RV: FAILED update.
by RIPE Database Administration 14 Oct '02

14 Oct '02

Dear Jesus Iglesias, [Please send any operational problems/doubts with the RIPE database to ripe-dbm(a)ripe.net , this is the best address to have your doubts answered]. The failure of your update is related to the fact that you have sent your object quoted: > as-set: AS-BTTEL > descr: BT Telecomunicaciones customers > members: AS8903 > ... Please don't quote the objects, ie send like as-set: AS-BTTEL descr: BT Telecomunicaciones customers members: AS8903 ... Also, we recommend never to send your password in the clean in mail messages, especially to public mailing lists. If you have any more questions, please contact <ripe-dbm(a)ripe.net>. Regards, Tiago Antao ____________________________ RIPE Database Administration. Original message follows: ------------------------ > Hello, > Can anyone tell me why did this update fail? > The robot answered: > > Update FAILED: Syntax error in object > ***Error: Error with class attribute, class invalid > > Thanks for your help ! > Regards. > > _________________________________ > Jes�s Iglesias Fuente > IP Platforms & Services (Planning) > BT Ignite Spain > jesus.iglesias(a)ignite.com > Phone: (+34) 91.270.62.14 > Fax: (+34) 91.270.63.10 > _____________________________________________ > > > -----Mensaje original----- > De: Iglesias Fuente, Jesus > Enviado el: viernes 11 de octubre de 2002 13:09 > Para: 'auto-rpsl(a)ripe.net' > Asunto: longack > > password: *********************** > > as-set: AS-BTTEL > descr: BT Telecomunicaciones customers > members: AS8903 > members: AS3324, AS21025 > members: AS12334, AS20784 > members: AS12356, AS12636 > members: AS8239, AS12430 > members: AS12845, AS21268 > members: AS9192, AS13066 > members: AS13143, AS15734 > members: AS12946, AS15369 > members: AS15912, AS15937 > members: AS15963, AS16373 > members: AS16203, AS13205 > members: AS20815, AS20944 > members: AS16371, AS21368 > members: AS21193, AS20718 > members: AS20760, AS20607 > members: AS24830, AS21181 > members: AS15919, AS25267 > remarks: BT Telecomunicaciones customers ASs > tech-c: BTT2-RIPE > admin-c: EL729-RIPE > notify: opsingguar(a)bt.es > mnt-by: BTTEL-MNT > changed: jesus.iglesias(a)bt.es > source: RIPE > > > aut-num: AS8903 > as-name: BT > descr: BT Tel AS 1 > import: from AS701 action pref=100; accept ANY > import: from AS5400 action pref=100; accept ANY > import: from AS3561 action pref=100; accept ANY > import: from AS2856 action pref=100; accept ANY > import: from AS6895 action pref=100; accept AS6895 > import: from AS3262 action pref=100; accept AS3262 > import: from AS8761 action pref=100; accept AS8761 > import: from AS8782 action pref=100; accept AS8782 > import: from AS8220 action pref=100; accept AS8220 > import: from AS4589 action pref=100; accept AS4589 > import: from AS12457 action pref=100; accept AS12457 > import: from AS12357 action pref=100; accept AS12357 > import: from AS6897 action pref=100; accept AS6897 > import: from AS12479 action pref=100; accept AS12479 > import: from AS12852 action pref=100; accept AS12852 > import: from AS2686 action pref=100; accept AS2686 > import: from AS3352 action pref=100; accept AS3352 > import: from AS3324 action pref=100; accept AS3324 > import: from AS2134 action pref=100; accept AS2134 > import: from AS12359 action pref=100; accept AS12359 > import: from AS3352 action pref=100; accept AS3352 > import: from AS13041 action pref=100; accept AS13041 > import: from AS12386 action pref=100; accept AS12386 > import: from AS9019 action pref=100; accept AS9019 > import: from AS5978 action pref=100; accept AS5378 > import: from AS12482 action pref=100; accept AS12482 > import: from AS9106 action pref=100; accept AS9106 > import: from AS12715 action pref=100; accept AS12715 > import: from AS702 action pref=100; accept AS702 > import: from AS3247 action pref=100; accept AS-3247 > import: from AS766 action pref=100; accept AS-766 > import: from AS3257 action pref=100; accept AS-NACAMAR > import: from AS6669 action pref=100; accept AS-BTES > import: from AS3324 action pref=100; accept AS3324 > import: from AS12334 action pref=100; accept AS12334 > import: from AS12356 action pref=100; accept AS12356 > import: from AS8239 action pref=100; accept AS8239 > import: from AS12430 action pref=100; accept AS12430 > import: from AS12636 action pref=100; accept AS12636 > import: from AS12845 action pref=100; accept AS12845 > import: from AS12946 action pref=100; accept AS12946 > import: from AS9192 action pref=100; accept AS9192 > import: from AS13066 action pref=100; accept AS13066 > import: from AS13143 action pref=100; accept AS13143 > import: from AS15369 action pref=100; accept AS15369 > import: from AS15734 action pref=100; accept AS15734 > import: from AS15912 action pref=100; accept AS15912 > import: from AS15937 action pref=100; accept AS15937 > import: from AS15963 action pref=100; accept AS15963 > import: from AS16373 action pref=100; accept AS16373 > import: from AS16203 action pref=100; accept AS16203 > import: from AS13205 action pref=100; accept AS13205 > import: from AS21025 action pref=100; accept AS21025 > import: from AS20815 action pref=100; accept AS20815 > import: from AS20784 action pref=100; accept AS20784 > import: from AS20944 action pref=100; accept AS20944 > import: from AS16371 action pref=100; accept AS16371 > import: from AS21368 action pref=100; accept AS21368 > import: from AS21268 action pref=100; accept AS21268 > import: from AS21193 action pref=100; accept AS21193 > import: from AS20718 action pref=100; accept AS20718 > import: from AS20607 action pref=100; accept AS20607 > import: from AS20760 action pref=100; accept AS20760 > import: from AS24830 action pref=100; accept AS24830 > import: from AS21181 action pref=100; accept AS21181 > import: from AS15919 action pref=100; accept AS15919 > import: from AS25267 action pref=100; accept AS25267 > export: to AS701 announce AS-BTTEL > export: to AS5400 announce AS-BTTEL > export: to AS3561 announce AS-BTTEL > export: to AS2856 announce AS-BTTEL > export: to AS6669 announce AS-BTTEL AS-BTTELESPANIX AS-BTTELCATNIX > export: to AS2134 announce AS-BTTEL AS-BTES > export: to AS2686 announce AS-BTTEL AS-BTES > export: to AS3262 announce AS-BTTEL AS-BTES > export: to AS3324 announce AS-BTTEL AS-BTES > export: to AS3352 announce AS-BTTEL AS-BTES > export: to AS6895 announce AS-BTTEL AS-BTES > export: to AS6897 announce AS-BTTEL AS-BTES > export: to AS8761 announce AS-BTTEL AS-BTES > export: to AS8220 announce AS-BTTEL AS-BTES > export: to AS4589 announce AS-BTTEL AS-BTES > export: to AS12457 announce AS-BTTEL AS-BTES > export: to AS12357 announce AS-BTTEL AS-BTES > export: to AS12479 announce AS-BTTEL AS-BTES > export: to AS12359 announce AS-BTTEL AS-BTES > export: to AS8782 announce AS-BTTEL AS-BTES > export: to AS12852 announce AS-BTTEL AS-BTES > export: to AS13041 announce AS-BTTEL AS-BTES > export: to AS12386 announce AS-BTTEL AS-BTES > export: to AS9019 announce AS-BTTEL AS-BTES > export: to AS8761 announce AS-BTTEL AS-BTES > export: to AS12482 announce AS-BTTEL AS-BTES > export: to AS3262 announce AS-BTTEL AS-BTES > export: to AS9106 announce AS-BTTEL AS-BTES > export: to AS12715 announce AS-BTTEL AS-BTES > export: to AS5378 announce AS-BTTEL AS-BTES > export: to AS3257 announce AS-BTTEL AS-BTES > export: to AS702 announce AS-BTTEL AS-BTES > export: to AS3247 announce AS-BTTEL AS-BTES > export: to AS766 announce AS-BTTEL AS-BTES > export: to AS12334 announce ANY > export: to AS12356 announce ANY > export: to AS8239 announce ANY > export: to AS12430 announce ANY > export: to AS12636 announce ANY > export: to AS12845 announce ANY > export: to AS9192 announce ANY > export: to AS13066 announce ANY > export: to AS3324 announce ANY > export: to AS13143 announce ANY > export: to AS15734 announce ANY > export: to AS12946 announce ANY > export: to AS15369 announce ANY > export: to AS15912 announce ANY > export: to AS15937 announce ANY > export: to AS15963 announce ANY > export: to AS16373 announce ANY > export: to AS16203 announce ANY > export: to AS13205 announce ANY > export: to AS21025 announce ANY > export: to AS20815 announce ANY > export: to AS20784 announce ANY > export: to AS20944 announce ANY > export: to AS16371 announce ANY > export: to AS21368 announce ANY > export: to AS21268 announce ANY > export: to AS21193 announce ANY > export: to AS20718 announce ANY > export: to AS20607 announce ANY > export: to AS20760 announce ANY > export: to AS24830 announce ANY > export: to AS21181 announce ANY > export: to AS15919 announce ANY > export: to AS25267 announce ANY > admin-c: EL729-RIPE > tech-c: BTT2-RIPE > notify: opsingguar(a)bt.es > mnt-by: BTTEL-MNT > changed: jesus.iglesias(a)bt.es > source: RIPE > ********************************************** Noticia legal Este mensaje electr�nico contiene informaci�n de BT Ignite Espa�a S.A.U. que es privada y confidencial, siendo para el uso exclusivo de la persona (s) o entidades arriba mencionadas. Si usted no es el destinatario se�alado, le informamos que cualquier divulgaci�n, copia, distribuci�n o uso de los contenidos est� prohibida. Si usted ha recibido este mensaje por error, por favor borre su contenido lo antes posible. Gracias.

1 0

RE: RV: FAILED update.
by Wilfried Woeber, UniVie/ACOnet 14 Oct '02

14 Oct '02

> Hello, > Can anyone tell me why did this update fail? > The robot answered: > ... >********************************************** >Noticia legal >Este mensaje electrónico contiene información de BT Ignite España S.A.U. que >es privada y confidencial, siendo para el uso exclusivo de la persona (s) o >entidades arriba mencionadas. Si usted no es el destinatario señalado, le >informamos que cualquier divulgación, copia, distribución o uso de los >contenidos está prohibida. Si usted ha recibido este mensaje por error, por >favor borre su contenido lo antes posible. >Gracias. Sorry, I am not dealing with mails containing legal disclaimers or privacy restrictions (regardless of the language they are written in ;-) -WW

1 0