- ripe-list - mailman.ripe.net

repeated and continued PDP violation - WG chairs delaying or denying proposal publication - new policy proposal "Ensure Neutrality of PDP Appeals Procedure"
by JORDI PALET MARTINEZ 09 Feb '21

09 Feb '21

Hi all, Across the years, I've suffered this situation several times and I think this community must not allow it anymore and I wish the PDP has explicit actions against those situations, so they don't happen over and over. Briefly, in several situation I've written policy proposals, and the chairs of the WG, tried to convince me to not publish it, or actually decided not to publish it, or delayed it. Of course, this is a clear violation of the PDP (RIPE-710). The PDP states: "Discussions may be started by anyone at any time. Participants are welcome to discuss broad ideas as well as to make detailed policy proposals" Also: "A proposal is discussed publicly in the relevant RIPE Working Group (WG)[1]. The proposal is usually submitted via the chair of that WG." Actually, and since many years, "usually", you submit the proposal to the Policy Officer and if you already know the appropriate WG, you copy to the WG chairs. It is normal that the publication is delayed for a few days, as the WG chairs can provide some inputs, the staff as well (including editorial suggestions), questions to the staff, even the Board, etc., etc. HOWEVER, there is no way for the WG chairs to delay or deny a publication or reject a proposal (unless is clearly out of the scope of the WG). Actual specific example of the situation I'm facing (approximate dates, just to show the unacceptable delay in a policy proposal publication): 1) 9th September 2020: Anti-abuse-wg chairs decided to declare non-consensus in proposal 2019-04 and I announce that I've asked them for more details and if I'm not satisfied, I will start an appeal. A couple of community members, in private, tell me that it will not happen. I re-read the PDP and get convinced that they're right, but I must do it anyway. 2) I write a policy proposal ("Ensure Neutrality of PDP Appeals Procedure") to update the PDP to avoid this happening in the future (so clearly knowing that it will be relevant for my appeal). Submitted formally on 5th October. This proposal is sent to the Policy Officer and copied the chairs-team (as the PDP update is done via the "plenary" WG). 3) In the following few days/weeks, there are some updates of the policy proposal, thanks to the inputs of the Policy Officer and even there is a request to the Board for their confirmation in one detail (no longer relevant in the attached version). 4) At the end of October, as a result of several inputs from the Policy Officer and the Board I've a final version, which however, gets new inputs from the chairs-team so my very last version is really final by 12 of November and I ask for immediate publication. 5) Chairs-team try to convince me that they don't agree with a paragraph from the proposal on December 1st, also they indicate that Xmas is a bad timing (which never minds because the discussion phase could be extended if there are no inputs, etc.). 6) Even if there have been several requests from my side for publication (we have been discussing a parallel topic for a report on the appeal process, which doesn't change my perspective on my proposal), I've asked several times for the immediate publication, which has not yet been done. I agree that a month, for an initial discussion with the staff, editorial inputs, etc., is acceptable, even if most of those discussions could actually happen just in 1-2 weeks, because they could take place in parallel, instead of sequentially as it has been the case. However, we have got 3 extra months (November, December, January), and the proposal is NOT YET PUBLISHED. Even worst, the last times I asked for the publication, I got NO RESPONSE from the chairs. As a consequence, in addition to make sure that this NEVER HAPPENS AGAIN (I mean in general, no violation of the PDP), I attach the proposal, so the staff, *following the mandate of the PDP* (not the chairs, which have no voice on this according to the PDP) publish it IMMEDIATELY and we can start a discussion of it, immediately. Thanks. 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.

12 29

Re: [ripe-list] repeated and continued PDP violation - WG chairs delaying or denying proposal publication - new policy proposal "Ensure Neutrality of PDP Appeals Procedure"
by Niall O'Reilly 09 Feb '21

09 Feb '21

Hi, Ondřej. Apologies for any confusion; I received two copies of this message and replied already to what looked like a private, off-list message. On 9 Feb 2021, at 14:08, Ondřej Surý wrote: > > also with my Arbiter hat on, this seems like quite widening the area that > RIPE Arbiters would have to cover. I don't think that enlisting the > Arbiters to cover the Appeals is something that could be done with their > consent. Agreed. Any change to the mandate of the RIPE NCC Arbiters could only be by consent. Indeed, I think that even to seek such consent from existing Arbiters would be to exercise undue pressure. If the RIPE Community were to decide to set up some kind of “RIPE PDP Appeal Panel”, I think that this would have to be formally quite separate from the RIPE NCC Panel of Arbiters. I don’t see any reason in principle not to allow anyone who might wish to volunteer for both panels do do so. I hope this reassures you. Niall

