- policy-announce - mailman.ripe.net

RIPE community session on proposed revised Policy Development Process (PDP) - 26 January 2022
by Angela Dall'Ara 21 Jan '22

21 Jan '22

Dear colleagues, You are invited to provide your comments about the revised version of the PDP document at the online session next week, on Wednesday, 26 January 2022, at 16:00 Amsterdam time (UTC +1). In this message you can find the Zoom link to join the meeting. The new draft document is available at: https://www.ripe.net/publications/docs/ripe-documents/other-documents/polic… You can find more background information about the meeting in the email sent by the RIPE Chair to the ripe-list on 12 January 2022: https://www.ripe.net/ripe/mail/archives/ripe-list/2022-January/002410.html **** Topic: RIPE Workshop on revised PDP Time: Jan 26, 2022 16:00 - 17:30 Amsterdam time (UTC+1) Join Zoom Meeting https://ripe.zoom.us/j/98728370455?pwd=RXh5UStFRm9vaXFTMjVFcTJ4UERadz09 Meeting ID: 987 2837 0455 Passcode: 860568 Join by SIP 98728370455(a)zoomcrc.com Join by H.323 162.255.37.11 (US West) 162.255.36.11 (US East) 221.122.88.195 (China) 115.114.131.7 (India Mumbai) 115.114.115.7 (India Hyderabad) 213.19.144.110 (Amsterdam Netherlands) 213.244.140.110 (Germany) 103.122.166.55 (Australia Sydney) 103.122.167.55 (Australia Melbourne) 209.9.211.110 (Hong Kong SAR) 64.211.144.160 (Brazil) 69.174.57.160 (Canada Toronto) 65.39.152.160 (Canada Vancouver) 207.226.132.110 (Japan Tokyo) 149.137.24.110 (Japan Osaka) Meeting ID: 987 2837 0455 Passcode: 860568 -- Kind regards, Angela Dall'Ara RIPE NCC Policy Officer

1 0

Appeal against the Anti-Abuse WG Co-chairs decisions on proposal 2019-04 (Validation of “abuse-mailbox”)
by JORDI PALET MARTINEZ 26 Oct '20

26 Oct '20

Hi all, This appeal (attached in PDF) follows the process outlined by ripe-710 (RIPE PDP). Regards, Jordi @jordipalet ********************************************** IPv4 is over Are you ready for the new Internet ? http://www.theipv6company.com The IPv6 Company This electronic message contains information which may be privileged or confidential. The information is intended to be for the exclusive use of the individual(s) named above and further non-explicilty authorized disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited and will be considered a criminal offense. If you are not the intended recipient be aware that any disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited, will be considered a criminal offense, so you must reply to the original sender to inform about this communication and delete it.

3 2

2019-04 Policy Proposal Withdrawn (Validation of "abuse-mailbox")
by Petrit Hasani 08 Sep '20

08 Sep '20

Dear colleagues, The policy proposal 2019-04, "Validation of "abuse-mailbox”” has been withdrawn. The proposal aimed to have the RIPE NCC validate "abuse-c:” information more often and introduce a new validation process. The proposal is archived and can be found at: https://www.ripe.net/participate/policies/archived-policy-proposals/archive… Reason for withdrawal: The proposal did not reach consensus and the WG chairs did not feel that any further redrafting of the proposal would achieve consensus. Kind regards, -- Petrit Hasani Policy Officer RIPE NCC

1 0

2019-04 Review Phase (Validation of "abuse-mailbox")
by Petrit Hasani 20 Jul '20

20 Jul '20

Dear colleagues, Policy proposal 2019-04, "Validation of "abuse-mailbox"", is now in the Review Phase. This proposal aims to have the RIPE NCC validate "abuse-c:” information more often and introduces a new validation process. The RIPE NCC has prepared an impact analysis to support the community’s discussion. You can find the proposal and impact analysis at: https://www.ripe.net/participate/policies/proposals/2019-04 https://www.ripe.net/participate/policies/proposals/2019-04#impact-analysis And the draft documents at: https://www.ripe.net/participate/policies/proposals/2019-04/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 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 18 August 2020. Kind regards, -- Petrit Hasani Policy Officer RIPE NCC

1 0

2019-08 Policy Proposal Withdrawn (SLURM file for Unallocated and Unassigned RIPE NCC Address Space)
by Petrit Hasani 09 Jul '20

09 Jul '20

