Set default maintainer on locked inetnum resources
Dear colleagues, From time to time, the RIPE NCC gets requests from LIRs to unlock their PA assignments that have RIPE-NCC-LOCKED-MNT as mnt-by. These inetnums are locked due to the deprecation of the NONE authentication scheme in 2004: https://www.ripe.net/publications/news/announcements/deprecation-of-the-none... A total of 438 ASSIGNED PA AND 13 LEGACY inetnums have both this maintainer, and a responsible LIR organisation referenced in a less-specific inetnum. The DB team wishes to update these inetnums with the responsible LIR's default maintainer, so they can be maintained by the LIR without needing to contact the RIPE NCC. We will inform the affected maintainers. Please let me know your comments. If there are no objections, I'd like to implement this in the coming weeks. Regards Ed Shryane RIPE NCC
Edward Shryane via db-wg wrote on 09/02/2023 13:31:
The DB team wishes to update these inetnums with the responsible LIR's default maintainer, so they can be maintained by the LIR without needing to contact the RIPE NCC. We will inform the affected maintainers.
Please let me know your comments. If there are no objections, I'd like to implement this in the coming weeks. if the LIR / end-user contacts the RIPE NCC, is this what you guys do by default? If so, then doing this by default for all affected objects seems reasonable enough.
Nick
Hi Nick,
On 9 Feb 2023, at 14:38, Nick Hilliard <nick@foobar.org> wrote:
... if the LIR / end-user contacts the RIPE NCC, is this what you guys do by default? If so, then doing this by default for all affected objects seems reasonable enough.
Nick
Correct, this is what the RIPE NCC is doing by default now, on request. Regards Ed Shryane RIPE NCC
Seems like a reasonable thing to do. However with anything that changes after such a long time I think you should notify all relevant admin contacts and maintainers a week or two in advance. This is just so they have a chance to object if it would be the wrong maintainer or whatever. Also make sure to notify those parties once the update has gone through. Are these legacy resources just those who are under some kind of direct or indirect agreement with the RIPE NCC? I assume so but I just want to make sure. -Cynthia On Thu, 9 Feb 2023, 14:32 Edward Shryane via db-wg, <db-wg@ripe.net> wrote:
Dear colleagues,
From time to time, the RIPE NCC gets requests from LIRs to unlock their PA assignments that have RIPE-NCC-LOCKED-MNT as mnt-by.
These inetnums are locked due to the deprecation of the NONE authentication scheme in 2004:
https://www.ripe.net/publications/news/announcements/deprecation-of-the-none...
A total of 438 ASSIGNED PA AND 13 LEGACY inetnums have both this maintainer, and a responsible LIR organisation referenced in a less-specific inetnum.
The DB team wishes to update these inetnums with the responsible LIR's default maintainer, so they can be maintained by the LIR without needing to contact the RIPE NCC. We will inform the affected maintainers.
Please let me know your comments. If there are no objections, I'd like to implement this in the coming weeks.
Regards Ed Shryane RIPE NCC
--
To unsubscribe from this mailing list, get a password reminder, or change your subscription options, please visit: https://lists.ripe.net/mailman/listinfo/db-wg
Hi Cynthia,
On 9 Feb 2023, at 14:49, Cynthia Revström <me@cynthia.re> wrote:
Seems like a reasonable thing to do.
However with anything that changes after such a long time I think you should notify all relevant admin contacts and maintainers a week or two in advance. This is just so they have a chance to object if it would be the wrong maintainer or whatever. Also make sure to notify those parties once the update has gone through.
This is a good idea, we will email admin contacts in addition to maintainers, far enough in advance to give them a reasonable amount of time to respond.
Are these legacy resources just those who are under some kind of direct or indirect agreement with the RIPE NCC? I assume so but I just want to make sure.
Correct, there are 460 LEGACY inetnums in total that are locked, but only 13 of these are covered by an agreement with the RIPE NCC. For each of these 13, we will perform due diligence on the parent LIR to confirm the relationship with the LEGACY resource. Regards Ed Shryane RIPE NCC
Dear Colleagues,
On 10 Feb 2023, at 10:49, Edward Shryane via db-wg <db-wg@ripe.net> wrote: ... This is a good idea, we will email admin contacts in addition to maintainers, far enough in advance to give them a reasonable amount of time to respond.
We now plan to notify the resource contacts and LIR default maintainers by email on Monday 27th February, and will update the affected objects on the following Monday 6th March.
Correct, there are 460 LEGACY inetnums in total that are locked, but only 13 of these are covered by an agreement with the RIPE NCC.
For each of these 13, we will perform due diligence on the parent LIR to confirm the relationship with the LEGACY resource.
We have performed due diligence checks on the 13 LEGACY resources and have confirmed the relationship with the associated LIR. We will also include the 438 ASSIGNED PA resources, as already mentioned. Regards Ed Shryane RIPE NCC
Dear Colleagues,
...
We now plan to notify the resource contacts and LIR default maintainers by email on Monday 27th February, and will update the affected objects on the following Monday 6th March.
We have now updated these resources and notified the contacts. Regards Ed Shryane RIPE NCC
participants (3)
-
Cynthia Revström -
Edward Shryane -
Nick Hilliard