RIPE NCC impact analysis for RIPE DB Requirements TF recommendations
Dear APWG, The RIPE NCC has released an initial impact analysis on the recommendations made by the RIPE Database Requirements Task Force. This should prove a useful reference point when reviewing the recommendations. You can find a link to the impact analysis here, at the end of the first paragraph: https://www.ripe.net/participate/ripe/tf/rdb-requirements-tf/database-requir.... Regarding recommendation 2: IPv4 PA Assignments, the RIPE NCC reports the following "Requirements" and "Impact". "Requirements: A new policy providing details about if and how to amend PA assignment registration must be proposed and accepted in the RIPE Address Policy WG. Impact: The RIPE NCC will need to update the Database rules and related external documentation. RIPE NCC Registry Services can expect some additional tickets with questions and requests for support. RIPE NCC training course content will need to be updated." RDBTF recommendation 2: IPv4 PA assignments The task force recommends that as resource holders have full responsibility over the registration of their IPv4 PA assignment(s), they are free to make assignments or not. If the community accepts this recommendation, the relevant RIPE Policies should be updated accordingly, and documenting IPv4 PA assignment(s) will stop being a policy requirement. Please note that the task force does NOT recommend that these assignments be deleted but that resource holders can choose to document this information in the RIPE Database. However, if a resource holder wants to sub-allocate or partition part of their IPv4 resources to another entity, the task force strongly recommends documenting this sub-allocation or assignment in the RIPE Database. Following the data consistency principle, the task force also recommends resource registration requirements be applied consistently to all Internet number resources, regardless of their type or status. To ensure that the information published in the RIPE Database is correctly updated by resource holders, the task force recommends that the RIPE NCC continue to use ARCs (Assisted Registry Checks) to verify this data. *** Regards, James apwg co-chair
Direct link to the RIPE NCC's initial impact assessment of the RIPE Database Requirements Task Force (DBTF) recommendations: https://www.ripe.net/participate/ripe/tf/rdb-requirements-tf/initial-analysi... Overview of all DBTF recommendations, related working groups, and the status of each: https://www.ripe.net/participate/ripe/tf/rdb-requirements-tf/database-requir... Regards, James apwg co-chair On Tue, Sep 13, 2022 at 12:52 PM James Kennedy <jameskennedy001@gmail.com> wrote:
Dear APWG,
The RIPE NCC has released an initial impact analysis on the recommendations made by the RIPE Database Requirements Task Force. This should prove a useful reference point when reviewing the recommendations. You can find a link to the impact analysis here, at the end of the first paragraph: https://www.ripe.net/participate/ripe/tf/rdb-requirements-tf/database-requir....
Regarding recommendation 2: IPv4 PA Assignments, the RIPE NCC reports the following "Requirements" and "Impact".
"Requirements: A new policy providing details about if and how to amend PA assignment registration must be proposed and accepted in the RIPE Address Policy WG.
Impact: The RIPE NCC will need to update the Database rules and related external documentation. RIPE NCC Registry Services can expect some additional tickets with questions and requests for support. RIPE NCC training course content will need to be updated."
RDBTF recommendation 2: IPv4 PA assignments The task force recommends that as resource holders have full responsibility over the registration of their IPv4 PA assignment(s), they are free to make assignments or not. If the community accepts this recommendation, the relevant RIPE Policies should be updated accordingly, and documenting IPv4 PA assignment(s) will stop being a policy requirement. Please note that the task force does NOT recommend that these assignments be deleted but that resource holders can choose to document this information in the RIPE Database. However, if a resource holder wants to sub-allocate or partition part of their IPv4 resources to another entity, the task force strongly recommends documenting this sub-allocation or assignment in the RIPE Database.
Following the data consistency principle, the task force also recommends resource registration requirements be applied consistently to all Internet number resources, regardless of their type or status. To ensure that the information published in the RIPE Database is correctly updated by resource holders, the task force recommends that the RIPE NCC continue to use ARCs (Assisted Registry Checks) to verify this data.
***
Regards, James apwg co-chair
participants (1)
-
James Kennedy