[policy-announce] 2016-03 New Policy Proposal (Locking Down the Final /8 Policy)
- Previous message (by thread): [policy-announce] 2016-02 New Policy Proposal (Resource Authentication Key ( RAK ) code for third party authentication)
- Next message (by thread): [policy-announce] 2015-05 Discussion Period extended until 13 June 2016 (Last /8 Allocation Criteria Revision)
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Marco Schmidt
mschmidt at ripe.net
Tue May 17 14:05:23 CEST 2016
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 at ripe.net> before 15 June 2016. Regards Marco Schmidt Policy Development Officer RIPE NCC
- Previous message (by thread): [policy-announce] 2016-02 New Policy Proposal (Resource Authentication Key ( RAK ) code for third party authentication)
- Next message (by thread): [policy-announce] 2015-05 Discussion Period extended until 13 June 2016 (Last /8 Allocation Criteria Revision)
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]