- policy-announce - mailman.ripe.net

2017-02 Proposal Accepted (Regular abuse-c Validation)
by Marco Schmidt 01 Jun '18

01 Jun '18

Dear colleagues, Consensus has been reached on 2017-02, "Regular abuse-c Validation". This proposal gives the RIPE NCC a mandate to regularly validate "abuse-mailbox:" information and to follow up in cases where the attribute is deemed to be incorrect. You can find the full proposal at: https://www.ripe.net/participate/policies/proposals/2017-02 The new RIPE Document is ripe-705 and is available at: https://www.ripe.net/publications/docs/ripe-705 The RIPE NCC has already begun preparations to implement this policy change. Details of the implementation status are available at: https://www.ripe.net/manage-ips-and-asns/resource-management/policy-impleme… We will send another announcement once the implementation is complete and the regular validation is in place for all “abuse-mailbox:” attributes. Thank you to everyone who provided input. Kind regards, Marco Schmidt Policy Officer RIPE NCC

1 0

2018-01 Review Phase (Organisation-LIR Clarification in IPv6 Policy)
by Marco Schmidt 03 May '18

03 May '18

Dear colleagues, Policy proposal 2018-01, "Organisation-LIR Clarification in IPv6 Policy" is now in the Review Phase. This proposal aims to clarify the wording used in ripe-699 regarding terms such as "organisation" and "LIR". The proposal has been updated following the last round of discussion and is now at version v2.0. Some of the differences from version v1.0 include: - Clarifies when the subsequent allocation policy applies - Fixing some typos The RIPE NCC has prepared an impact analysis on this latest proposal version to support the community’s discussion. You can find the full proposal and impact analysis at: https://www.ripe.net/participate/policies/proposals/2018-01 And the draft documents at: https://www.ripe.net/participate/policies/proposals/2018-01/draft As per the RIPE Policy Development Process (PDP), the purpose of this four week Review Phase is to continue discussing the proposal, taking the impact analysis into consideration, and to review the full draft RIPE Policy Document. At the end of the Review Phase, the WG Chairs will determine whether the WG has reached rough consensus. It is therefore important to provide your opinion, even if it is simply a restatement of your input from the previous phase. We encourage you to read the proposal, impact analysis and draft document and send any comments to <address-policy-wg(a)ripe.net> before 1 June 2018. Kind regards, Marco Schmidt Policy Officer RIPE NCC

1 0

2017-02 Last Call for Comments (Regular abuse-c Validation)
by Marco Schmidt 26 Apr '18

26 Apr '18

Dear colleagues, Policy proposal 2017-02, "Regular abuse-c Validation", is now in Concluding Phase. The goal of this proposal is to give the RIPE NCC a mandate to regularly validate "abuse-mailbox:" information and to follow up in cases where the attribute is deemed to be incorrect. The WG Chairs have declared that rough consensus has been reached and the proposal will now move to Last Call. As per the RIPE Policy Development Process (PDP), the purpose of this four week Concluding Phase is to give an opportunity to present well-justified objections for those who missed the previous two phases and wish to oppose the proposal. Any objection must be made by 25 May 2018 and must be supported by an explanation. If no substantive objections are raised by the end of Last Call, the proposal will complete the PDP and will be evaluated by the WG Chairs for consensus. You can find the full proposal at: https://www.ripe.net/participate/policies/proposals/2017-02 Please e-mail any final comments about this proposal to <anti-abuse-wg(a)ripe.net> before 25 May 2018. Regards, Marco Schmidt Policy Officer RIPE NCC

1 0

2018-04 New Proposal (PDP Clarification)
by Marco Schmidt 26 Apr '18

26 Apr '18

Dear colleagues, A new RIPE proposal, 2018-04, "PDP Clarification" is now available for discussion. This proposal aims to clarify the options available to the WG chairs at the end of the Review Phase of the RIPE Policy Development Process (PDP). Please note that since changes to the PDP can affect all RIPE Working Groups, the RIPE Chair decided to discuss this proposal on the RIPE Discussion mailing list. The RIPE Chair will also moderate the proposal discussion. You can find the complete proposal at: https://www.ripe.net/participate/policies/proposals/2018-04 As per the RIPE Policy Development Process (PDP), the purpose of this four week Discussion Phase is to discuss the proposal and provide feedback to the proposer. At the end of the Discussion Phase, the proposer, with the agreement of the RIPE Chair, will decide how to proceed with the proposal. We encourage you to review this proposal and send your comments to ripe-list(a)ripe.net before 25 May 2018. Regards, Marco Schmidt Policy Officer RIPE NCC

1 0

2018-03 New Policy Proposal (Fixing Outdated Information in the IPv4 Policy)
by Marco Schmidt 24 Apr '18

24 Apr '18

Dear colleagues, A new RIPE Policy proposal, 2018-03, "Fixing Outdated Information in the IPv4 Policy" is now available for discussion. This proposal aims to fix outdated information in the RIPE Policy "IPv4 Address Allocation and Assignment Policies for the RIPE NCC Service Region". You can find the full proposal at: https://www.ripe.net/participate/policies/proposals/2018-03 As per the RIPE Policy Development Process (PDP), the purpose of this four week Discussion Phase is to discuss the proposal and provide feedback to the proposer. At the end of the Discussion Phase, the proposer, with the agreement of the WG Chairs, will decide how to proceed with the proposal. We encourage you to review this proposal and send your comments to <address-policy-wg(a)ripe.net> before 23 May 2018. Regards, Marco Schmidt Policy Officer RIPE NCC

