Hi. Should I preserve this: mnt-by: RIPE-NCC-END-MNT mnt-lower: RIPE-NCC-END-MNT in my inet6num ASSIGNED PI? And if I should, why not this forced by database update validator?
Alexander, On Mon, 2010-11-01 at 21:47 +0300, Alexander Zubkov wrote:
Hi. Should I preserve this:
mnt-by: RIPE-NCC-END-MNT mnt-lower: RIPE-NCC-END-MNT
in my inet6num ASSIGNED PI? And if I should, why not this forced by database update validator?
The RIPE-NCC-END-MNT object has the following "descr:" and "remarks:" attributes: descr: RIPE-NCC IPRA Maintainer for all direct resources remarks: Never send email to <rs-enduser@ripe.net> Local Internet Registries (LIRs)or End Users that need to update an object only maintained by this maintainer should write to <lir-help@ripe.net> If you are not a member you should send e-mail to <ncc@ripe.net>. If your object is maintained by this, you probably cannot change the maintainer even if you wanted to. :) Try e-mailing one of the two accounts there, lir-help@ripe.net or ncc@ripe.net, and I am sure you'll get the help you need. -- Shane
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? :) On 11/01/2010 10:06 PM, Shane Kerr wrote:
Alexander,
On Mon, 2010-11-01 at 21:47 +0300, Alexander Zubkov wrote:
Hi. Should I preserve this:
mnt-by: RIPE-NCC-END-MNT mnt-lower: RIPE-NCC-END-MNT
in my inet6num ASSIGNED PI? And if I should, why not this forced by database update validator?
The RIPE-NCC-END-MNT object has the following "descr:" and "remarks:" attributes:
descr: RIPE-NCC IPRA Maintainer for all direct resources remarks: Never send email to<rs-enduser@ripe.net> Local Internet Registries (LIRs)or End Users that need to update an object only maintained by this maintainer should write to<lir-help@ripe.net> If you are not a member you should send e-mail to<ncc@ripe.net>.
If your object is maintained by this, you probably cannot change the maintainer even if you wanted to. :)
Try e-mailing one of the two accounts there, lir-help@ripe.net or ncc@ripe.net, and I am sure you'll get the help you need.
-- Shane
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@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
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@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
Alexander, Thanks! On Tue, 2010-11-02 at 16:10 +0300, Alexander Zubkov wrote:
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:".
The idea here is that you should not assign blocks from PI space further, I guess. If you want to do that you should get PA space. -- Shane
On 11/02/2010 04:33 PM, Shane Kerr wrote:
Alexander,
Thanks!
On Tue, 2010-11-02 at 16:10 +0300, Alexander Zubkov wrote:
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:".
The idea here is that you should not assign blocks from PI space further, I guess. If you want to do that you should get PA space.
I've seen somewhere also that You can create assignment only if there is no more specific or less specific assignment already. So this will be forbidden by this. And this maintainers they need I think for some other purpose.
participants (2)
-
Alexander Zubkov -
Shane Kerr