Modify section 7.1 of the Policy Manual
The resource revocation period may be extended for certain networks. Assessment by the LACNIC Board of Directors.
This proposal seeks to provide the community with another tool that will ensure resource availability for essential, strategic infrastructure, so as to not run any risks in exceptional cases.
Consequently, we propose that the power and ability to interpret which infrastructure can be considered essential and which cases are exceptional and merit invoking this possibility lie with the LACNIC Board of Directors.
Modify section 7.1 of the Policy Manual
Current text
-------------
If the situation cannot be rectified, LACNIC shall publish the resource that is to be recovered for a period of three months.
During this period, the organization may rectify the situation with LACNIC. After this period, the resource shall be recovered and therefore the records of the previous holder of the recovered resource shall be removed from LACNIC’s database.
Proposed text
-------------
If the situation cannot be rectified, LACNIC shall publish the resource that is to be recovered for a period of three months.
During this period, the organization may rectify the situation with LACNIC. After this period, the resource shall be recovered and therefore the records of the previous holder of the recovered resource shall be removed from LACNIC’s database.
Where the revocation of resources involves essential strategic infrastructure needed for operating the Internet in our region, the LACNIC Board of Directors may extend the resource revocation period should an extraordinary situation so require.
New textModify section 7.1 of the Policy Manual
Current text
-------------
If the situation cannot be rectified, LACNIC shall publish the resource that is to be recovered for a period of three months.
During this period, the organization may rectify the situation with LACNIC. After this period, the resource shall be recovered and therefore the records of the previous holder of the recovered resource shall be removed from LACNIC’s database.
Proposed text
-------------
If the situation cannot be rectified, LACNIC shall publish the resource that is to be recovered for a period of three months.
During this period, the organization may rectify the situation with LACNIC. After this period, the resource shall be recovered and therefore the records of the previous holder of the recovered resource shall be removed from LACNIC’s database.
Where the revocation of resources involves essential strategic infrastructure needed for operating the Internet in our region, the LACNIC Board of Directors may extend the resource revocation period should an extraordinary situation so require.
Additional informationhttps://www.youtube.com/watch?v=hSmamuVtrcY&t=3198s
TimetableNot specified
ReferencesNot specified
Presented at:-
Modify section 7.1 of the Policy Manual
The resource revocation period may be extended for certain networks. Assessment by the LACNIC Board of Directors.
This proposal seeks to provide the community with another tool that will ensure resource availability for essential, strategic infrastructure, so as to not run any risks in exceptional cases.
Consequently, we propose that the power and ability to interpret which infrastructure can be considered essential and which cases are exceptional and merit invoking this possibility lie with the LACNIC Board of Directors.
The modifications to version 2 of the proposal add additional possibilities to take into account exceptional cases and introduce specifications regarding a Staff Assessment.
Current textModify section 7.1 of the Policy Manual
Current text
-------------
If the situation cannot be rectified, LACNIC shall publish the resource that is to be recovered for a period of three months.
During this period, the organization may rectify the situation with LACNIC. After this period, the resource shall be recovered and therefore the records of the previous holder of the recovered resource shall be removed from LACNIC’s database.
Proposed text
-------------
If the situation cannot be rectified, LACNIC shall publish the resource that is to be recovered for a period of three months.
During this period, the organization may rectify the situation with LACNIC. After this period, the resource shall be recovered and therefore the records of the previous holder of the recovered resource shall be removed from LACNIC’s database.
In those cases where the revocation of resources involves essential strategic infrastructure that is necessary for operating the Internet in our region, or in exceptional situations such as natural disasters or political instability, the LACNIC Board of Directors may extend the resource revocation period, with prior assessment by the Staff once such an extraordinary situation is detected.
New textModify section 7.1 of the Policy Manual
Current text
-------------
If the situation cannot be rectified, LACNIC shall publish the resource that is to be recovered for a period of three months.
During this period, the organization may rectify the situation with LACNIC. After this period, the resource shall be recovered and therefore the records of the previous holder of the recovered resource shall be removed from LACNIC’s database.
Proposed text
-------------
If the situation cannot be rectified, LACNIC shall publish the resource that is to be recovered for a period of three months.
During this period, the organization may rectify the situation with LACNIC. After this period, the resource shall be recovered and therefore the records of the previous holder of the recovered resource shall be removed from LACNIC’s database.
In those cases where the revocation of resources involves essential strategic infrastructure that is necessary for operating the Internet in our region, or in exceptional situations such as natural disasters or political instability, the LACNIC Board of Directors may extend the resource revocation period, with prior assessment by the Staff once such an extraordinary situation is detected.
Additional informationhttps://www.youtube.com/watch?v=hSmamuVtrcY&t=3198s
TimetableNot specified
ReferencesNot specified
Presented at:LACNIC 27 (22/05/2017)