Hi, I don't think is right for the chairs to withdraw a policy proposal. The authors, or other authors have always the right to send a new proposal.
I think we are here misjudging what rough consensus means, which shall be interpreted as per RFC7282. There must be solid technical arguments against a proposal, not personal opinions. I don't think "fierce opposition" and "doubt that will reach consensus" aren't reasonable arguments. We can show many situations where a long discussion or after a pause (such as the summer) drives to different conclusions. Regards, Jordi @jordipalet El 8/7/20 15:29, "routing-wg en nombre de Paul Hoogsteder" <[email protected] en nombre de [email protected]> escribió: Dear Routing WG, dear authors of 2019-08 "SLURM file for Unallocated and Unassigned RIPE NCC Address Space", after the previous Review phase (v2 of the proposal) didn't reach consensus in April I asked the authors whether they would like to withdraw the proposal or come up with a new one. A new proposal "SLURM file for Unallocated and Unassigned RIPE NCC Address Space" was written and a new Review phase started on the 25th of May 2020, we had a few messages on the mailinglist in reply to that. This phase ended on June 23. I have concluded that no rough consensus has been reached this time either as raised concerns have not been addressed, and judging by the sometimes fierce opposition I doubt that we will reach consensus with a few small changes to the proposal and a new Review phase - and therefore I have decided to withdraw the proposal. Kind regards, Paul Hoogsteder RIPE Routing WG co-chair > 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 <[email protected]> before 23 June 2020. > > Kind regards, > -- > Petrit Hasani > Policy Officer > RIPE NCC > > > > > > ********************************************** 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.
