From green at msu.ru Mon Nov 1 19:47:16 2010 From: green at msu.ru (Alexander Zubkov) Date: Mon, 01 Nov 2010 21:47:16 +0300 Subject: RIPE-NCC-END-MNT in IPv6 PI Message-ID: <4CCF0B34.6020806@msu.ru> 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? From shane at time-travellers.org Mon Nov 1 20:06:30 2010 From: shane at time-travellers.org (Shane Kerr) Date: Mon, 01 Nov 2010 20:06:30 +0100 Subject: RIPE-NCC-END-MNT in IPv6 PI In-Reply-To: <4CCF0B34.6020806@msu.ru> References: <4CCF0B34.6020806@msu.ru> Message-ID: <1288638390.29598.388.camel@shane-asus-laptop> 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 Local Internet Registries (LIRs)or End Users that need to update an object only maintained by this maintainer should write to If you are not a member you should send e-mail to . 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 at ripe.net or ncc at ripe.net, and I am sure you'll get the help you need. -- Shane From green at msu.ru Mon Nov 1 20:17:22 2010 From: green at msu.ru (Alexander Zubkov) Date: Mon, 01 Nov 2010 22:17:22 +0300 Subject: RIPE-NCC-END-MNT in IPv6 PI In-Reply-To: <1288638390.29598.388.camel@shane-asus-laptop> References: <4CCF0B34.6020806@msu.ru> <1288638390.29598.388.camel@shane-asus-laptop> Message-ID: <4CCF1242.40006@msu.ru> 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 > Local Internet Registries (LIRs)or End Users that need > to update an object only maintained by this maintainer > should write to > If you are not a member you should send e-mail > to. > > 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 at ripe.net or > ncc at ripe.net, and I am sure you'll get the help you need. > > -- > Shane > From green at msu.ru Mon Nov 1 20:48:07 2010 From: green at msu.ru (Alexander Zubkov) Date: Mon, 01 Nov 2010 22:48:07 +0300 Subject: RIPE-NCC-END-MNT in IPv6 PI In-Reply-To: <20101101194007.GA17262@unikko.org> References: <4CCF0B34.6020806@msu.ru> <1288638390.29598.388.camel@shane-asus-laptop> <4CCF1242.40006@msu.ru> <20101101194007.GA17262@unikko.org> Message-ID: <4CCF1977.4070004@msu.ru> Thank You. :) But is there some policies or other stuff that says it? On 11/01/2010 10:40 PM, Jussi Sallinen wrote: > No, you shouldnt delete those :-) > > -- > -Jussi Sallinen > +358407007600 > jussi at unikko.org > > On Mon, Nov 01, 2010 at 10:17:22PM +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? :) >> >> 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 >>> Local Internet Registries (LIRs)or End Users that need >>> to update an object only maintained by this maintainer >>> should write to >>> If you are not a member you should send e-mail >>> to. >>> >>> 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 at ripe.net or >>> ncc at ripe.net, and I am sure you'll get the help you need. >>> >>> -- >>> Shane >>> >> > From shane at time-travellers.org Mon Nov 1 22:26:06 2010 From: shane at time-travellers.org (Shane Kerr) Date: Mon, 01 Nov 2010 22:26:06 +0100 Subject: RIPE-NCC-END-MNT in IPv6 PI In-Reply-To: <4CCF1242.40006@msu.ru> References: <4CCF0B34.6020806@msu.ru> <1288638390.29598.388.camel@shane-asus-laptop> <4CCF1242.40006@msu.ru> Message-ID: <1288646766.29598.510.camel@shane-asus-laptop> 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 From green at msu.ru Tue Nov 2 14:10:00 2010 From: green at msu.ru (Alexander Zubkov) Date: Tue, 02 Nov 2010 16:10:00 +0300 Subject: RIPE-NCC-END-MNT in IPv6 PI In-Reply-To: <1288646766.29598.510.camel@shane-asus-laptop> References: <4CCF0B34.6020806@msu.ru> <1288638390.29598.388.camel@shane-asus-laptop> <4CCF1242.40006@msu.ru> <1288646766.29598.510.camel@shane-asus-laptop> Message-ID: <4CD00DA8.3080704@msu.ru> 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 > From shane at time-travellers.org Tue Nov 2 14:33:49 2010 From: shane at time-travellers.org (Shane Kerr) Date: Tue, 02 Nov 2010 14:33:49 +0100 Subject: RIPE-NCC-END-MNT in IPv6 PI In-Reply-To: <4CD00DA8.3080704@msu.ru> References: <4CCF0B34.6020806@msu.ru> <1288638390.29598.388.camel@shane-asus-laptop> <4CCF1242.40006@msu.ru> <1288646766.29598.510.camel@shane-asus-laptop> <4CD00DA8.3080704@msu.ru> Message-ID: <1288704829.29598.541.camel@shane-asus-laptop> 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 From green at msu.ru Tue Nov 2 14:50:25 2010 From: green at msu.ru (Alexander Zubkov) Date: Tue, 02 Nov 2010 16:50:25 +0300 Subject: RIPE-NCC-END-MNT in IPv6 PI In-Reply-To: <1288704829.29598.541.camel@shane-asus-laptop> References: <4CCF0B34.6020806@msu.ru> <1288638390.29598.388.camel@shane-asus-laptop> <4CCF1242.40006@msu.ru> <1288646766.29598.510.camel@shane-asus-laptop> <4CD00DA8.3080704@msu.ru> <1288704829.29598.541.camel@shane-asus-laptop> Message-ID: <4CD01721.7080104@msu.ru> 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.