May 2016 - policy-announce - mailman.ripe.net

2016-02 Discussion Period Extended Until 29 June 2016 (Resource Authentication Key ( RAK ) code for third party authentication)
by Marco Schmidt 31 May '16

31 May '16

Dear colleagues, The Discussion Phase for RIPE Policy proposal 2016-02, "Resource Authentication Key ( RAK ) code for third party authentication" has been extended until 29 June 2016. The proposal aims to allow all number resources, in exacts and more specifics, to be authenticated via an API-key that expires on a certain date. You can find the full proposal at: https://www.ripe.net/participate/policies/proposals/2016-02 We encourage you to review this proposal and send your comments to <ncc-services-wg(a)ripe.net>. Regards, Marco Schmidt Policy Development Officer RIPE NCC

1 0

2016-01 Discussion Period Extended Until 21 June 2016 (Include Legacy Internet Resource Holders in the Abuse-c Policy)
by Marco Schmidt 23 May '16

23 May '16

Dear colleagues, The Discussion Phase for 2016-01, "Include Legacy Internet Resource Holders in the Abuse-c Policy” has been extended until 21 June 2016. The goal of this proposal is to extend ripe-563, "Abuse Contact Management in the RIPE Database” to include Legacy Internet Resource Holders. The proposal text has been revised based on mailing list feedback and a new version (2.0) is now published. This has started a new Discussion Phase for the proposal. The main difference from version 1.0 is that the policy will be only applied when creating or modifying Legacy Internet Resource objects in the RIPE Database. You can find the full proposal at: https://www.ripe.net/participate/policies/proposals/2016-01 We encourage you to review this proposal and send your comments to <anti-abuse-wg at ripe.net>. Regards, Marco Schmidt Policy Development Officer RIPE NCC

1 0

2015-05 Discussion Period extended until 13 June 2016 (Last /8 Allocation Criteria Revision)
by Marco Schmidt 20 May '16

20 May '16

Dear colleagues, The Discussion Period for the proposal 2015-05, "Last /8 Allocation Criteria Revision" has been extended until 13 June 2016. You can find the full proposal at: https://www.ripe.net/participate/policies/proposals/2015-05 We encourage you to review this policy proposal and send your comments to <address-policy-wg(a)ripe.net>. Regards, Marco Schmidt Policy Development Officer RIPE NCC

1 0

2016-03 New Policy Proposal (Locking Down the Final /8 Policy)
by Marco Schmidt 17 May '16

17 May '16

Dear colleagues, A new RIPE Policy proposal 2016-03, "Locking Down the Final /8 Policy" is now available for discussion. The goal of this proposal is to limit IPv4 from the remaining address pool to one /22 per LIR (regardless of how it was received). These “final /22” allocations will receive a separate status with several restrictions: - These allocation are not transferrable - LIRs may only retain one final /22 following a merger or acquisition - Sub-allocations are not possible - Reverse delegation authority can not delegated to another party You can find the full proposal at: https://www.ripe.net/participate/policies/proposals/2016-03 We encourage you to review this proposal and send your comments to <address-policy-wg(a)ripe.net> before 15 June 2016. Regards Marco Schmidt Policy Development Officer RIPE NCC

1 0

2016-02 New Policy Proposal (Resource Authentication Key ( RAK ) code for third party authentication)
by Marco Schmidt 02 May '16

02 May '16

Dear colleagues, A new RIPE Policy Proposal 2016-02, "Resource Authentication Key ( RAK ) code for third party authentication" has been made and is now available for discussion. The proposal aims to allow all number resources, in exacts and more specifics, to be authenticated via an date expiring API-key. You can find the full proposal at: https://www.ripe.net/participate/policies/proposals/2016-02 We encourage you to review this proposal and send your comments to <ncc-services-wg(a)ripe.net> before 31 May 2016. Regards, Marco Schmidt Policy Development Officer RIPE NCC

1 0