more authority for mnt-lower in the allocation objects
Hi Lir-WG, this is a hostmasters argument upon my question why I am not able to change the contacts and mnt-routes in my own allocation by myself. I am interested if somebody else is sharing my opinion. Hostmasters argument: "It is not possible for you to update an allocation object because RIPE NCC is the maintainer of these objects, which makes sense. :)" This is my opinion: Yes, it makes sence that RIPE NCC is the maintainer of a LIRs allocation. But in my opinion it makes NO sence that Cable and Wireles (and all other LIRs) as mnt-lower do not have the authority to change their own administrative and technical contacts in the allocation. There must be an restricted authority for a mnt-lower to change things like that by their own. I think especially about following attributes: (marked with +++) inetnum: 62.208.0.0 - 62.208.255.255 netname: DE-ECRC-970502 descr: ECRC GmbH country: DE +++++admin-c: EN65-RIPE +++++tech-c: EN65-RIPE status: ALLOCATED PA mnt-by: RIPE-NCC-HM-MNT mnt-lower: CW-EUROPE-GSOC +++++mnt-routes: CW-EUROPE-GSOC changed: hostmaster@ripe.net 20010814 source: RIPE In my opiniom it makes no sence that for a very simple change in the allocation, that does actually not affect the allocation itself we have to send requests to the hostmasters and wait sometimes weeks for their handling. I think that persons that stand behind the respective reg-id should have this authority. Best regards, Tanja Heimes -- Tanja Heimes / IP Engineer E-Mail Tanja.Heimes@de.cw.com Cable & Wireless Deutschland GmbH TEL. + 49 89 92699-0 Landsberger Strasse 155 Fax. + 49 89 92699-810 D-80687 Munich, Germany web: http://www.cw.com/de
Hi, Tanja Heimes wrote: [..]
This is my opinion: Yes, it makes sence that RIPE NCC is the maintainer of a LIRs allocation. But in my opinion it makes NO sence that Cable and Wireles (and all other LIRs) as mnt-lower do not have the authority to change their own administrative and technical contacts in the allocation.
IMO this is correct. The LIR should be able to modify this information without needing to write to hostmaster@ripe.net (which may take some time depending on how busy the hostmaster team is). admin-c, tech-c, mnt-lower and mnt-routes within an allocation should be changeable by the LIR itself. I know this is difficult to accomplish while "mnt-by:" points to an ripe-maintainer. But as far as i know RIPE has a second database where all allocations are stored for cross-checlking. Therefore we could take an approach where the allocation may only be created by RIPE but may be updated by the according LIR. This can simply be accomplished by removing the RIPE-Maintainer from the object after creation and change it to the according maintainer of the LIR. regards, Arnd Vehling -- NetHead Network Design and Security Arnd Vehling av@nethead.De Gummersbacherstr. 27 Phone: +49 221 8809210 50679 Cologne, Germany Fax : +49 221 8809212
Tanya, The RIPE NCC maintains all the allocations it makes as it is responsible for them. We expect most LIRs will want to maintain all their assignments for the same reason. We agree that it is desirable for LIRs to be able to control the contact information in their allocation inetnum objects as well as the mainatiners used for hierarchical authorisation. As Joao wrote a few days ago, we want to provide the RIPE NCC membership with ways of accessing and modifying their own data using currently avaiable technologies such as a secure web site. These systems are being developed at the moment. As Karsten points out, there is no easy way to add mnt-routes attributes to inetnum objects for allocations where the LIR's maintainer is not already referenced as a mnt-lower. Of course, where LIRs already have role objects referenced they can update the contacts in the role and have no need to contact RIPE NCC. The new systems we are developing are one way we intend to reduce the workload carried out by the Registration Services department and to help provide a speedier service to our customers. Regards, -- leo vegoda RIPE NCC
Hi Leo, good that RIPE is aware of this problem. in concern: Of course, where LIRs already have role objects referenced they
can update the contacts in the role and have no need to contact RIPE NCC.
In our case we have a old role object that is not in use anymore EN65-RIPE and I want to change it to the new one. For that in this situation I have to contact the hostmasters. The same I have to do with all other allocations of aquired ISPs. In much of them I am already a reg-id contact in our maintainer is stated in the objetcs. In all this allocations I have to change to contacts/roles. An update of the contacts/roles in this cases is not relevant but an completely exchange to a new one. Tanja leo vegoda wrote:
Tanya,
The RIPE NCC maintains all the allocations it makes as it is responsible for them. We expect most LIRs will want to maintain all their assignments for the same reason.
We agree that it is desirable for LIRs to be able to control the contact information in their allocation inetnum objects as well as the mainatiners used for hierarchical authorisation. As Joao wrote a few days ago, we want to provide the RIPE NCC membership with ways of accessing and modifying their own data using currently avaiable technologies such as a secure web site. These systems are being developed at the moment.
As Karsten points out, there is no easy way to add mnt-routes attributes to inetnum objects for allocations where the LIR's maintainer is not already referenced as a mnt-lower.
Of course, where LIRs already have role objects referenced they can update the contacts in the role and have no need to contact RIPE NCC.
The new systems we are developing are one way we intend to reduce the workload carried out by the Registration Services department and to help provide a speedier service to our customers.
Regards,
-- leo vegoda RIPE NCC
-- Tanja Heimes / IP Administrator E-Mail Tanja.Heimes@de.cw.com Cable & Wireless Deutschland GmbH TEL. + 49 89 92699-0 Landsberger Strasse 155 Fax. + 49 89 92699-810 D-80687 Munich, Germany web: http://www.cw.com/de
Hello, leo vegoda wrote:
The RIPE NCC maintains all the allocations it makes as it is responsible for them.
You maintain a copy of the allocations within a seperate second db as far as i know?! You can always make cross checks t confirm the allocations are valid. For the RIPE it should be sufficient to be able to create and delete an inetnum object with status = ALLOCATED (i.e. an allocation). The LIRS should be able to change the mentioned attributes like mnt-by, mnt-lower, mnt-routes. The changes to the ripe-software for this are minimal. Therefore i dont see why it shouldnt be possible to commit such a change. best regards, Arnd Vehling -- NetHead Network Design and Security Arnd Vehling av@nethead.De Gummersbacherstr. 27 Phone: +49 221 8809210 50679 Cologne, Germany Fax : +49 221 8809212
participants (3)
-
Arnd Vehling -
leo vegoda -
Tanja Heimes