1 0

RIPE Working Group Chair Collective Meeting Summary
by Mirjam Kuehne 09 Feb '21

09 Feb '21

Dear colleagues, The RIPE Working Group Chairs met in January to review the appeal and to exchange experiences with regard to the RIPE Policy Development Process. We also discussed the meeting plan for the upcoming RIPE 82 Meeting. You can find a summary from the meeting here: https://www.ripe.net/participate/ripe/wg/wg-chairs/working-group-chair-coll… Kind regards, Mirjam Kühne RIPE Chair

10 18

New on RIPE Labs: #LetsGreenTheWeb with ClimateAction.tech
by Alun Davies 09 Feb '21

09 Feb '21

Dear colleagues, The #LetsGreenTheWeb campaign run by ClimateAction.tech kicks off next week. In this latest article on RIPE Labs, Michael Oghia talks about how the campaign calls on web developers, designers, and Internet users everywhere to get involved, learn more, and spread the word about sustainable web design: https://labs.ripe.net/Members/michael_oghia/letsgreentheweb-with-climateact… Kind regards, Alun Davies RIPE Labs Editor RIPE NCC

1 0

Call for Public Comments on the 2020 IANA Performance Matrix Summary Report
by Antony Gollan 04 Feb '21

04 Feb '21

This message is sent on behalf of the Number Resource Organization (NRO). *** Call for Public Comments on the 2020 IANA Performance Matrix Summary Report Dear colleagues, As you may be aware, as a result of the successful IANA Stewardship transition in 2016, the IANA Numbering Services are today being managed through an SLA between ICANN and the five Regional Internet Registries (RIRs). As part of the result of the IANA Stewardship transition, the IANA Numbering Services Review Committee (IANA RC) was established in 2016. The IANA RC is composed of representatives from each RIR region, and advises and assists the RIRs in the review of the IANA Numbering Services. The IANA services are today provided by Public Technical Identifiers (PTI), which publishes monthly performance reports on the IANA Numbering Services. Based on these monthly performance reports, the five RIRs have produced the 2020 IANA Performance Matrix Summary Report: https://www.nro.net/2020-RIR-IANA-summary-report 30 Day Public Comment Period The IANA RC is now launching a public comment period of 30 days, seeking comments and input from the community on the IANA numbering services performance and the 2020 IANA Performance Matrix Summary Report. The IANA RC encourages all members of the Internet number community to review the public IANA Performance Matrix Summary Report. Comments on the IANA service performance should be sent to: <iana-performance [at] nro [dot] net>. The IANA RC will publish an annual report in March 2021, as advice to the NRO EC with its evaluation of the IANA Numbering services. The report will be based on the IANA Performance Matrix Summary Report, as well as any input gathered on the performance from the global number community. The public comment period ends on Friday, 5 March 2021 at 23:59 UTC. All public comments will be published on the NRO website in the dedicated IANA RC section (https://www.nro.net/iana-rc-reports) and will be considered as input to the final report by IANA. At the end of the 30-day public comment period, the IANA RC will meet and evaluate all input to the final report. The final IANA RC 2020 Report will be published at: https://www.nro.net/iana-rc-reports <https://www.nro.net/iana-rc-reports Kind regards, Bertrand Cherrier Chair, IANA Numbering Services Review Committee Further Information IANA Numbering Services Review Committee https://www.nro.net/iana-rc Public Technical Identifiers (PTI) https://pti.icann.org/ IANA Stewardship Transition Archive https://www.nro.net/internet-governance/iana/iana-stewardship-transition The SLA for the IANA Numbering Services https://www.nro.net/sla IANA Stewardship Transition Number Community Proposal https://www.nro.net/crisp-final-proposal IANA RC Report 2019: https://www.nro.net/iana-rc-report-2019 IANA RC Report 2018 https://www.nro.net/iana-rc-report-2018 IANA RC Report 2017 https://www.nro.net/iana-rc-report-2017 *** Regards Antony Gollan Senior Communications Officer RIPE NCC

1 0

The DBTF needs your feedback!
by Bijal Sanghani 01 Feb '21

01 Feb '21