Dear colleagues, The policy proposal 2019-08, "SLURM file for Unallocated and Unassigned RIPE NCC Address Space" has been withdrawn. This proposal aimed for the RIPE NCC to publish a SLURM file (Simplified Local Internet Number Resource Management with the RPKI), containing assertions with the origin “AS0” for all unallocated and unassigned address space under our control. The proposal is archived and can be found at: https://www.ripe.net/participate/policies/archived-policy-proposals/archive… Reason for withdrawal: The WG Chair felt that raised concerns remained unaddressed and that there was a strong opposition against the proposal in the community. Kind regards, -- Petrit Hasani Policy Officer RIPE NCC

1 0

2019-08 Review Phase (SLURM file for Unallocated and Unassigned RIPE NCC Address Space)
by Petrit Hasani 25 May '20

25 May '20

Dear colleagues, Policy proposal 2019-08, “SLURM file for Unallocated and Unassigned RIPE NCC Address Space", is now in the Review Phase. The proposal aims for the RIPE NCC to publish a SLURM file (Simplified Local Internet Number Resource Management with the RPKI), containing assertions with the origin “AS0” for all unallocated and unassigned address space under our control. The proposal has been updated following the last round of discussion. Version 3 of the proposal has moved from instructing the RIPE NCC to create ROAs to creating a SLURM file for use with Relying Parties/Validators. The RIPE NCC has prepared an impact analysis on this latest proposal version to support the community’s discussion. You can find the proposal and impact analysis at: https://www.ripe.net/participate/policies/proposals/2019-08 https://www.ripe.net/participate/policies/proposals/2019-08#impact-analysis And the draft documents at: https://www.ripe.net/participate/policies/proposals/2019-08/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 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 23 June 2020. Kind regards, -- Petrit Hasani Policy Officer RIPE NCC

1 0

2019-04 Discussion Phase (Validation of "abuse-mailbox")
by Petrit Hasani 28 Apr '20

28 Apr '20

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. Most of the text has been rewritten following the last round of discussion and the proposal is now at version 3.0. Some key points in this version: - The abuse-mailbox should not force the sender to use a form - The validation process must ensure that the abuse mailbox is able to receive messages - The validation should happen at least every six months 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, will decide 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 27 May 2020. Kind regards, -- Petrit Hasani Policy Officer RIPE NCC

1 0

2019-06 Proposal Accepted (Multiple Editorial Changes in IPv6 Policy)
by Petrit Hasani 16 Mar '20

16 Mar '20

Dear colleagues, Consensus has been reached on 2019-06, "Multiple Editorial Changes in IPv6 Policy". This proposal aimed 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 The new RIPE Document is called ripe-738 and is available at: https://www.ripe.net/publications/docs/ripe-738 We estimate that this proposal will take around one month 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, -- Petrit Hasani Policy Officer RIPE NCC

1 0

2019-08 Review Phase (RPKI ROAs for Unallocated and Unassigned RIPE NCC Address Space)
by Petrit Hasani 20 Feb '20

20 Feb '20

Dear colleagues, Policy proposal 2019-08, "RPKI ROAs for Unallocated and Unassigned RIPE NCC Address Space", is now in the Review Phase. The goal of the proposal is to ask the RIPE NCC to create ROAs with origin AS0 for all unallocated and unassigned address space under its control. The proposal has been updated following the last round of discussion. Version 2 of the proposal includes a specification for the RIPE NCC to create all AS0 ROAs under a specific Trust Anchor. The RIPE NCC has prepared an impact analysis on this latest proposal version to support the community’s discussion. You can find the proposal and impact analysis at: https://www.ripe.net/participate/policies/proposals/2019-08 https://www.ripe.net/participate/policies/proposals/2019-08#impact-analysis And the draft documents at: https://www.ripe.net/participate/policies/proposals/2019-08/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 20 March 2020. Kind regards, -- Petrit Hasani Policy Officer RIPE NCC

1 0

2019-06 Last Call for Comments (Multiple Editorial Changes in IPv6 Policy)
by Petrit Hasani 11 Feb '20

11 Feb '20

Dear colleagues, Proposal 2019-06, "Multiple Editorial Changes in IPv6 Policy", is now in Concluding Phase. This proposal aims to remove obsoleted text and simplify the IPv6 policy. 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 11 March 2020 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/2019-06 Please e-mail any final comments about this proposal to <address-policy-wg(a)ripe.net> before 11 March 2020. Regards, -- Petrit Hasani Policy Officer RIPE NCC

1 0