Hi. It is obviously the 99℅ of members want to withdraw this proposal in any versions, but the NCC strongly moves it forward. May be the NCC has own reasons to do it, but why it doesn't notice evident things. 19 Окт 2016 г. 11:05 пользователь "Marco Schmidt" <mschmidt@ripe.net> написал:
Dear colleagues,
The draft documents for version 3.0 of the policy proposal 2016-03, "Locking Down the Final /8 Policy" have now been published, along with an impact analysis conducted by the RIPE NCC.
The goal of this proposal is to ban transfers of allocations made under the final /8 policy. Also the proposal specifies what resources must be added to the RIPE NCC IPv4 available pool.
Some of the differences from version 2.0 include:
- Clarification that changes to holdership of address space as a result of company mergers or acquisitions are not affected by proposed transfer restriction - Legacy space handed over to the RIPE NCC will be added to the IPv4 available pool
You can find the full proposal and the impact analysis at: https://www.ripe.net/participate/policies/proposals/2016-03
And the draft documents at: https://www.ripe.net/participate/policies/proposals/2016-03/draft
We want to draw your attention to two changes, which we hope it will make your proposal evaluation easier.
- Policy proposals now contain a diff tool that allows easy comparison of different proposal versions – simply click on the “View Changes” symbol right beside the list of proposal versions. - The RIPE NCC impact analysis only mentions areas where the proposal is actually expected to have an impact. For example, if the analysis makes no comment about financial or legal impact, it means that no such impact is expected.
We encourage you to read the draft document and send any comments to < address-policy-wg@ripe.net> before 17 November 2016.
Regards,
Marco Schmidt Policy Development Officer RIPE NCC
Sent via RIPE Forum -- https://www.ripe.net/participate/mail/forum