- policy-announce - mailman.ripe.net

2019-08 New Policy Proposal (RPKI ROAs for Unallocated and Unassigned RIPE NCC Address Space)
by Petrit Hasani 31 Oct '19

31 Oct '19

Dear colleagues, A new RIPE Policy proposal, 2019-08, "RPKI ROAs for Unallocated and Unassigned RIPE NCC Address Space" is now available for discussion. This proposal aims to instructs the RIPE NCC to create ROAs with origin AS0 for all unallocated and unassigned address space under its control. You can find the full proposal at: https://www.ripe.net/participate/policies/proposals/2019-08 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 <routing-wg(a)ripe.net> before 29 November 2019. Kind regards, -- Petrit Hasani Policy Officer RIPE NCC

1 0

2019-07 New Policy Proposal (Default assignment size for IXPs)
by Marco Schmidt 15 Oct '19

15 Oct '19

Dear colleagues, A new RIPE Policy proposal, 2019-07, "Default assignment size for IXPs" is now available for discussion. This proposal aims to change the default IXP assignment size from a /24 to a needs-based model, with a /27 as a minimum. You can find the full proposal at: https://www.ripe.net/participate/policies/proposals/2019-07 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 13 November 2019. Regards, Marco Schmidt Policy Officer RIPE NCC

1 0

2019-05 Proposal Accepted (Revised IPv4 assignment policy for IXPs)
by Marco Schmidt 10 Oct '19

10 Oct '19

Dear colleagues, Consensus has been reached on 2019-05, "Revised IPv4 assignment policy for IXPs". This proposal aimed to increase the reserved IPv4 pool for IXPs to a /15 and finetune assignment criteria. You can find the full proposal at: https://www.ripe.net/participate/policies/proposals/2019-05 The new RIPE Document is called ripe-730 and is available at: https://www.ripe.net/publications/docs/ripe-730 We have already implemented the pool management part of this proposal (185.0.0.0/16 and the IPv4 fragments smaller than /24 have been added to the reserved IPv4 pool for IXPs). We estimate that this proposal will take around two months 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 us with your input. Kind regards, Marco Schmidt Policy Officer RIPE NCC

1 0

2019-06 New Policy Proposal (Multiple Editorial Changes in IPv6 Policy)
by Marco Schmidt 08 Oct '19

08 Oct '19

Dear colleagues, A new RIPE Policy proposal, 2019-06, "Multiple Editorial Changes in IPv6 Policy" is now available for discussion. This proposal aims to remove obsoleted text and simplify the IPv6 policy. You can find the full proposal at: https://www.ripe.net/participate/policies/proposals/2019-06 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 6 November 2019. Regards, Marco Schmidt Policy Officer RIPE NCC

1 0

2018-06 Last Call (RIPE NCC IRR Database Non-Authoritative Route Object Clean-up)
by Marco Schmidt 07 Oct '19

07 Oct '19

Dear colleagues, Policy proposal 2018-06, "RIPE NCC IRR Database Non-Authoritative Route Object Clean-up", is now in Concluding Phase. The goal of the proposal is to delete an non-authoritative object stored in the RIPE IRR, if it conflicts with an RPKI ROA. The WG co-chair has 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 before 5 November 2019 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 co-chairs for final consensus. You can find the full proposal at: https://www.ripe.net/participate/policies/proposals/2018-06 Please e-mail any final comments about this proposal to <routing-wg(a)ripe.net> before 5 November 2019. Regards, Marco Schmidt Policy Officer RIPE NCC

1 0

2019-03 Policy Proposal Withdrawn (Resource Hijacking is a RIPE Policy Violation)
by Marco Schmidt 02 Oct '19

02 Oct '19

Dear colleagues, The policy proposal 2019-03, "Resource Hijacking is a RIPE Policy Violation" has been withdrawn. This proposal aimed to define that BGP hijacking is not accepted as normal practice within the RIPE NCC service region. The proposal is archived and can be found at: https://www.ripe.net/participate/policies/archived-policy-proposals/archive… Reason for withdrawal: The proposers felt they were unable to address concerns that the policy would expose the RIPE NCC to unacceptable liability risks. These concerns were expressed by both the Executive Board and some community members. Kind regards, Marco Schmidt Policy Officer RIPE NCC

