This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/ripe-list@ripe.net/
[ripe-list] [news] RIPE Policy Proposals - September Update
- Previous message (by thread): [ripe-list] New on RIPE Labs: How informal channels are important for network coordination
- Next message (by thread): [ripe-list] DNS Root Zone KSK Rollover postponed
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Marco Schmidt
mschmidt at ripe.net
Fri Sep 29 12:00:33 CEST 2017
Dear colleagues, Here is our monthly overview of open policy proposals and their stage in the RIPE Policy Development Process (PDP). If you wish to join the discussion about a particular proposal, please do so on the relevant working group mailing list. Proposals Open for Discussion: NEW: 2017-02, "Regular abuse-c Validation" NEW: 2017-03, "Reducing Initial IPv4 Allocation, Aiming to Preserve a Minimum of IPv4 Space for Newcomers" Proposals Awaiting Input: 2016-04, "IPv6 PI Sub-assignment Clarification" Proposal Withdrawn: 2017-01, "Publish statistics on Intra-RIR Legacy updates" Proposal Overview: NEW PROPOSAL: 2017-02, "Regular abuse-c Validation" OVERVIEW: The goal of this proposal is to give the RIPE NCC a mandate to regularly validate "abuse-c:" information and to follow up in cases where contact information is found to be invalid. STATUS: Discussion Phase WHERE TO COMMENT: Anti-Abuse Working Group: anti-abuse-wg at ripe.net DEADLINE: 6 October 2017 FULL PROPOSAL: https://www.ripe.net/participate/policies/proposals/2017-02 NEW PROPOSAL: 2017-03, "Reducing Initial IPv4 Allocation, Aiming to Preserve a Minimum of IPv4 Space for Newcomers " OVERVIEW: The goal of this proposal is to reduce the IPv4 allocations made by the RIPE NCC to a /24 (currently a /22) and only to LIRs that have not received an IPv4 allocation directly from the RIPE NCC before. STATUS: Discussion Phase WHERE TO COMMENT: Address Policy Working Group: address-policy-wg at ripe.net DEADLINE: 20 October 2017 FULL PROPOSAL: https://www.ripe.net/participate/policies/proposals/2017-03 ===== The following proposal is awaiting input before they can go any further in the PDP. PROPOSAL: 2016-04, "IPv6 PI Sub-assignment Clarification" OVERVIEW: The goal of this proposal is to define sub-assignments in IPv6 PI assignments as subnets of /64 and shorter. RIPE NCC IMPACT ANALYSIS: Explains feasibility and possible side effects. STATUS: Review Phase – Creating impact analysis for new version FULL PROPOSAL: https://www.ripe.net/participate/policies/proposals/2016-04 ===== The following proposal has been withdrawn. PROPOSAL: 2017-01, "Publish statistics on Intra-RIR Legacy updates" OVERVIEW: This proposal aimed to add the requirement that the RIPE NCC publish all changes to the holdership of legacy resources in the existing transfer statistics. STATUS: Withdrawn. The proposer didn't see enough community support, especially from Legacy Resource Holders as the parties that would be most affected. FULL PROPOSAL: https://www.ripe.net/participate/policies/proposals/2017-01 The RIPE NCC provides an overview of current RIPE Policy Proposals here: https://www.ripe.net/participate/policies/current-proposals/current-policy-proposals We look forward to your involvement in the PDP. Kind regards, Marco Schmidt RIPE Policy Development Officer RIPE NCC Sent via RIPE Forum -- https://www.ripe.net/participate/mail/forum
- Previous message (by thread): [ripe-list] New on RIPE Labs: How informal channels are important for network coordination
- Next message (by thread): [ripe-list] DNS Root Zone KSK Rollover postponed
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]