[Gnso-epdp-team] Final report and consensus designation

[Mueller, Milton L]

Rafik,
Thanks for your efficient handling of the end game of the final report. NCSG is already reviewing the consensus designations. After another day of consultations we will likely submit one or two minor changes to our support indicators.  Our submissions will be made well before the July 29 deadline you have specified. We look forward to the submission of the final report to the GNSO Council by August 1.

An important part of your message below is that there is, in fact, a finish line to this process. We have been told by ICANN org and by many stakeholders how absolutely critical it is to have a standardized, globally coordinated method for disclosing nonpublic domain registration data. Some have even said the stability and security of the whole DNS depends on it! If this is true, we need to finish this and get the SSAD implemented as soon as possible.

When team EPDP crosses the finish line of the marathon I will support putting you on the podium to receive the gold medal on our behalf. I do not think we broke any world records for speed, but we did finish the race.

Dr. Milton L Mueller
Georgia Institute of Technology
School of Public Policy
Internet Governance Project<https://internetgovernance.org/>



From: Gnso-epdp-team <gnso-epdp-team-bounces at icann.org> On Behalf Of Rafik Dammak
Sent: Friday, July 24, 2020 6:30 AM
To: gnso-epdp-team at icann.org
Subject: [Gnso-epdp-team] Final report and consensus designation


Hi all,





We are reaching today an important milestone of our long journey. As promised, I am sharing with you the consensus designation I made for the policy recommendations.



Following the GNSO Working Group Guidelines provision, I am sharing here the first iteration of the consensus designation. Similar to phase 1, I am using a table to identify the consensus designation for each policy recommendation I believe has been achieved. The table also indicates which groups do not appear to support a recommendation or a part of it. The designation is based on the outcome of our latest deliberations this week and I made the assessment with the “cannot live with” as an indicator or where groups have indicated directly that they do not support certain recommendations, to select what I think is the appropriate level of consensus.



We managed to resolve the majority of “cannot live with” items identified, but unfortunately we were not able to do that for all. I have used those “cannot live with” items that we were not able to resolve as an indicator. I want also to highlight that in certain cases the “cannot live with” items went to a very specific part of the recommendation and I have taken a cautious approach and assumed that this meant a group is not able to live with the whole recommendation for the purpose of the consensus designation. Groups can of course correct that if it is not an accurate assumption. The document includes also the relevant provisions in the GNSO working group guidelines.



As mentioned previously, this is an iterative process but also not an endless one. So I would like to ask each group to indicate if they believe the consensus designation is not the correct one or the group has been incorrectly identified or not identified as not supporting certain recommendations. Please do that asap to help me to review the received input and make the necessary updates in a timely manner. I am hoping that this process will be straightforward and we all come swiftly to a general understanding on the consensus designations. The period of 24 to 29 July is for the EPDP Team to respond to consensus designations and share its feedback. For ease of use, you can use the table to share your input.



We tried our best to revolve concerns, reach agreements within the limits and constraints we are dealing with. The product is not perfect but it is the result of a consensus process and a lot of compromise. Although it would have been nice if the outcome of PDPs could make everybody happy and give everyone everything they want, unfortunately this is not possible, but it is important that we have a product you can accept and own. This is not the time for revisions or re-opening discussions but it is for finalizing our deliverable. So let’s stay focused.



I do believe that we did what we could do and deliberated on those topics to the extent of possible. I acknowledge there are disagreements and concerns. As I stated during the calls, you have the opportunity to get them on the record through the minority statement where you can go into details and explain your rationale. Even if you support a consensus position, you can still provide a statement to make your views heard. I urge you to submit them by deadline in order to be included, you don’t need to wait for the 29th July to do so. I recognize there may be some general dissatisfaction with some wanting more, others wanting less but at the end the group has come and worked together on delivering this report. The GNSO council will consider the final report and recommendations upon reception and will have to act on. Rest ensured that the report will be reviewed diligently.



I also acknowledge the frustration that some have about the remaining priority 2 issues not being addressed. I can reassure you that the GNSO Council is looking at how, not if, to address those topics in a timely manner and outlining the next steps and timing. It tasked a small team of councillors to come up with the proposal to be considered.



You can find the final report here: https://community.icann.org/x/K4LsBw .



Finally and on a less formal note, today was supposed to be the start of the Olympics game in Tokyo. Many described our EPDP as a marathon, definitely at an Olympic level of efforts and commitment. We are so close to the finishing line and we should celebrate soon the finalization of this phase.



Best Regards,



Rafik
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mm.icann.org/pipermail/gnso-epdp-team/attachments/20200724/c909d2bd/attachment-0001.html>