1 0

2019-04 Discussion Phase (Validation of "abuse-mailbox")
by Marco Schmidt 01 Oct '19

01 Oct '19

Dear colleagues, A new version of RIPE Policy proposal, 2019-04, "Validation of "abuse-mailbox"", is now available for discussion. This proposal aims to have the RIPE NCC validate "abuse-c:" information more often, and introduces a new validation process that requires input from resource holders. 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: - Removes ambiguous examples from the policy text - Defines mandatory elements of the abuse handling procedures - Removes the prohibtion of automated processing of the abuse reports You can find the full proposal at: https://www.ripe.net/participate/policies/proposals/2019-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 Anti-Abuse Working Group Chairs, decides how to proceed with the proposal. We encourage you to review this proposal and send your comments to <anti-abuse-wg(a)ripe.net> before 30 October 2019. Kind regards, Marco Schmidt Policy Officer RIPE NCC

1 0

2019-05 Last Call for Comments (Revised IPv4 assignment policy for IXPs)
by Marco Schmidt 09 Sep '19

09 Sep '19

Dear colleagues, Proposal 2019-05, "Revised IPv4 assignment policy for IXPs", is now in Concluding Phase. This proposal aims to increase the reserved IPv4 pool for IXPs to a /15 and finetune assignment criteria. The WG co-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 8 October 2019 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 co-chairs for final consensus. As this policy change has reaches rough consensus, the RIPE NCC has now reserved 185.0.0.0/16 for this policy change. If final consensus is achieved, the /16 will be used as per the policy proposal, and alternatively, if the proposal is withdrawn, the address space will be returned to the IPv4 pool for allocations. You can find the full proposal at: https://www.ripe.net/participate/policies/proposals/2019-05 Please e-mail any final comments about this proposal to <address-policy-wg(a)ripe.net> before 8 October 2019. Regards, Marco Schmidt Policy Officer RIPE NCC

1 0

2019-03 Review Phase (Resource Hijacking is a RIPE Policy Violation)
by Marco Schmidt 05 Sep '19

05 Sep '19

Dear colleagues, Policy proposal 2019-03, "Resource Hijacking is a RIPE Policy Violation" is now in the Review Phase. The goal of this proposal is to define that BGP hijacking is not accepted as normal practice within the RIPE NCC service region. The proposal has been updated following the last round of discussion and is now at version v2.0. Some of the changes made to version v1.0 include: - Includes procedural steps for reporting and evaluation of potential hijacks - Provides guidelines for external experts - Adjusted title 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/2019-03 https://www.ripe.net/participate/policies/proposals/2019-03#impact-analysis And the draft documents at: https://www.ripe.net/participate/policies/proposals/2019-03/draft As per the RIPE Policy Development Process (PDP), the purpose of this four week Review Phase is to continue discussion of 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 Working Group (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 <anti-abuse-wg(a)ripe.net> before 4 October 2019. Kind regards, Marco Schmidt Policy Officer RIPE NCC

1 0

2018-06 Review Phase (RIPE NCC IRR Database Non-Authoritative Route Object Clean-up)
by Marco Schmidt 14 Aug '19

14 Aug '19

Dear colleagues, Policy proposal 2018-06, "RIPE NCC IRR Database Non-Authoritative Route Object Clean-up", is now in the Review Phase. The goal of the proposal is to delete an non-authoritative object stored in the RIPE IRR, if it conflicts with an RPKI ROA. The proposal has been updated following the last round of discussion and is now at version v3.0. Some of the differences from version v2.0 include: - Provides details about the process how to identify and solve conflicts 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-06 And the draft documents at: https://www.ripe.net/participate/policies/proposals/2018-06/draft As per the RIPE Policy Development Process (PDP), the purpose of this four week Review Phase is to continue discussion of 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 Working Group (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 <routing-wg(a)ripe.net> before 12 September 2019. Kind regards, Marco Schmidt Policy Officer RIPE NCC

1 0