Here is answer from RIPE NCC for archives.
-----------------------------
When the IPv6 PI was created, there was a disclaimer that the
LIR shoudl had provided to the End-user regarding the maitnianers
listed - see below:
If the End User wishes to cease the current contractual relationship,
they must first have a new contractual relationship in place with
either another sponsoring LIR or else with the RIPE NCC.
In either case, such contractual changes must be communicated to the
RIPE NCC
each time they occur. If such a contract is terminated and a new
contract is not realised with another sponsoring LIR or the RIPE NCC,
the resources will return by default to the RIPE NCC.
A PI object will always have:
mnt-by: RIPE-NCC-END-MNT
mnt-lower: RIPE-NCC-END-MNT
***Do not remove these lines from the object***
It should have the End User's and/or the LIR's maintainer as
"mnt-by:", "mnt-routes:", and "mnt-domains:" but never as
"mnt-lower:".
-----------------------------
On 11/02/2010 12:26 AM, Shane Kerr wrote:
> Alexander,
>> On Mon, 2010-11-01 at 22:17 +0300, Alexander Zubkov wrote:
>> My object is maintained by my maintainer also, I have no problem with
>> access to it.
>> The question was: can I delete RIPE-NCC-END-MNT? Actually, I've deleted
>> it successfully and got no error. But may be I shouldn't do that? :)
>> In these cases, the RIPE NCC gets notified, as specified in the
> "mnt-nfy:" attribute of the maintainer:
>> mnt-nfy: hm-dbm-msgs at ripe.net>> IIRC, someone periodically reads these notifications. I don't know what
> the procedure is to get the RIPE-NCC-END-MNT added in. Maybe they send
> you a mail asking you to fix it, or maybe they just add the maintainer
> back in using a database override.
>> Probably e-mailing one of the addresses listed in the "descr:" of the
> object is the best way to find the actual answer.
>> --
> Shane
>