1 0

2018-02 New Policy Proposal (Assignment Clarification in IPv6 Policy)
by Marco Schmidt 17 Apr '18

17 Apr '18

Dear colleagues, A new RIPE Policy proposal, 2018-02, "Assignment Clarification in IPv6 Policy" is now available for discussion. This proposal aims to clarify the definition of “Assign” in ripe-699 (section 2.6). The non-permanent provision of up to a /64 prefix to third parties shall not be considered a sub-assignment. You can find the full proposal at: https://www.ripe.net/participate/policies/proposals/2018-02 As per the RIPE Policy Development Process (PDP), the purpose of this four week Discussion Phase is to discuss the proposal and provide feedback to the proposer. At the end of the Discussion Phase, the proposer, with the agreement of the WG Chairs, will decide how to proceed with the proposal. We encourage you to review this proposal and send your comments to <address-policy-wg(a)ripe.net> before 15 May 2018. Regards, Marco Schmidt Policy Officer RIPE NCC

1 0

2016-04 Proposal Accepted (IPv6 Sub-assignment Clarification)
by Marco Schmidt 20 Mar '18

20 Mar '18

Dear colleagues, Consensus has been reached on 2016-04, "IPv6 Sub-assignment Clarification". The goal of this proposal was to re-define the term "sub-assignment" for IPv6. You can find the full proposal at: https://www.ripe.net/participate/policies/proposals/2016-04 The new RIPE Document is ripe-699 and is available at: https://www.ripe.net/publications/docs/ripe-699 We estimate that this proposal will take around two weeks to fully implement. We will send another announcement once the implementation is complete and the new procedures are in place. Thank you to everyone who provided input. Kind regards, Marco Schmidt Policy Development Officer RIPE NCC

1 0

2017-02 Extended Review Phase Extended (Regular abuse-c Validation)
by Marco Schmidt 12 Mar '18

12 Mar '18

Dear colleagues, Policy proposal 2017-02, "Regular abuse-c Validation" is now in the extended Review Phase. The goal of this proposal is to give the RIPE NCC a mandate to regularly validate "abuse-mailbox:" information and to follow up in cases where the attribute is deemed to be incorrect. You can find the full proposal and the RIPE NCC impact analysis at: https://www.ripe.net/participate/policies/proposals/2017-02 And the draft document at: https://www.ripe.net/participate/policies/proposals/2017-02/draft As per the RIPE Policy Development Process (PDP), the purpose of this four week extended Review Phase is to continue discussing the proposal, taking the impact analysis into consideration, and to review the full draft RIPE Policy Document. At the end of the Review Phase, the WG Chairs will determine whether the WG has reached rough consensus. We encourage you to read the proposal, impact analysis and draft document, and share your comments on <anti-abuse-wg(a)ripe.net> before 10 April 2018. Kind regards, Marco Schmidt Policy Development Officer RIPE NCC

1 0

2018-01 New Policy Proposal (Organisation-LIR Clarification in IPv6 Policy)
by Marco Schmidt 22 Feb '18

22 Feb '18

Dear colleagues, A new RIPE Policy proposal, 2018-01, "Organisation-LIR Clarification in IPv6 Policy" is now available for discussion. This proposal aims to clarify the wording used in ripe-684 regarding terms such as "organisation" and "LIR". You can find the full proposal at: https://www.ripe.net/participate/policies/proposals/2018-01 As per the RIPE Policy Development Process (PDP), the purpose of this four week Discussion Phase is to discuss the proposal and provide feedback to the proposer. At the end of the Discussion Phase, the proposers, with the agreement of the WG Chairs, will decide how to proceed with the proposal. We encourage you to review this proposal and send your comments to <address-policy-wg(a)ripe.net> before 23 March 2018. Regards, Marco Schmidt Policy Development Officer RIPE NCC

1 0

2017-02 Review Phase (Regular abuse-c Validation)
by Marco Schmidt 18 Jan '18

18 Jan '18

Dear colleagues, Policy proposal 2017-02, "Regular abuse-c Validation" is now in the Review Phase. 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 the attribute is deemed to be incorrect. This proposal has been updated following the last round of discussion and is now at version v2.0. Some of the differences from version v1.0 include: - A focus on validating the "abuse-mailbox:" attribute and fixing incorrect contact information - Added references to RIPE Policies and RIPE NCC procedures The RIPE NCC has prepared an impact analysis on this latest proposal version to support the community’s discussion. You can find the full proposal and impact analysis at: https://www.ripe.net/participate/policies/proposals/2017-02 And the draft documents at: https://www.ripe.net/participate/policies/proposals/2017-02/draft As per the RIPE Policy Development Process (PDP), the purpose of this four-week Review Phase is to continue discussing the proposal, taking the impact analysis into consideration, and to review the full draft policy document. At the end of the Review Phase, the WG Chairs will determine whether the WG has reached rough consensus. It is therefore important to provide your opinion, even if it is simply a restatement of your input from the previous phase. We encourage you to read the proposal, impact analysis and draft document, and share your comments on <anti-abuse-wg(a)ripe.net> before 16 February 2018. Kind regards, Marco Schmidt Policy Development Officer RIPE NCC

1 0