WEBVTT 1 00:00:00.000 --> 00:00:01.950 MTS - AV: Thank you, everyone. 2 00:00:02.760 --> 00:00:03.960 MTS - AV: Thank you. 3 00:00:04.190 --> 00:00:14.170 MTS - AV: Thanks, everyone, and welcome back. Before we start the session, let me give the floor to my colleague Fernanda to read the script. Fernanda? 4 00:00:15.970 --> 00:00:32.610 MTS - AV: Thanks, Sirinush. Hello, welcome back from lunch. Hope everyone was able to eat a little bit, wake up a bit now. And welcome to our How It Works ICANN Policy Session. My name is Fernanda Younes, and I'm a Participation Manager for the session. 5 00:00:32.689 --> 00:00:50.520 MTS - AV: Please note that this session is being recorded and is governed by the ICANN Community Participant Code of Conduct, ICANN Expected Standards of Behavior, and the ICANN Community Anti-Harassment Policy. Please observe the following guidelines to participate in this session. I'll also be posting them in the chat for your reference. 6 00:00:51.200 --> 00:01:00.320 MTS - AV: During the session, questions will only be read aloud if submitted within the Q&A pod. Interpretation for this session will include English, French, and Indonesian. 7 00:01:00.530 --> 00:01:08.780 MTS - AV: If you'd like to speak during the session, please raise your hand in Zoom. When called upon, virtual participants will be given permission to unmute in Zoom. 8 00:01:08.900 --> 00:01:12.530 MTS - AV: On-site participants will use a physical microphone to speak. 9 00:01:12.690 --> 00:01:19.740 MTS - AV: Only questions posted in the Q&A pod will be read aloud during the session, as time permits, and when directed by the chair of the session. 10 00:01:19.980 --> 00:01:27.029 MTS - AV: Please state your name for the record, the language you will speak if speaking a language other than English, and speak clearly and at a moderate pace. 11 00:01:27.200 --> 00:01:29.340 MTS - AV: Thank you. And Siranush, back to you. 12 00:01:29.810 --> 00:01:42.209 MTS - AV: Thank you very much. We have talked about two pillars of ICANN work, and one was technical, and we heard about IROS and IANA, how it works. 13 00:01:42.210 --> 00:01:54.779 MTS - AV: And now we are to another important pillar which ICANN is engaged is policy development because internet cannot work on its own. There should be policies in place. 14 00:01:54.820 --> 00:01:55.800 MTS - AV: And… 15 00:01:55.950 --> 00:02:08.330 MTS - AV: ICANN has a specific policy development processes for the communities, how they work, and it's my pleasure to have my colleague Ozan Sahin today. 16 00:02:08.330 --> 00:02:21.940 MTS - AV: with us, who will explain us how the policy works here, and which community pays what attention, and how this work in general, who then approve, and how it… 17 00:02:21.940 --> 00:02:29.729 MTS - AV: the entire process. And I will encourage all of you to use the opportunity to ask questions to Ozan. 18 00:02:30.540 --> 00:02:33.890 MTS - AV: And without further ado, Ozan, the floor is yours. 19 00:02:35.450 --> 00:02:42.830 MTS - AV: Thank you, Siranush. Hello, everyone. My name is Ozan Sahin, and it is great to be here with you this afternoon. 20 00:02:43.570 --> 00:02:53.149 MTS - AV: In this presentation, I will talk about ICANN policy and advice development, and I will start with an overview of the. 21 00:02:53.340 --> 00:03:03.100 MTS - AV: ICANN community, and also try to address your questions throughout the presentation. 22 00:03:16.030 --> 00:03:28.149 MTS - AV: So, on our first slide, what you see is the ICANN ecosystem, and you see three components there, the ICANN community, ICANN board, and ICANN organization. 23 00:03:28.550 --> 00:03:36.729 MTS - AV: And, what ICANN Committee does is to, develop the, policy. 24 00:03:36.860 --> 00:03:39.749 MTS - AV: and make recommendations to ICANN board. 25 00:03:39.910 --> 00:03:49.120 MTS - AV: And then ICANN board is the part, which reviews these recommendations and, and adopts them. 26 00:03:49.200 --> 00:04:07.050 MTS - AV: And then you see a line between the ICANN board and ICANN organization. ICANN board instructs the ICANN organization to implement these, adopted policies. And ICANN organization, works on, implementing these policies. 27 00:04:07.050 --> 00:04:16.820 MTS - AV: And also, you see a line between ICANN organization and ICANN community. The organization also supports the ICANN community in the development of 28 00:04:16.990 --> 00:04:21.619 MTS - AV: these policies and in the 29 00:04:21.850 --> 00:04:29.330 MTS - AV: slides to come, I will explain how the ICANN Post-Development Support Team supports these efforts. 30 00:04:32.710 --> 00:04:46.929 MTS - AV: In the next slide, we will start reviewing the ICANN supporting organizations. So, we have three of them. One is the address supporting organization. 31 00:04:47.290 --> 00:04:57.720 MTS - AV: And, this is the, numbers community, which work on… Policies on global, number resources. 32 00:04:57.760 --> 00:05:17.500 MTS - AV: And, there is an, address council. So, some of you may know that there are 5 regional internet registries in the world that deal with the allocation of number resources within their regions. And the address supporting organization, Address Council, is composed of 33 00:05:17.610 --> 00:05:20.809 MTS - AV: A total of 15 volunteers. 34 00:05:20.930 --> 00:05:32.399 MTS - AV: And, 3… 3 from each of these regional internet registries, so there's 5 of them, and… and the address council is composed of, 15 volunteers. 35 00:05:33.100 --> 00:05:41.990 MTS - AV: We have the contract code name supporting organization, or the CCNSO, where you will see the. 36 00:05:42.440 --> 00:05:45.010 MTS - AV: Country Code Top Level Domain Managers. 37 00:05:45.440 --> 00:05:52.900 MTS - AV: who have agreed to be members of the CCNSO, and there is also a CCNSO Council. 38 00:05:53.050 --> 00:06:01.170 MTS - AV: the executive body in the CCNSO. And then, we have the generic name supporting organization. 39 00:06:01.310 --> 00:06:07.940 MTS - AV: Which has the, both the contracted parties, which ICANN has contracts with. 40 00:06:08.070 --> 00:06:22.219 MTS - AV: And we also have non-contracted parties, and we will be, taking a closer look at how the GNSO Council is composed in the, in the next slides. 41 00:06:24.300 --> 00:06:28.750 MTS - AV: So these three supporting organizations do 42 00:06:28.760 --> 00:06:46.850 MTS - AV: develop policies. I think this slide… we can only see, like, half of this slide, but, and the font is, too small here. I will just drop a link in the chat if you would like to take a look at this infographic yourself, you can… you can do that. 43 00:06:46.870 --> 00:07:02.569 MTS - AV: And see the steps in the policy development process for each of these supporting organizations. There are some common themes, of course, across these three organizations in how they develop policies. 44 00:07:02.760 --> 00:07:15.680 MTS - AV: But today, let's take an example of the GNSO, or Generic Name Supporting Organization, and review how the policy development is done within the Generic Name Supporting Organization. 45 00:07:20.250 --> 00:07:24.760 MTS - AV: So, let's go to the overview of GNSL policy development. 46 00:07:25.120 --> 00:07:31.380 MTS - AV: And, and start with, the GNSO Council. 47 00:07:31.510 --> 00:07:48.289 MTS - AV: Which is divided into two houses, as I have mentioned, contracted and non-contracted parties, and the GNSO Council, work on the generic top-level domain, domain name policies, or GTLD policies. 48 00:07:52.240 --> 00:07:53.700 MTS - AV: So, 49 00:07:54.000 --> 00:08:08.279 MTS - AV: looking in detail in the composition of the GNSO Council, in the middle, down below GNSO Council, you see Registry Stakeholder Group and Registrar Stakeholder Group. 50 00:08:08.400 --> 00:08:15.739 MTS - AV: Which have contracts with ICANN. And also, on the left, you have commercial stakeholder group. 51 00:08:15.850 --> 00:08:24.670 MTS - AV: Which also splits into, three constituencies, the business constituency, intellectual property constituency. 52 00:08:24.790 --> 00:08:34.530 MTS - AV: and internet service providers and connectivity providers constituency. And on the right-hand side, you have a non-commercial stakeholder group. 53 00:08:34.640 --> 00:08:42.350 MTS - AV: Which has, two constituencies, the non-commercial users constituency and the not-for-profit. 54 00:08:42.350 --> 00:08:54.850 MTS - AV: organization's constituency. So, on the slide, the, idea is, you see that how, different interests can be represented in… within the GNSO Council. 55 00:08:55.260 --> 00:09:03.559 MTS - AV: And, this is how the GNSO Council is designed to, to actually, allow for this representation. 56 00:09:09.660 --> 00:09:13.789 MTS - AV: So, on the slide, you see. 57 00:09:17.340 --> 00:09:26.189 MTS - AV: details of the GNSO policy development process. And it all starts with the identification of an issue. 58 00:09:26.480 --> 00:09:35.009 MTS - AV: And, it can be GNSO Council, the ICANN board, or an advisory committee who comes up with an issue. 59 00:09:35.530 --> 00:09:47.009 MTS - AV: And then, the next step would be GNSO Council, considering if this issue will result in a consensus policy, if it's within the scope of the generic name supporting organization. 60 00:09:47.690 --> 00:09:56.330 MTS - AV: And if the GNSO Council determines that it is indeed within the GNSO scope. 61 00:09:56.460 --> 00:10:03.029 MTS - AV: Then, this would take us to the next step, which is the scoping, phase. 62 00:10:03.340 --> 00:10:16.559 MTS - AV: So in the scoping phase, the GNSO Council would request a preliminary issue report, and the staff publishes the preliminary issue report for public comment. 63 00:10:16.840 --> 00:10:24.539 MTS - AV: And, you may notice, there are some arrows on the both left and right-hand side. 64 00:10:24.820 --> 00:10:44.050 MTS - AV: These are on the slide to indicate the opportunities for the ICANN community to come in and provide their input, actually. So, in the first step, as you see, it's not only the GNSO Council, but the ICANN Board or Advisory Committee who can identify the issue. 65 00:10:44.050 --> 00:10:47.890 MTS - AV: And when we talk about the scoping phase, in the second step. 66 00:10:48.090 --> 00:10:53.109 MTS - AV: When staff publishes the preliminary issue report for public comment. 67 00:10:53.240 --> 00:11:00.049 MTS - AV: Again, the ICANN community may step in and provide their feedback into this process. 68 00:11:00.440 --> 00:11:12.410 MTS - AV: And then, once the public comment feedback is gathered, this is reviewed, and then final issue report is submitted for GNSO Council's consideration. 69 00:11:13.160 --> 00:11:20.450 MTS - AV: And this takes us to step 3, the initiation of a policy development process, or PDP. 70 00:11:20.740 --> 00:11:24.970 MTS - AV: And the GNSO Council considers the final issue report. 71 00:11:25.140 --> 00:11:41.290 MTS - AV: And, this is when they decide whether to initiate a policy development process. And if the GNSO Council says yes, then they adopt a charter for this new policy development process working group. 72 00:11:41.620 --> 00:11:49.290 MTS - AV: And then there's a call for volunteers, to form the, Post Development Process Working Group. 73 00:11:49.560 --> 00:12:06.939 MTS - AV: And this, takes us to the completion of the, initiation phase. And you also see an arrow, so, the GNSO Council may, when they, when they put up a call for volunteers, they may ask for 74 00:12:06.950 --> 00:12:21.089 MTS - AV: representatives from, other ICANN groups, ICANN advisory committees or supporting organizations who may, take their seat in the, in the working group. 75 00:12:21.560 --> 00:12:38.670 MTS - AV: On the next slide, you will see the remaining steps of the GNSL POS development process. So, we just initiated a working group, and this working group consults with the community and develops an initial report 76 00:12:38.720 --> 00:12:42.170 MTS - AV: And then eventually. 77 00:12:42.340 --> 00:12:52.130 MTS - AV: publishes this initial report for public comment, and this is also where you see an opportunity for feedback from the ICANN community. 78 00:12:52.420 --> 00:12:57.099 MTS - AV: The community would provide their feedback on the initial report. 79 00:12:57.270 --> 00:13:06.859 MTS - AV: And then, the working group Reviews all this feedback, and publishes their final report. 80 00:13:06.990 --> 00:13:23.529 MTS - AV: Which is submitted to the GNSO Council for its consideration. So, at ICANN 87, one of the policy development process, sessions that you will, you will see, and I think there was the first session in the morning. 81 00:13:23.710 --> 00:13:28.659 MTS - AV: is the DNS abuse mitigation, post-development process. 82 00:13:28.980 --> 00:13:42.910 MTS - AV: A few weeks ago, I think 2 or 3 weeks ago, this group's initial report was, open for public comment. If you went to the ICANN public comment webpage. 83 00:13:43.010 --> 00:14:00.369 MTS - AV: I think this, public comment received, 40, comments in total. And then, the PDP working group, what they are doing at ICANN 87 is reviewing this feedback gathered from ICANN community. 84 00:14:00.380 --> 00:14:14.420 MTS - AV: And I think they have 4 sessions here. One was in the morning, and the last one is, I think, on Thursday. So, they are reviewing this feedback in order to create their final report. This is where they are in this post-development process. 85 00:14:15.200 --> 00:14:20.589 MTS - AV: In the next phase, once the final report is submitted to the GNSO Council. 86 00:14:20.690 --> 00:14:27.109 MTS - AV: The GNSO Council would review it, and considers whether to adopt it. 87 00:14:27.210 --> 00:14:28.479 MTS - AV: Of course, this… 88 00:14:29.130 --> 00:14:40.769 MTS - AV: GNSO Council doesn't see it as a surprise, right? As the post-development process working group progresses its work. 89 00:14:40.800 --> 00:14:52.709 MTS - AV: There is regular reporting to GNSO Council, so the GNSO Council would be… would already be informed, where the working group is headed, what's new in the working group. 90 00:14:52.890 --> 00:15:07.689 MTS - AV: So, they, consider adoption of the final report in the, in the fifth phase, and then if GNSO Council, adopts it, the recommendations from this, working group 91 00:15:07.760 --> 00:15:20.430 MTS - AV: in the final report, go to ICANN board for, adoption. And this is step 6. ICANN board also consults with ICANN Committee and the GEC. 92 00:15:20.510 --> 00:15:28.420 MTS - AV: Before they take a vote on adopting the recommendations coming from this working group. 93 00:15:28.630 --> 00:15:37.089 MTS - AV: And after the, the, This consultation, the board takes a vote, and… 94 00:15:37.210 --> 00:15:48.049 MTS - AV: If adopted, the recommendations from the post-development process become effective. 95 00:15:49.510 --> 00:15:58.169 MTS - AV: So, these are the steps for the GNSO post-development process. I just wanted to pause and see any… 96 00:15:58.530 --> 00:16:04.530 MTS - AV: If you have any questions on this, or what have been presented so far. 97 00:16:09.960 --> 00:16:10.929 Louis Marius ANDRIAMPARANY: What should promote? 98 00:16:10.930 --> 00:16:12.929 MTS - AV: Alfredo? Alfredo, please. 99 00:16:17.930 --> 00:16:31.340 MTS - AV: Hello, my name is Alfredo Calderon, I'm a mentor for the NextGen program. Ozan, you mentioned that the board and the GAC have to review the… the final. 100 00:16:32.070 --> 00:16:33.060 MTS - AV: Oh. 101 00:16:34.140 --> 00:16:40.359 MTS - AV: policy to comment on it. Why does the GAC have to do that, and not just the board? 102 00:16:40.850 --> 00:16:41.710 MTS - AV: Thank you. 103 00:16:43.130 --> 00:16:54.010 MTS - AV: Thank you, Alfredo. Yes, there's a specific status of the GAC in this… 104 00:16:54.600 --> 00:17:12.809 MTS - AV: consultation period, and that's why in this phase, the board also needs to consult with the GAC to make sure they are okay with this, with the recommendations coming from PDP. So. 105 00:17:13.119 --> 00:17:15.900 MTS - AV: That's… that's written in the bylaws. 106 00:17:17.680 --> 00:17:21.549 MTS - AV: Just a reminder that Gac is the Governmental Advisory Committee. 107 00:17:22.420 --> 00:17:23.880 MTS - AV: Thank you, Fernanda. 108 00:17:24.260 --> 00:17:34.980 MTS - AV: Hello, thank you so much. My name is Goswe Kubi, a Fellow. Yes, so, following up with Alfredo's question, you know, the GAC is already representing in the PDP process. 109 00:17:35.420 --> 00:17:39.239 MTS - AV: So, I was also wondering why they need to… 110 00:17:39.470 --> 00:17:46.170 MTS - AV: be consulted again separately with the board before it's been voted for. And what if. 111 00:17:46.870 --> 00:17:49.800 MTS - AV: There is a disagreement at that level. What happens? 112 00:17:53.100 --> 00:18:03.740 MTS - AV: I think then, in case, there's a disagreement between the board and GAC, Then. 113 00:18:04.210 --> 00:18:10.969 MTS - AV: Set of meetings between the two groups start to iron out the differences and. 114 00:18:11.180 --> 00:18:13.830 MTS - AV: See if they can come to a mutual agreement. 115 00:18:13.970 --> 00:18:23.920 MTS - AV: And, I believe these are rare cases, because, as I already mentioned. 116 00:18:24.040 --> 00:18:43.380 MTS - AV: Any concerns, or issues about the policies being developed can, should not wait until the end when the final report is, you know, published. And this can be… and these are usually addressed very early in the process. 117 00:18:43.510 --> 00:18:49.409 MTS - AV: With the groups talking to each other at the early stages. 118 00:18:50.000 --> 00:18:59.160 MTS - AV: So, but again, if there's still disagreement in the end, there's a special, 119 00:19:00.020 --> 00:19:08.290 MTS - AV: There would be meetings between the groups to, again, see if there's a mutual ground to come to. 120 00:19:09.370 --> 00:19:28.159 MTS - AV: Alright, thank you so much. I said that because, you know, during… I'm part of the PDP process, I'm a participant for NCUC and NCSG, so… There were some few disagreements along the line, you know, not agreeing to what the NCSG community wants, and I also want the other, so that's what I'm just thinking. 121 00:19:28.160 --> 00:19:32.520 MTS - AV: It goes the other way around, where they also have a final decision to make. 122 00:19:32.550 --> 00:19:35.030 MTS - AV: You know, at the end of the day, it goes in their favor. 123 00:19:35.380 --> 00:19:40.070 MTS - AV: Because they will now make decision with the board, yeah, so that's why I was just present that. Thank you. 124 00:19:41.240 --> 00:19:48.870 MTS - AV: NCUC and CSG, they are part of non-commercial stakeholder group, and we will learn about them tomorrow. 125 00:19:49.030 --> 00:19:53.599 MTS - AV: But just to know that those acronyms will coming up. 126 00:20:00.420 --> 00:20:21.999 MTS - AV: Hello, my name is Sadiq Saha, I'm, with ICANN Fellowship Program, and from Nepal. So, I have a very simple question. As a… as you mentioned, when the, like, there is a public comments and everything, and, recently is in the NCSG group, so I'm quite of, like, getting lots of public comments, review of review, and everything, so… 127 00:20:22.000 --> 00:20:38.649 MTS - AV: I just wanted to know, like, from a young perspective, or, like, from a small country, when the public comment is there, how will… what is the process that… to know whether that comment is reflected in the ICANN policy or not? How can we know that? 128 00:20:39.720 --> 00:20:41.859 MTS - AV: Thank you for the question. So… 129 00:20:42.250 --> 00:20:57.740 MTS - AV: It's actually up to the working group to decide whether to, apply that comment or recommendation coming from the public comment process to their PDP process or not. 130 00:20:57.990 --> 00:21:09.400 MTS - AV: They would discuss it, and there would be a report of all the public comments received in the end, that is also published on the public comment website. 131 00:21:09.700 --> 00:21:16.630 MTS - AV: But if the working group decides not to follow the, comments received. 132 00:21:16.760 --> 00:21:22.300 MTS - AV: They would probably do that and maybe explain why they didn't follow it. 133 00:21:22.570 --> 00:21:25.830 MTS - AV: They don't have to, but that's usually the case. 134 00:21:26.100 --> 00:21:32.489 MTS - AV: And you may expect some, different comments. 135 00:21:32.620 --> 00:21:44.220 MTS - AV: during a public comment proceeding, so one would be conflicting with another comment, right? So, not all comments would be supporting a particular position. 136 00:21:44.410 --> 00:21:59.830 MTS - AV: And, again, in these cases, working group just, as they are doing for the DNS abuse mitigation PDP1 working group in this meeting at ICANN 87, they would review them, have a discussion about it. 137 00:21:59.990 --> 00:22:11.310 MTS - AV: And come to a conclusion, and then eventually, when they publish a report, they may explain why they followed a particular comment, or they didn't. 138 00:22:13.070 --> 00:22:18.970 MTS - AV: Jen, I saw you. You have your hand raised in the zoom. Please go ahead. If you have a question. 139 00:22:18.970 --> 00:22:35.580 MTS - AV: Yes, Jean-Jose Quijada from the Ayo Foundation, for the record. I was wondering, if maybe there's the reason why, those extra conversations, coming back to the topic from before, between the board and the GAC, has anything to do with the GAC situation in terms of voting? 140 00:22:36.330 --> 00:22:41.399 MTS - AV: in the board? Is it because they don't have voting power that they are extra consulted? 141 00:22:42.480 --> 00:22:44.450 MTS - AV: Before the voting happens. 142 00:22:44.990 --> 00:22:56.419 MTS - AV: Exactly, these are, you know, not waiting until the final vote, and they'd like to have a discussion. 143 00:22:56.490 --> 00:23:06.130 MTS - AV: And, if there are any concerns beforehand, they'd like to find a mutual ground beforehand, before it comes to voting, and have this conversation with the CAC 144 00:23:07.500 --> 00:23:08.380 MTS - AV: That's true. 145 00:23:11.710 --> 00:23:15.279 MTS - AV: I see a couple of questions here. Yes, please go ahead. 146 00:23:16.340 --> 00:23:26.160 MTS - AV: Okay, hello, everyone. My name is Jifanida Sabila. I'm from ICANN Fellows and from Rawijaya University, Indonesia. So, this is my question. 147 00:23:26.160 --> 00:23:40.440 MTS - AV: Some GNSO policy development process can take several years to complete. Were this process originally designed to take this long, or have they become more complex over time? What are the main factors contributing to this? 148 00:23:40.440 --> 00:23:42.070 MTS - AV: Delays. Thank you. 149 00:23:43.690 --> 00:23:52.010 MTS - AV: Thank you. Yes, the post-development process may take long in Many cases, couple of years. 150 00:23:52.300 --> 00:24:04.860 MTS - AV: And, I think this is, partly because there are so many different interests are represented within the… within a working group, so… You may need some time to… 151 00:24:05.000 --> 00:24:13.500 MTS - AV: come to come to an agreement with colleagues representing other interests. 152 00:24:13.720 --> 00:24:16.930 MTS - AV: But in time, 153 00:24:17.940 --> 00:24:26.729 MTS - AV: I think the ICANN community and the organization and the board heard so many feedback about, post-development process taking too long. 154 00:24:26.840 --> 00:24:36.310 MTS - AV: And, what happens today, when the GNSO Council, initiates a PDP is that there's a more. 155 00:24:36.710 --> 00:24:50.000 MTS - AV: project-oriented approach, and then you would have, you know, estimated timelines, and there's, regular reporting on how the policy development process progresses. 156 00:24:50.180 --> 00:25:00.060 MTS - AV: And, of course, there can be updates to the timelines based on how the discussions are going, but. 157 00:25:00.520 --> 00:25:02.830 MTS - AV: The effort is to ensure. 158 00:25:02.950 --> 00:25:17.080 MTS - AV: The PDP, you know, concludes, based on this, projections, and then, and then… 159 00:25:17.140 --> 00:25:28.800 MTS - AV: Because of the regular reporting, the GNSO Council, keeps, informed about the progress, and if any And. 160 00:25:29.470 --> 00:25:44.519 MTS - AV: issues need to be addressed at an earlier stage, that's what they do. So, yes, it can take long, but at the same time, the GNSO Council, which is the executive body within the GNSO, is trying to. 161 00:25:44.650 --> 00:25:54.659 MTS - AV: Apply a more structured approach, to, you know, to make the process more efficient. 162 00:25:57.180 --> 00:25:58.540 MTS - AV: Okay, thank you. 163 00:25:59.490 --> 00:26:08.460 MTS - AV: We have a Zoom question, so Fernanda will go for that question, and then we have the queue here. Yes, we have a question from Pramod Dhungana. 164 00:26:08.490 --> 00:26:19.710 MTS - AV: He's asking, given that countries have different national laws, regulatory frameworks, and public policy priorities, how can the GNSO and the GAC strengthen early engagement and development? 165 00:26:19.780 --> 00:26:33.610 MTS - AV: develop a structured negotiation mechanism that identifies common grounds while respecting national legal differences. Could ICANN establish a practical framework for resolving disagreements before policies reach the board? 166 00:26:38.150 --> 00:26:47.959 MTS - AV: Thank you for the question. Now, talking about different, national, jurisdiction or legislation. 167 00:26:49.100 --> 00:27:04.849 MTS - AV: So, when it comes to GNSO, we are talking about the consensus policies here, right? So these are the policies that would relate to generic top-level domains, and as I said. 168 00:27:04.850 --> 00:27:19.930 MTS - AV: the registries and registrars are the parties that have contracts with ICANN, and what is… unique for the GNSO development process is, once that happens, it results in a consensus policy, so… 169 00:27:19.940 --> 00:27:23.900 MTS - AV: You typically don't see a contract. 170 00:27:24.100 --> 00:27:27.570 MTS - AV: Getting changed afterwards, after it's signed. 171 00:27:27.740 --> 00:27:41.289 MTS - AV: But, what is unique here is that, any policy development process resulting in the, consensus policy, can update these contracts, so can change them. 172 00:27:41.500 --> 00:27:56.230 MTS - AV: And, you know, that's regardless of the national, national, rules or… legislation, so… And. 173 00:27:57.780 --> 00:28:00.489 MTS - AV: I don't know if that answers the question. 174 00:28:02.610 --> 00:28:11.749 MTS - AV: But, that's what it relates to the GNSO policy development process here. There can be. 175 00:28:12.860 --> 00:28:26.240 MTS - AV: Examples, of, you know, how, The differences in national policies may affect how these contracted parties would function. 176 00:28:26.420 --> 00:28:44.940 MTS - AV: But, again, these are… these are discussed in the, working group phase, and, you know, again, these contract parties and non-contract parties are represented within the working group, so… and these are part of the discussion in this case. 177 00:28:47.620 --> 00:28:51.910 MTS - AV: Thank you. We have a question. Amruta? Yes, please go ahead. 178 00:28:52.420 --> 00:29:08.209 MTS - AV: Hello, everyone. I'm Amrita. I'm a NextGen, and I'm from India. So first of all, thank you so much for this opportunity. My question is, what does I can take action if someone violates or refuse to follow the policies? 179 00:29:08.440 --> 00:29:13.610 MTS - AV: So I was just curious, like, have you ever experienced this? Like, yeah. 180 00:29:14.700 --> 00:29:23.580 MTS - AV: Thank you for the question. Now, the policies that we're talking about, specific to the GNSL post-development process, would… 181 00:29:23.850 --> 00:29:29.820 MTS - AV: affect the contracted parties, again, the registrars and registries. 182 00:29:29.970 --> 00:29:41.320 MTS - AV: So, if a contracted party would violate that, if someone has a complaint about it, ICANN has a contractual compliance function. 183 00:29:41.490 --> 00:29:54.940 MTS - AV: And, somebody can report this complaint about this violation to, this function, and then the, contractual compliance, team would review it. 184 00:29:55.100 --> 00:30:02.910 MTS - AV: See if it follows the contract, or if it's a violation, and then they may take the corrective action in this case. 185 00:30:04.920 --> 00:30:17.860 MTS - AV: Thank you. We have two people here in the queue, and if you raise your hand, I will see you, but we'll go with the lady, and then Godsway, then we'll come back to you. 186 00:30:19.030 --> 00:30:24.690 MTS - AV: You were… you wanted to ask a question, right? Yes, go ahead. Hello? 187 00:30:24.810 --> 00:30:37.660 MTS - AV: Thank you for the wonderful talk. My name is Anuza, I'm a computer engineering student from Nepal, and I'm a next-gen. So my question is, as you mentioned earlier, that consensus can take a long time. 188 00:30:37.660 --> 00:30:45.079 MTS - AV: In your experience, is it better to move slowly with a board agreement or other some kind of disagreement like that? 189 00:30:50.100 --> 00:30:54.889 MTS - AV: Thanks. It may be taking a long time, but in the end. 190 00:30:56.000 --> 00:30:58.790 MTS - AV: If you think about why it's taken a long time. 191 00:30:59.040 --> 00:31:03.320 MTS - AV: This is to, make sure that everyone 192 00:31:03.770 --> 00:31:09.980 MTS - AV: Everyone's concerns and issues are heard, if possible, addressed. 193 00:31:10.260 --> 00:31:19.210 MTS - AV: And, it's, it's basically taken a long time, because they want the end result to be. 194 00:31:19.410 --> 00:31:30.440 MTS - AV: satisfying all participating parties. So, I think the… that's why it's taken a long time, and, if it's serving this purpose. 195 00:31:30.490 --> 00:31:41.520 MTS - AV: then I think, you know, the… the result, could be worth… worth the time, if all the participating parties are happy in… if… if they are happy in the end. 196 00:31:42.680 --> 00:31:51.570 MTS - AV: Which is usually not the case, you know, in a setting where, the, there are different views, and… 197 00:31:52.200 --> 00:31:58.060 MTS - AV: And you need to find a mutual ground. You can… 198 00:31:58.780 --> 00:32:15.070 MTS - AV: You may probably rarely see that everyone is leaving the table in a happy mood, but to put it in a better statement, maybe, Everyone would be as happy as they can. 199 00:32:16.670 --> 00:32:18.409 MTS - AV: Godswing, please go ahead. 200 00:32:20.550 --> 00:32:35.419 MTS - AV: Well, it could be for the record. So, you know, I've been thinking of this, I think it came up in some of our sessions, ICANN85, which, you know, after we opened for public comments, and people put in public comments. 201 00:32:35.610 --> 00:32:53.669 MTS - AV: You know, how do they know that, their comments are actually accepted or rejected? And, I know it's kind of a lot of work if you have to reach out to everybody, but, you know, same… I believe same time the person put in the efforts to put in a comment, at least 202 00:32:53.800 --> 00:33:11.220 MTS - AV: There should be maybe a feedback, okay, my comments wasn't accepted because it doesn't meet this. For instance, the current PDP gave me a lot of exposure to know how this basically work, like how we are currently reviewing the recommendations and comments that came in. Okay, so after then, what happens? 203 00:33:11.220 --> 00:33:14.480 MTS - AV: Those who put in the comments, are they able to know that, okay. 204 00:33:14.480 --> 00:33:23.990 MTS - AV: my comments didn't move forward, or the community didn't accept it because of this. Is there anything we could do about such thing, you know? 205 00:33:25.850 --> 00:33:34.440 MTS - AV: Thank you. There's no requirement to, for the post-development process working group to 206 00:33:35.200 --> 00:33:40.930 MTS - AV: Explain why they didn't accept a particular comment or not. 207 00:33:41.120 --> 00:33:48.370 MTS - AV: But some of them do. Some of them take all the comments and have a discussion. 208 00:33:48.390 --> 00:34:05.620 MTS - AV: And they just also record the end result, what they decided on, and then put it in their public comment report. So there's no such requirement, but some of the working groups do that and explain why they follow the particular. 209 00:34:05.820 --> 00:34:07.130 MTS - AV: comment or not. 210 00:34:07.490 --> 00:34:08.650 MTS - AV: But no requirement. 211 00:34:10.320 --> 00:34:13.419 MTS - AV: Please come closer to the mic and ask your question. 212 00:34:15.280 --> 00:34:15.969 MTS - AV: Okay. 213 00:34:16.250 --> 00:34:23.309 MTS - AV: Hello, I'm Islam Khalid from the Fellowship program. My question is. 214 00:34:23.600 --> 00:34:32.269 MTS - AV: Since the policy development maybe take, like, 2 years or more for whatever the core issue. 215 00:34:32.330 --> 00:34:51.969 MTS - AV: that being, refining the policy to be developed, has a new input or, like, fundamental shift in the definition of the issue itself. Do we start the process from the first step, or at the current step of the policy development process? 216 00:34:52.960 --> 00:34:53.730 MTS - AV: Does it? 217 00:34:56.050 --> 00:35:06.740 MTS - AV: Would you mind repeating the question? Are you asking, if there are major differences between the parties, and if it's taken too long? 218 00:35:06.940 --> 00:35:09.110 MTS - AV: Then, what would we do, or… 219 00:35:10.160 --> 00:35:21.140 MTS - AV: Yeah, like, I mean, if in the middle of the development of the process, if we have, like, new inputs or updates in the core issue, what do we do in this situation? 220 00:35:22.970 --> 00:35:38.860 MTS - AV: new input, such as coming from public comments. So, if there's new input, that's definitely would be for the consideration of the working group. So, you know, the work… the existence of the working group is basically to… 221 00:35:39.210 --> 00:35:50.459 MTS - AV: review, the issue report that's available to them, and any additional input that may come throughout the discussion. So, one thing to… 222 00:35:50.840 --> 00:35:55.459 MTS - AV: Pay attention to is, you know, the… 223 00:35:56.790 --> 00:36:03.859 MTS - AV: GNSO Council and the working group has a specific scope. 224 00:36:03.870 --> 00:36:17.100 MTS - AV: So, one thing to determine is whether this additional input is within the scope or not. If it's in the scope, then I'm sure the working group would consider it, have a discussion about it. 225 00:36:17.100 --> 00:36:28.320 MTS - AV: But they may also determine that any additional input could be outside of their scope, and they may not have a discussion on it in this case. 226 00:36:31.590 --> 00:36:38.010 MTS - AV: We have a question from Roshate and one more over there from Camila and then we'll continue. 227 00:36:38.700 --> 00:36:46.119 MTS - AV: Hi, my name is Roshate. My question is related to the policy process within ICANN. 228 00:36:46.350 --> 00:36:56.790 MTS - AV: and overall. So, in my practice, as I've worked with the policy sector, too, back in my country, sometimes policies look good on paper, but 229 00:36:56.790 --> 00:37:21.760 MTS - AV: They do fail in practice. And this is not only, you know, pertaining to ICANN, it's everywhere, right? So my question would be that, is there any sort of reassessment done within ICANN's, final report or the policy process if the intended consequences are not achieved? Or is there any feedback mechanism, where you are sort of seeing implementation challenges and where you map it? 230 00:37:21.760 --> 00:37:24.470 MTS - AV: Back to the original policy process. 231 00:37:25.120 --> 00:37:38.029 MTS - AV: Thank you for the question. We have seen a few cases of that. I think it was the last ICANN public meeting where the board, unadopted some of the recommendations that they had initially adopted. 232 00:37:38.030 --> 00:37:45.820 MTS - AV: So, yes, there may be times, when, it is obvious for everyone that. 233 00:37:45.820 --> 00:37:52.949 MTS - AV: The previously adopted recommendations could be unadopted. 234 00:37:53.170 --> 00:38:06.179 MTS - AV: But the other side of your question is, you know, to, the implementability of the recommendations. To address that, we see a more. 235 00:38:06.970 --> 00:38:11.879 MTS - AV: A more common theme nowadays wants to… 236 00:38:11.960 --> 00:38:26.729 MTS - AV: recommendations are adopted, the organization, ICANN organization work with, continue to work with ICANN community, to do an assessment of the implementation and how. 237 00:38:26.730 --> 00:38:32.189 MTS - AV: How the feasibility would go in terms of implementation, so… 238 00:38:32.190 --> 00:38:45.110 MTS - AV: To make sure that the adopted recommendations would be implemented in the intended way, and also do the assessment that you just mentioned. 239 00:38:47.390 --> 00:38:50.040 MTS - AV: Camila Yep, no? 240 00:38:52.260 --> 00:39:00.280 MTS - AV: Hello, I'm Zainab. Zainab. And I'm an ICANN Fellow from Pakistan. So, I wanted to ask that. 241 00:39:00.630 --> 00:39:19.209 MTS - AV: I heard that the new GTLD round of applications just closed, right? And you also mentioned that the DNS abuse PDP is in place, too. So… and you again mentioned that this policy development process can be pretty slow. So, how does this… 242 00:39:19.290 --> 00:39:27.310 MTS - AV: Policy development body makes sure that with the new technical expansions, how does it make sure that. 243 00:39:27.410 --> 00:39:31.859 MTS - AV: The technical advancements, they do not outpace 244 00:39:32.130 --> 00:39:42.680 MTS - AV: The policy development process, like, how does this policy development body keep up with technical advancements and expansion of the domain namespace? 245 00:39:45.680 --> 00:39:49.010 MTS - AV: Thank you, Zeynep, for the question. I believe this is. 246 00:39:50.940 --> 00:39:59.270 MTS - AV: Based on the projections that the, the working group members would make during the, policy development process phase. 247 00:39:59.600 --> 00:40:03.089 MTS - AV: So, they, 248 00:40:03.260 --> 00:40:19.179 MTS - AV: try their best to make these projections, and sometimes they may also, need help from, ICANN organization, if they had particular questions, or, if they need a… 249 00:40:19.300 --> 00:40:28.929 MTS - AV: some, questions get answered, that would inform the post-development process. So, they would have this discussion within the working group. 250 00:40:29.040 --> 00:40:36.509 MTS - AV: And determine whether that's… that is sufficient for them to come to a conclusion and conclude the post-development process. 251 00:40:37.810 --> 00:40:38.670 MTS - AV: Thank you. 252 00:40:39.020 --> 00:40:39.720 MTS - AV: Thank you. 253 00:40:40.560 --> 00:40:43.310 MTS - AV: Do we want to continue or take more questions? 254 00:40:43.700 --> 00:40:48.179 MTS - AV: Are you okay? We have one more question. You're good? 255 00:40:49.200 --> 00:40:51.130 MTS - AV: Okay, let's go ahead. 256 00:40:51.260 --> 00:40:54.439 MTS - AV: Gentlemen, please come closer to the mic. 257 00:40:59.740 --> 00:41:11.989 MTS - AV: Yeah. Hi. I'm Daniel Hirsch from the DotMeow Foundation. As some of the people in this room may be aware, we are one of the, supported applicants to the next round. 258 00:41:12.110 --> 00:41:29.340 MTS - AV: of the new GDLD program. So, from a policy perspective, we were in quite a difficult position, because while many of the policies and procedures of the new GDLD program were being produced, we were not yet stakeholders. 259 00:41:30.040 --> 00:41:38.230 MTS - AV: And now we are in a situation where we can join the RYSG as a… Oh! 260 00:41:38.650 --> 00:41:40.320 MTS - AV: As an observing member. 261 00:41:40.580 --> 00:41:47.030 MTS - AV: But many of the decisions have already been made by parties that do not have our interests at heart. 262 00:41:47.220 --> 00:41:57.370 MTS - AV: How… or presumably this has been thought of, but how is this generally considered in the ICANN policy development process? 263 00:42:06.800 --> 00:42:10.030 MTS - AV: So, I'm trying to understand… 264 00:42:10.600 --> 00:42:18.080 MTS - AV: how that relates to post-development process. Could you please tell me again about your case, and… 265 00:42:18.580 --> 00:42:24.570 MTS - AV: Where you are having trouble in the post-development process? So, to be more specific. 266 00:42:24.730 --> 00:42:30.050 MTS - AV: Many of the policies around prioritization. 267 00:42:30.630 --> 00:42:35.349 MTS - AV: Prioritization is the big one that I've been considering recently. 268 00:42:35.680 --> 00:42:44.599 MTS - AV: were considered, prior to, many of the applicants… or supported applicants, from the Applicant Support Program. 269 00:42:46.930 --> 00:42:56.800 MTS - AV: And many of the decisions that were… or at least, the way that the prioritization process works is not something… or had we been consulted. 270 00:42:57.510 --> 00:43:08.090 MTS - AV: During that process, we would have made, specific recommendations. Quite reasonably, we were not, because at the time, we had not yet submitted an application. 271 00:43:08.390 --> 00:43:13.959 MTS - AV: Oh, there was no opportunity for a… there was no reason that you would have consulted us. 272 00:43:14.890 --> 00:43:17.180 MTS - AV: How would… Okay. 273 00:43:18.200 --> 00:43:23.979 MTS - AV: How is the process designed to take considerate or take this sort of situation to account? 274 00:43:24.130 --> 00:43:29.289 MTS - AV: Where the set of stakeholders changes as a policy is being developed. 275 00:43:30.250 --> 00:43:32.410 MTS - AV: Because that's really the core of my question. 276 00:43:33.590 --> 00:43:38.269 MTS - AV: I see, thank you. So, in terms of the order of things, what happens is. 277 00:43:38.540 --> 00:43:47.230 MTS - AV: You, set up a working group to work on a specific policy development process. 278 00:43:47.340 --> 00:44:02.689 MTS - AV: They work on the, issue, and then they come up with recommendations. And then, we had the post-development process for the subsequent, rounds of the, Niji TLDs. 279 00:44:02.850 --> 00:44:09.149 MTS - AV: And then, they… they've done their job, and then. 280 00:44:09.500 --> 00:44:16.019 MTS - AV: you know, now we have the 2026 rounds of that. So. 281 00:44:18.210 --> 00:44:22.199 MTS - AV: I don't know if that… at that point, they… there's a… 282 00:44:22.300 --> 00:44:36.209 MTS - AV: Specific reason why they should go back to the post-development process and visit if there is anything to change there until, you know, this, this, process is concluded. 283 00:44:36.340 --> 00:44:39.930 MTS - AV: So, if there are… 284 00:44:40.090 --> 00:44:55.609 MTS - AV: additional issues, problems with the process, then again, we go back to the first step of the post-doc on process. So, somebody would raise this issue, and then, you know, if it's within the scope of the GNSO, we would 285 00:44:55.690 --> 00:45:02.729 MTS - AV: complete step one, and then a new PDP may be set up to address the issue that's being raised. 286 00:45:07.340 --> 00:45:11.320 MTS - AV: Okay, I… yes, I see. Fia, please go ahead. 287 00:45:13.020 --> 00:45:24.889 MTS - AV: Talofalava, everyone. I'm Tupe Tulomalafaele, an academic from the National University of Samoa. Just a quick question with regards to. 288 00:45:25.540 --> 00:45:33.639 MTS - AV: the process number 6 vote by ICANN board. What's going to happen if there's a tie in the number of votes? 289 00:45:35.730 --> 00:45:38.170 MTS - AV: Thank you for the question. I am 290 00:45:39.690 --> 00:45:51.449 MTS - AV: To be honest, I'm not sure about the voting thresholds within the board to accept PDP, but obviously there are certain thresholds for a… 291 00:45:51.630 --> 00:45:54.020 MTS - AV: For the recommendations to be adopted. 292 00:45:56.010 --> 00:46:00.790 MTS - AV: So in this sense, I don't know what happens if there's a tie. 293 00:46:00.910 --> 00:46:03.350 MTS - AV: But… 294 00:46:04.220 --> 00:46:19.220 MTS - AV: Again, since these are parts of the board's discussions from the early stages. Any reason or concern that would result in a tie in the end would probably be addressed earlier. 295 00:46:19.300 --> 00:46:32.180 MTS - AV: So, we don't see, in many cases, a tie situation. But to the specific, answer to your question, I don't know what happens if there's a tie within the board. 296 00:46:33.680 --> 00:46:39.799 MTS - AV: But we can get back to you about it with… after consulting the board colleagues. 297 00:46:40.660 --> 00:46:42.110 MTS - AV: Thank you. Okay. 298 00:46:42.590 --> 00:46:43.420 MTS - AV: Cliff? 299 00:46:43.690 --> 00:46:45.090 MTS - AV: Go ahead, please. 300 00:46:46.560 --> 00:46:51.030 MTS - AV: Thank you. My name is Cliff, Fellow from Uganda. 301 00:46:51.360 --> 00:46:58.079 MTS - AV: From my understanding, a policy is usually framed around a problem. 302 00:46:58.570 --> 00:47:07.430 MTS - AV: My question is, what if, along the way, the definition of the problem changes? Is there a provision for adjustment? 303 00:47:08.670 --> 00:47:11.730 MTS - AV: Excuse me, can you repeat what if what changes? 304 00:47:12.100 --> 00:47:17.840 MTS - AV: In case the definition of the problem changes, especially now that we live. 305 00:47:18.180 --> 00:47:28.219 MTS - AV: in a world where there's Technology advancement that causes different factors to change around the problem. 306 00:47:28.430 --> 00:47:35.940 MTS - AV: Is there a provision for changing how you define the problem? Is there… For example. 307 00:47:36.580 --> 00:47:42.290 MTS - AV: Things like, a midterm review of the definition of the problem. 308 00:47:49.960 --> 00:48:01.449 MTS - AV: So, I think in response to this question, it's important to note a few things. One is, can we go back one slide? And it's your… I should do it myself. 309 00:48:02.990 --> 00:48:16.260 MTS - AV: So, again, it starts with a specific issue, and then the GNSO Council deciding whether it would result in a consensus policy. 310 00:48:17.080 --> 00:48:23.540 MTS - AV: If the nature of the issue changes in time when the PDP working group is working on it. 311 00:48:23.680 --> 00:48:38.370 MTS - AV: then probably the working group would consider whether it still makes sense to continue, under these new circumstances to have a meaningful result that would be adopted by the GNSO Council and later be adopted by the board. 312 00:48:38.660 --> 00:48:43.119 MTS - AV: And if they determine so, I think they would continue. 313 00:48:43.230 --> 00:48:51.750 MTS - AV: But if the answer is no, then again, that would take us to step one, and under these new, you know, circumstances. 314 00:48:51.750 --> 00:49:09.759 MTS - AV: Maybe the first initial effort would pause there, it wouldn't result in any consequence, but then we would start again with the new findings, new circumstances available to us, and see if there is a need for a new post-development process working group. 315 00:49:11.270 --> 00:49:12.110 MTS - AV: Thank you. 316 00:49:15.000 --> 00:49:20.700 MTS - AV: Don't see any hand raised here, and nobody in the Zoom, so we can continue. 317 00:49:22.770 --> 00:49:32.659 MTS - AV: Thanks, everyone, for the questions, and on the slide deck, next, we will talk about the advice development at ICANN 318 00:49:32.820 --> 00:49:45.989 MTS - AV: And we have 4 of them, 4 advisory committees. One is the At-Large Advisory Committee, which voices the interests of the individual internet users. 319 00:49:46.950 --> 00:49:53.839 MTS - AV: Within… At-Large Advisory Committee, we have 15 members. 320 00:49:54.000 --> 00:50:05.169 MTS - AV: As you may know, there are five Regional At-Large organizations within different geographic regions. 321 00:50:05.170 --> 00:50:20.820 MTS - AV: And, two representatives, come from these, each of the five, Regional Net-Large Organizations, and five of the members of the ALAC are appointed by the ICANN nominating committee. 322 00:50:21.120 --> 00:50:23.400 MTS - AV: So, we have 15 members. 323 00:50:24.710 --> 00:50:31.869 MTS - AV: The Governmental Advisory Committee provides advice on public policy issues. 324 00:50:32.050 --> 00:50:43.009 MTS - AV: And, it has, it has members, some of the organizations are, also members of the… 325 00:50:43.050 --> 00:51:02.550 MTS - AV: Governmental Advisory Committee. The two advisory committees, in the lower half are more technical advisory committees. The Root Server System Advisory Committee advises the ICANN community and the board on the operation. 326 00:51:02.620 --> 00:51:19.850 MTS - AV: administration, security, and integrity of the internet's root server system. There are 12, root server operators. Running, 13 root servers. And, they are also having meetings. 327 00:51:19.980 --> 00:51:28.530 MTS - AV: open to, ICANN community at ICANN87, so you can… you can also follow their meetings. 328 00:51:28.630 --> 00:51:43.330 MTS - AV: And the Security and Stability Advisory Committee, are, made of, experts on the security and integrity of internets. Naming and address allocation systems. 329 00:51:43.620 --> 00:51:49.220 MTS - AV: For instance, these two advisory committees, RSEC and SSEC, will be offering 330 00:51:49.330 --> 00:51:59.809 MTS - AV: an open microphone session, I believe, on Wednesday morning, so you can, again, go listen to them and ask your questions about their work. 331 00:52:00.300 --> 00:52:12.870 MTS - AV: So, how these advisory committees are developing their advice, we can go ahead and review that. Again, we have an infographic for each of them. 332 00:52:12.920 --> 00:52:21.960 MTS - AV: That you can review, and I'll drop a link in the chat if you want to take a closer look at these steps. 333 00:52:22.020 --> 00:52:29.000 MTS - AV: So, there's now a link in the chat for this infographic. 334 00:52:30.500 --> 00:52:45.700 MTS - AV: And, let's go to the next slide and, review the At-Large Advice Development process. We just said the At-Large Advisory Committee is the voice of the Individual internet end users. 335 00:52:46.040 --> 00:52:50.689 MTS - AV: And, provides advice, to the ICANN board. 336 00:52:52.640 --> 00:53:03.289 MTS - AV: So, in this advice development process. Any At-Large Committee member can bring up an issue to the consideration of the ALAC. 337 00:53:03.470 --> 00:53:08.359 MTS - AV: or at-large advisory committee, And again, you see. 338 00:53:09.350 --> 00:53:15.310 MTS - AV: similar step here, identification of the issue. It all starts with the identification of the issue, right? 339 00:53:15.540 --> 00:53:25.330 MTS - AV: And then the second step is, again, scoping phase. The At-Large Advisory Committee would have a discussion. 340 00:53:25.510 --> 00:53:38.109 MTS - AV: About the issue, and determine if it has an impact on the individual end users, and if it's within the, within its scope. And then. 341 00:53:39.320 --> 00:53:50.670 MTS - AV: In this phase, scoping phase, if it's found to be, having an impact on the individual end users, then, we go to the next step. 342 00:53:50.870 --> 00:53:56.730 MTS - AV: And then what happens is that the ALAC would designate an issue shepherd. 343 00:53:56.910 --> 00:54:03.149 MTS - AV: Within At-Large, there's a… there's a consolidated policy working group. 344 00:54:03.340 --> 00:54:23.170 MTS - AV: That works on, these potential issues, and there would be a call for volunteers wanting to work on this issue, and a small team would be set up to review the issue. 345 00:54:23.430 --> 00:54:34.600 MTS - AV: And then, the small team would report on, potential end-user impacts. To the Consolidated Post Working Group. 346 00:54:34.820 --> 00:54:42.900 MTS - AV: And then, if the Consolidated Policy Working Group, or CPWG, would like to continue drafting a statement. 347 00:54:43.060 --> 00:54:44.840 MTS - AV: Then, 348 00:54:45.630 --> 00:54:55.929 MTS - AV: Then, the small team would work on, drafting this statement, would present it to, Consolidate Post Working Group. 349 00:54:56.200 --> 00:55:05.940 MTS - AV: And then, based on the feedback received from CPWG, the small group would also 350 00:55:06.130 --> 00:55:10.070 MTS - AV: Draft a final statement. 351 00:55:10.530 --> 00:55:28.290 MTS - AV: which then also be, for consideration of the CPWG, and once, the Consolidated Policy Working Group is, okay with the, final statement, this statement goes to, the At-Large Advisory Committee. 352 00:55:28.340 --> 00:55:30.619 MTS - AV: for ReViva and Ratification. 353 00:55:30.770 --> 00:55:45.390 MTS - AV: And at the end of the ratification process, if ratified, the ALEC would send the advice to the ICANN board, ICANN organization, or other advisory committees or supporting organizations. 354 00:55:48.240 --> 00:55:53.519 MTS - AV: So that's how the advice development would work for the At-Large Advisory Committee. 355 00:55:54.810 --> 00:56:00.069 MTS - AV: And, on the next one, I'd like to talk about 356 00:56:00.270 --> 00:56:13.149 MTS - AV: How you can participate in this policy and advice development, because, especially for newcomers, it can be, hard to, you know. 357 00:56:14.640 --> 00:56:27.860 MTS - AV: start contributing to this, policy development process, advice development process, at an early stage. So, what you can do is, I talked about these working groups. 358 00:56:27.970 --> 00:56:41.880 MTS - AV: In the post-development process, we talked about formation of a working group. In the advice development process, there's, again, a team working on an issue, so you may consider joining an open 359 00:56:42.060 --> 00:56:47.169 MTS - AV: Working group or a community, and. 360 00:56:48.540 --> 00:57:03.230 MTS - AV: you may first hear other ICANN committee members who are contributing to the policy and advice development process, and observe how they are doing their, their contribution. 361 00:57:03.520 --> 00:57:12.979 MTS - AV: And this way, you would be informed about the hot topics, common discussion items. 362 00:57:13.140 --> 00:57:25.960 MTS - AV: And then, this would… this would help you, make your own contribution to the, Policy and advice development process. 363 00:57:26.100 --> 00:57:34.489 MTS - AV: Also, feel free to join mailing list to see the discussions and observe it. 364 00:57:34.710 --> 00:57:53.789 MTS - AV: Oftentimes, there are… there's a background to an issue being discussed, so I am subscribed to many mailing lists, so it helps me Understand the background, understand different views on a certain topic. 365 00:57:53.900 --> 00:57:57.539 MTS - AV: And that's what also you can also consider doing. 366 00:57:57.830 --> 00:58:17.169 MTS - AV: And also, we talked about the public comment process. And, on the issues that are open for public comment, you may consider, submitting your individual input, or, again, you would, you would. 367 00:58:17.570 --> 00:58:23.470 MTS - AV: see organizations, and we talked about supporting organizations, advisory committees. 368 00:58:23.840 --> 00:58:32.470 MTS - AV: Submitting their comment as a group, And if… if they can, And. 369 00:58:33.480 --> 00:58:43.609 MTS - AV: finalize a statement, finalize the group comment, and ratify it. Then they can submit this comment as a group input. 370 00:58:43.800 --> 00:58:57.539 MTS - AV: You can also, consider submitting your individual comment for public comment, or be part of the group that is developing this, advice, and the statement. 371 00:58:57.950 --> 00:59:00.860 MTS - AV: And participate in the public comment process. 372 00:59:03.890 --> 00:59:09.040 MTS - AV: We… Oh, we did have a question. Let's go ahead. Let's go. 373 00:59:10.530 --> 00:59:17.560 MTS - AV: Hello, my name is Sanjina Chhetri. I'm from Nepal. I'm a Nixon participant, here. 374 00:59:17.560 --> 00:59:39.140 MTS - AV: And my question is related to the At-Large community. I just wanted to know, as being a beginner, being a newcomer in this field, and there are many youths back in Nepal, and I'm sorry, in other countries as well, that they are interested to know about ALAC and maybe how to join those committees. 375 00:59:39.140 --> 00:59:46.269 MTS - AV: So I just wanted to know the process. Is there a pathway? Is it open to all or I don't know? 376 00:59:46.290 --> 00:59:48.730 MTS - AV: Just a bit about a pathway. 377 00:59:49.530 --> 00:59:51.260 MTS - AV: Thank you. 378 00:59:51.550 --> 01:00:09.389 MTS - AV: I see we also have some At-Large community members in the room, so please feel free to chime in if you'd like to add to that, but the grassroots of the At-Large community are, at-large structures, so within your region, you may consider contacting the, existing. 379 01:00:09.390 --> 01:00:17.040 MTS - AV: an At-Large structure, see how they work, and see if you can get engaged with them. 380 01:00:17.070 --> 01:00:20.750 MTS - AV: And then, and. 381 01:00:21.490 --> 01:00:26.829 MTS - AV: with these At-Large structures, you have the regional At-Large organizations within your regions, right? 382 01:00:26.940 --> 01:00:34.949 MTS - AV: It may be the case that there's no At-Large structure within your region. You may consider, setting up one. 383 01:00:35.070 --> 01:00:49.830 MTS - AV: And in some Regional At-Large organizations, individual membership is also allowed, so you may also consider that. And, once you become active within your region and regionally at-large organization. 384 01:00:49.900 --> 01:01:02.779 MTS - AV: then I think this is when you may consider taking on leadership roles, and then maybe serving on that Large Advisory Committee. So, of course. 385 01:01:03.600 --> 01:01:14.809 MTS - AV: you don't have to be in the At-Large Advisory Committee to, contribute to all these processes. You can just, you know. 386 01:01:15.200 --> 01:01:29.140 MTS - AV: You can observe the meetings of the, I mentioned, Consolidated Post Working Group. You can observe the meetings there, try to make your individual contribution to the issues being discussed. 387 01:01:29.360 --> 01:01:46.800 MTS - AV: And, basically, again, observe mailing lists, observe and participate in the meetings, make your contribution, and become active, and I think that's how you would be engaged in these communities. 388 01:01:48.010 --> 01:02:00.200 MTS - AV: Also, just a quick note, we will have, people from ALAC, coming to talk to you guys today at 4.30 as well, so you can talk to them further if you'd like. 389 01:02:00.580 --> 01:02:14.000 MTS - AV: So, the good thing that we have Ozan now explaining about those supporting organizations, SOs, and advisory committees, ACs, is that after this session. 390 01:02:14.000 --> 01:02:23.610 MTS - AV: Starting from the next one till tomorrow, the end of the day, we will hear from each and every one of those community coming. 391 01:02:23.610 --> 01:02:33.830 MTS - AV: and talking to us, and specifically talking and explaining about their particular community. So, this is the overview. 392 01:02:33.830 --> 01:02:44.520 MTS - AV: what is this multi-stakeholder model, and then we will hear from each and every one of them. So that's why this is important that we started from this 393 01:02:44.590 --> 01:02:55.329 MTS - AV: major overview of each community, and then you will have the opportunity to ask the question directly to At-Large, to GNSO. 394 01:02:55.630 --> 01:02:59.979 MTS - AV: to non-commercial stakeholder groups, etc. 395 01:03:02.430 --> 01:03:15.949 MTS - AV: Zainab has the question. Please go ahead. Hello again, I'm Zainab, I'm from Pakistan. So, you just mentioned that, about the advisory committees of ICANN, right? 396 01:03:16.070 --> 01:03:33.760 MTS - AV: But in the previous slide, we just saw that GAC gets to… GAC is only consulted before the final voting. So does that mean that in all the ACs, some sort of hierarchy exists, and GAC is on top of them, since GAC was consulted and others were ignored? 397 01:03:33.880 --> 01:03:39.890 MTS - AV: No, on the slide, you saw the, This… 398 01:03:40.920 --> 01:03:47.360 MTS - AV: Yeah, this one? No, I think it was referring to the post-development slide, I guess. 399 01:03:47.650 --> 01:03:57.250 MTS - AV: Let's see… here in the final step, yes, the board consults community and the GAC. So… 400 01:03:57.390 --> 01:04:02.129 MTS - AV: The GAC is called out here because it's, called out in the bylaws. 401 01:04:02.350 --> 01:04:14.019 MTS - AV: But it doesn't mean that the board would only consult with the GAC and wouldn't care about the rest of ICANN community. So when, the board typically opens a public comment. 402 01:04:14.070 --> 01:04:23.680 MTS - AV: And, all the ICANN community groups and individuals may submit their comments to this public comment proceeding, including the GAC. 403 01:04:23.790 --> 01:04:28.190 MTS - AV: But that doesn't mean others are left out. The… 404 01:04:29.240 --> 01:04:35.349 MTS - AV: The reason that Yak is all called out on the slide is that it's called out in the bylaws. 405 01:04:38.700 --> 01:04:46.340 MTS - AV: And by the way, during the week, the ICANN board will be meeting with, separately, with those 406 01:04:46.390 --> 01:04:55.620 MTS - AV: SO and ACs. So if you are interested, for example, in At-Large, it will be very interesting for you to go to 407 01:04:55.620 --> 01:05:08.610 MTS - AV: the session where board meets with At-Large. So you can see how… what type of questions At-Large raise in front of the board, and how the board is responding to that. So… 408 01:05:08.610 --> 01:05:22.029 MTS - AV: Keep in mind and look through the agenda and schedule that the board meets with different communities and make sure that you go and participate in the ones which you are interested in, okay? 409 01:05:24.630 --> 01:05:44.460 MTS - AV: Also, I'd like to remind one more thing about the post-development process and the formation of the, formation of the working group. So, if the GNSO Council is inviting, different ICANN advisory committees and supporting organizations to participate in the working group. 410 01:05:44.540 --> 01:05:52.750 MTS - AV: you know, in addition to the GAC, other advisory committees are also invited, so if they wish to participate, they can 411 01:05:52.750 --> 01:06:08.900 MTS - AV: appoint representatives to this group, and these representatives would regularly report back to their communities, and try to have an understanding of what their position is. 412 01:06:08.900 --> 01:06:25.819 MTS - AV: and then communicate this position back to the working group. So, since I'm also supporting, the At-Large Consolidated Policy Working Group activities, for instance, from the example that I gave about the DNS abuse mitigation PDP1, 413 01:06:26.070 --> 01:06:32.660 MTS - AV: At-Large also has representatives within the PDP working group, just like GAC. 414 01:06:32.730 --> 01:06:47.190 MTS - AV: And these, representatives, keep reporting back to At-Large, to consider, the working group discussions from an end-user perspective. And, any At-Large positions on 415 01:06:47.270 --> 01:07:00.230 MTS - AV: on the initial report recommendations, would be communicated back to working group, or, would be submitted to the ICANN public comment proceeding as at-large position on that. 416 01:07:04.830 --> 01:07:19.520 MTS - AV: Okay, now we're talking about ICANN public comment. I'd like to mention a few things, around the public comment that would make your participation in the, consultation period easier. So, when you go to 417 01:07:19.520 --> 01:07:33.129 MTS - AV: the ICANN webpage, you will see a tab for ICANN public comment. That's where you can go and see open public comment proceedings. 418 01:07:33.160 --> 01:07:41.889 MTS - AV: The ones that are pending their, reports, and the ones that have been, closed. 419 01:07:42.270 --> 01:08:00.339 MTS - AV: So, if you wanted to go see a public comment from 10 years ago, you can still go do that and see all the comments that were submitted for this public comment proceeding. You can also see the report that was published after the proceeding was closed. 420 01:08:02.680 --> 01:08:05.490 MTS - AV: On the next slide, so this is… 421 01:08:05.860 --> 01:08:20.849 MTS - AV: The current one, there's one open public comment as of today. And what you can also see on the public comment page is how many days left for you to be able to submit your comment. 422 01:08:20.910 --> 01:08:28.600 MTS - AV: If you look at the right-hand side, you can see when the proceeding was open for submissions, when it will be closed. 423 01:08:28.720 --> 01:08:40.849 MTS - AV: When the report will be due, and you can… you will also be able to see, down this box, the submissions that have already been submitted for this, proceeding. So… 424 01:08:40.910 --> 01:08:51.810 MTS - AV: you will be able to do that. And if you need to contact, the ICANN Org staff member, opening this 425 01:08:52.090 --> 01:09:02.750 MTS - AV: Public comment to ask for clarification, before you submit your comment, you can also see a contact information there. To do so. 426 01:09:05.010 --> 01:09:08.770 MTS - AV: Do we have any other questions around public comment, or anything else? 427 01:09:11.229 --> 01:09:12.390 MTS - AV: Yes, sounds fine. 428 01:09:16.689 --> 01:09:32.450 MTS - AV: Here I am again, Alfredo Calderon, mentor for the NextGen group. It's more than a question, it's a comment based on what Olsan has been saying. I'm a member of the At-Large community as well. 429 01:09:32.529 --> 01:09:41.580 MTS - AV: And I participate in some of the working groups, especially the Consolidated Policy Working Group. 430 01:09:41.960 --> 01:09:51.820 MTS - AV: We are one of the committees or the community groups that oversees most of the policies within ICANN. 431 01:09:52.000 --> 01:10:01.750 MTS - AV: So, but we do it from the perspective of the internet end user. So it's important for us that our voice is heard as 432 01:10:01.920 --> 01:10:14.099 MTS - AV: people or individuals that are going to eventually be using the internet based on those new policies. Now, the other thing is that, although I'm a member of an ALS, an At-Large 433 01:10:14.550 --> 01:10:17.169 MTS - AV: organization and structure. 434 01:10:17.900 --> 01:10:19.600 MTS - AV: to rule my country. 435 01:10:19.720 --> 01:10:25.780 MTS - AV: I can also write individual as an individual, a public comment. 436 01:10:26.040 --> 01:10:45.159 MTS - AV: So, in some cases, if you go through the page, you'll see that I've made personal comments, but I've also made comments through the working group, because the perspective might be different, although we're talking about the same policy, okay? So… so don't… 437 01:10:45.530 --> 01:11:01.619 MTS - AV: feel that you're obligated to do it through the working group, you can do it also as an individual. And actually, I encourage some of you that have sort of a different opinion of what the working group is developing to write your own personal individual comments. 438 01:11:01.780 --> 01:11:12.000 MTS - AV: But keep in mind that your name is going to appear on that individual public comment that you're making. So make sure that your comment 439 01:11:12.110 --> 01:11:13.910 MTS - AV: is important. 440 01:11:14.030 --> 01:11:23.449 MTS - AV: It contributes to the resolution or the proceeding that is being consulted, and that it's documented. 441 01:11:23.650 --> 01:11:28.260 MTS - AV: Don't write something for the sake of writing it. It has to… 442 01:11:28.630 --> 01:11:33.809 MTS - AV: Contribute in some ways to, the policy process. 443 01:11:34.180 --> 01:11:34.980 MTS - AV: Thank you. 444 01:11:38.680 --> 01:11:40.809 MTS - AV: Do we have one more question? 445 01:11:41.880 --> 01:11:48.900 MTS - AV: Okay, I think we have a few minutes left. How many questions do you think we can take? Two? 446 01:11:49.650 --> 01:11:56.690 MTS - AV: We will take one question here and one there. Those who didn't ask questions during We'll come back. 447 01:11:57.100 --> 01:11:57.980 MTS - AV: Okay. 448 01:11:58.270 --> 01:12:06.220 MTS - AV: Hello, everyone. My name is Solange Olude. I'm from Bene. I'm a Folo. 449 01:12:06.400 --> 01:12:12.749 MTS - AV: And thank you very much for this opportunity, and… Thank you for your presentation. 450 01:12:13.340 --> 01:12:14.510 MTS - AV: I have. 451 01:12:15.540 --> 01:12:18.270 MTS - AV: One question. My question is. 452 01:12:18.600 --> 01:12:32.920 MTS - AV: For a fellows who want to remain actively involved in ICANN's policy development process After the meeting, Wal wool. 453 01:12:33.070 --> 01:12:39.010 MTS - AV: Your recommendation… your recommendation as most first step. 454 01:12:39.390 --> 01:12:44.810 MTS - AV: to take, especially for someone who still builds them experience. 455 01:12:45.440 --> 01:12:59.520 MTS - AV: I… I asked this question because this is the topic I'm generally interested in, and I love to learn how I can become more actively involved. 456 01:13:00.870 --> 01:13:06.330 MTS - AV: Thank you. Thank you. So again, based on your interest, profession. 457 01:13:06.510 --> 01:13:20.650 MTS - AV: We mentioned some ICANN community groups, you know, advisory committees and supporting organizations. For instance, we saw many different interests represented under GNSO community. 458 01:13:20.650 --> 01:13:27.209 MTS - AV: For the, non-commercial users, not-for-profit organizations. 459 01:13:27.210 --> 01:13:33.920 MTS - AV: And then for commercial part, you have business constituency, intellectual property constituency. 460 01:13:34.030 --> 01:13:41.439 MTS - AV: Internal service providers, and then the contracted parties. Let's say if you are. 461 01:13:41.590 --> 01:13:53.140 MTS - AV: technical person who is interested in the DNS, and also working on DNS root server system, maybe. 462 01:13:53.140 --> 01:14:05.599 MTS - AV: then in this case, you can apply to become a member of RSEC Caucus, which is composed of DNS experts 463 01:14:05.600 --> 01:14:20.529 MTS - AV: who contribute to the work of RSEC and RSEC publications. So, RSEC also can start a work party or work group, and may seek help from the RSEC caucus to work on this issue. And. 464 01:14:20.610 --> 01:14:33.230 MTS - AV: you know, you should, I think, review these advisory committees and supporting organizations, and see what's the best fit for you, and consider maybe applying for a membership 465 01:14:33.330 --> 01:14:52.469 MTS - AV: For these groups, so you can contribute to their policy or advice development process being attached or being a member of this group. And then the other steps, you can consider joining working groups, and if it's, you may… 466 01:14:52.520 --> 01:15:05.400 MTS - AV: Be more familiar with the topics being discussed by being a member of an existing group, and then you can consider joining the open working groups to contribute even more. 467 01:15:05.400 --> 01:15:16.650 MTS - AV: And then observing mailing lists are… is always a good step in the initial stages. So, And… 468 01:15:17.100 --> 01:15:36.579 MTS - AV: you know, there's a mailing list for the RSEC Caucus that I mentioned, the working groups within various advisory committees, supporting organizations, so you can consider signing up to this mailing list. And then public comment is very informative as well. 469 01:15:36.580 --> 01:15:39.459 MTS - AV: When there is a report 470 01:15:39.460 --> 01:15:46.910 MTS - AV: Offer public comment. There's a detail, information, and you can go read it, and then. 471 01:15:46.910 --> 01:15:48.310 Jovita Kanza, ICANN87 Fellow: Great meeting. 472 01:15:48.600 --> 01:15:50.330 Jovita Kanza, ICANN87 Fellow: Reading room… 473 01:15:53.630 --> 01:16:10.879 MTS - AV: Are we good now? Okay. Reading the comments that are submitted, this is the public comment, is also informative, so you can see all these different views. That's why that would be my recommendation if you wanted to, engage more and participate in this, policy advice development. 474 01:16:11.600 --> 01:16:12.789 MTS - AV: Thank you. 475 01:16:13.510 --> 01:16:15.830 MTS - AV: Very brief, 10 seconds. 476 01:16:17.420 --> 01:16:18.840 MTS - AV: AL 477 01:16:18.840 --> 01:16:42.979 MTS - AV: Hello, everyone. My name is Siddhanth Pant. I'm a computer engineering student from Nepal, participating here as a NextGen. So, as you told earlier that the comments may contradict with each other, so many people may have different perspectives, and they may be opposing from each other. So, how does the working group determine whether to compromise or to declare no consensus? Thank you. That would be my question. 478 01:16:45.680 --> 01:16:49.270 MTS - AV: Thank you for the question. So… 479 01:16:52.240 --> 01:17:00.490 MTS - AV: Defining the consensus or, you know, determining a consensus, is often… 480 01:17:00.650 --> 01:17:14.130 MTS - AV: left to, working group leadership. And the working group leadership should be, working under certain, You know. 481 01:17:18.800 --> 01:17:24.750 MTS - AV: talents, I would say, and, some. 482 01:17:25.010 --> 01:17:41.429 MTS - AV: when conducting the leadership for the working group, they should be, seeking, you know, a balanced approach. If there are different views, they should be allowing, you know, different voices in. 483 01:17:41.430 --> 01:17:45.309 MTS - AV: Encouraging that kind of atmosphere within the working group. 484 01:17:45.400 --> 01:17:54.800 MTS - AV: So, when it comes to, determining consensus, the working group leadership may say. 485 01:17:55.430 --> 01:18:13.529 MTS - AV: Okay, do you have any objections to such recommendations? And maybe there are some objections, and the working group would try to understand how they can really address these issues. And. 486 01:18:13.640 --> 01:18:17.650 MTS - AV: They could ask the question if, you know. 487 01:18:20.610 --> 01:18:31.300 MTS - AV: If the working group members could live with the recommendations, or there are certain, things that should be taken out, because they're not happy with it. 488 01:18:31.300 --> 01:18:55.279 MTS - AV: In these cases, if there are such things, the working group may consider, you know, taking these out and then continue with the rest of the recommendations where you may this time achieve a consensus. This is what we observe in the working groups. So that's why there's always a reporting back, taking feedback from the appointing advisory committees, supporting organizations. 489 01:18:55.370 --> 01:19:10.499 MTS - AV: And if there are certain no's on some of the recommendations, then the leadership may think of, you know, progressing with the rest of the items and taking the work to a finish. 490 01:19:11.880 --> 01:19:18.549 MTS - AV: Thank you, Ozan, and thank you very much for this very interesting session. I hope… 491 01:19:18.680 --> 01:19:37.890 MTS - AV: It was good starting point for you to understand how policy development process works here within ICANN community, but that also give you the thoughts for the week to get to make a deep dive and to learn more, to meet people, to talk to community members. 492 01:19:37.890 --> 01:19:46.779 MTS - AV: And, before we go to the next session, we are starting the series of Get to Know ICANN Community. 493 01:19:46.780 --> 01:19:58.170 MTS - AV: from the next session till the end of tomorrow, so I'm looking forward to seeing you back at 3 p.m. here. And for now, this meeting is adjourned. There is a coffee break. 494 01:19:58.170 --> 01:20:03.340 MTS - AV: Please go enjoy and come back here in 25 minutes. Thank you.