[db-wg] Re: AW: [local-ir at ripe.net]Proposed change of "mnt-lower:" behaviour: procedure and timelines

On Thu, Sep 18, 2003 at 01:36:16PM +0200, Bornhorst, Ludger wrote:

Dear Ludger,

> > To solve this problem, allocation objects have to be modified to include a
> > "mnt-lower" attribute. We have applied certain heuristics to determine the most
> > suitable maintainer for an allocation. If there is no maintainer, a new 
> > maintainer will be generated.
> 
> in the case of PA allocations I agree with you, to include a "mnt-lower" 
> attribute to all PA allocation objects. 
> 
> But what about PI Allocations? In order to create an appropriate route object
> for PI addresses, it is necessary to update (not create!) the ASSIGNED PI-
> inetnum with a mnt-routes attribute etc. to get through the authorization
> for the route object creation.

The proposed change in the behaviour won't affect the updates of the existing objects. It affects only the _creation_ of more-specific inetnums (inet6nums, domains).

> Is it guaranteed, that we can perform ASSIGNED PI-inetnum updates in the future?

Yes, as long as the update is authorised by "mnt-by:" of the object itself.

Hopefully this answers your question.

> 
> regards
>  Lu
> 
> Ludger Bornhorst
> ______________________________________________________________________
> 
> Deutsche Telekom AG
> T-Com Headquarters
> Network Information Center
> Ammerlander Heerstr. 138, D-26129 Oldenburg                    Hotline
> +49 441 234 4581                (phone)                +49 800 3301180
> +49 441 234 4589                (fax)                  +49 800 3301179
> ludger.bornhorst at telekom.de     (mail)       dk.call-center at telekom.de
>  

-- 
Katie Petrusha
Database Group
RIPE NCC