Dear colleagues, The DBTF (RIPE Database Requirements Task Force) would like to thank those that have given feedback so far on the published draft document - https://www.ripe.net/participate/ripe/tf/rdb-requirements-tf/the-ripe-datab… We appreciate the feedback given so far, however need a little bit more clarity on some aspects and have therefore published a new questionnaire to collect further feedback. Please can you take a few moments to compete this survey - https://www.surveymonkey.com/r/ZM222M3 You have until Monday, 15 February 2021 and the results will be reviewed and integrated by the task force in the final draft. More information about the task force is available at - https://www.ripe.net/participate/ripe/tf/rdb-requirements-tf Thank you for your participation! Kind regards, Bijal Sanghani RIPE DBTF Chair

1 0

New on RIPE Labs: Outcome of the AFRINIC Audit
by Alun Davies 28 Jan '21

28 Jan '21

Dear colleagues, Following the misappropriation of IPv4 resources that came to light in 2019, AFRINIC has completed a comprehensive audit of its WHOIS Database. In this new RIPE Labs article, we share their full report covering the outcomes of the audit: https://labs.ripe.net/Members/alun_davies/outcome-of-the-afrinic-audit Kind regards, Alun Davies RIPE NCC

1 0

IoT WG Survey
by Constanze Dietrich 11 Jan '21

11 Jan '21

Hi and happy new year everyone! I suspect whoever can afford it is, by now, in some kind of hibernation pre-stage waiting for the madness to be over (Wise choice!). That said, we (co-chairs of the Internet of Things Working Group) want to kick off 2021 by collecting some qualitative input from the RIPE community -- as to what IoT-related topics we should look into, what you'd like to see on the mailing list and during the sessions, who we may collaborate with, where we might contribute... So if you could spare a few minutes to fill in our survey -- that would be great! ;) Survey: https://docs.google.com/forms/d/e/1FAIpQLSdVVq38C96Mn_Lv8eDgiHGzt3TgzPfx_MM… Note: While we use the survey as a tool to collect feedback beyond the bounds of any mailing list, we intend to publish and discuss the results on the IoT WG mailing list. Cheers and kind regards Constanze Dietrich & Sandoche Balakrichenan

1 0

Invitation to the Internet Numbers Community to Participate as Observers in the ASO AC and IANA RC Teleconferences
by Boris Duval 05 Jan '21

05 Jan '21

This message is sent on behalf of the Number Resource Organization (NRO). *** The ASO[1] is one of ICANN’s three Supporting Organizations. They review and develop recommendations on Internet Protocol (IP) address policy and advise the ICANN Board on policy issues relating to the operation, assignment, and management of IP addresses. The ASO Address Council (ASO AC)[2] hold monthly teleconferences, usually on the first Wednesday of each month, with exceptions to avoid clashes with Regional Internet Registry meetings and other meetings relevant to the Internet Numbers Community. Likewise, the IANA Review Committee (IANA RC)[3] advises the NRO EC in its annual review of the service level of the IANA Numbering Services provided to the Regional Internet Registries. The IANA RC hold three or four teleconference meetings each year, on dates agreed by the members to prepare their annual report. The dates for the 2021 meetings of both groups are currently being updated and are available at the following links: ASO AC Meeting Schedule: https://aso.icann.org/aso-ac/meetings/aso-ac-meeting-schedule/ IANA RC Meetings Schedule: https://www.nro.net/accountability/operational/iana-numbering-services-revi… Both the ASO AC and the IANA RC meetings are open to observers. Zoom information is published at the above URLs on the eve of each meeting. =============== [1] Address Supporting Organization: https://aso.icann.org/ [2] Address Supporting Organization Address Council: https://aso.icann.org/aso-ac/ [3] IANA Review Committee: https://www.nro.net/accountability/operational/iana-numbering-services-revi… *** Best Regards, Boris Duval Communications Officer RIPE NCC

1 0

Happy New Year
by Mirjam Kuehne 01 Jan '21

01 Jan '21

Dear colleagues, 2020 presented us challenges which were unusual and demanding.   Thank you all for your commitment and cooperation in keeping this community together, and for maintaining and improving the network that we all rely on more than ever for our communications, for business and for staying in touch with friends and family. This is an amazing community that I am proud to support and contribute to. I look forward to our future work together, and I wish you all a very happy and healthy 2021. Best Regards, Mirjam Kühne RIPE Chair

1 0