{ "session_id": "icann87-sched-2Wjef", "canonical_id": "icann87-sched-2Wjef", "segments": [ { "start": 0.0, "end": 1.95, "text": "MTS - AV: Thank you, everyone." }, { "start": 2.76, "end": 3.96, "text": "MTS - AV: Thank you." }, { "start": 4.19, "end": 14.17, "text": "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?" }, { "start": 15.97, "end": 32.61, "text": "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." }, { "start": 32.689, "end": 50.52, "text": "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." }, { "start": 51.2, "end": 60.32, "text": "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." }, { "start": 60.53, "end": 68.78, "text": "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." }, { "start": 68.9, "end": 72.53, "text": "MTS - AV: On-site participants will use a physical microphone to speak." }, { "start": 72.69, "end": 79.74, "text": "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." }, { "start": 79.98, "end": 87.029, "text": "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." }, { "start": 87.2, "end": 89.34, "text": "MTS - AV: Thank you. And Siranush, back to you." }, { "start": 89.81, "end": 102.209, "text": "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." }, { "start": 102.21000000000001, "end": 114.779, "text": "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." }, { "start": 114.82, "end": 115.8, "text": "MTS - AV: And…" }, { "start": 115.95, "end": 128.33, "text": "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." }, { "start": 128.33, "end": 141.94, "text": "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…" }, { "start": 141.94, "end": 149.72899999999998, "text": "MTS - AV: the entire process. And I will encourage all of you to use the opportunity to ask questions to Ozan." }, { "start": 150.54, "end": 153.89, "text": "MTS - AV: And without further ado, Ozan, the floor is yours." }, { "start": 155.45, "end": 162.82999999999998, "text": "MTS - AV: Thank you, Siranush. Hello, everyone. My name is Ozan Sahin, and it is great to be here with you this afternoon." }, { "start": 163.57, "end": 173.149, "text": "MTS - AV: In this presentation, I will talk about ICANN policy and advice development, and I will start with an overview of the." }, { "start": 173.34, "end": 183.1, "text": "MTS - AV: ICANN community, and also try to address your questions throughout the presentation." }, { "start": 196.03, "end": 208.149, "text": "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." }, { "start": 208.55, "end": 216.72899999999998, "text": "MTS - AV: And, what ICANN Committee does is to, develop the, policy." }, { "start": 216.86, "end": 219.749, "text": "MTS - AV: and make recommendations to ICANN board." }, { "start": 219.91, "end": 229.12, "text": "MTS - AV: And then ICANN board is the part, which reviews these recommendations and, and adopts them." }, { "start": 229.2, "end": 247.05, "text": "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." }, { "start": 247.05, "end": 256.82, "text": "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" }, { "start": 256.99, "end": 261.619, "text": "MTS - AV: these policies and in the" }, { "start": 261.85, "end": 269.33, "text": "MTS - AV: slides to come, I will explain how the ICANN Post-Development Support Team supports these efforts." }, { "start": 272.71, "end": 286.929, "text": "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." }, { "start": 287.29, "end": 297.72, "text": "MTS - AV: And, this is the, numbers community, which work on… Policies on global, number resources." }, { "start": 297.76, "end": 317.5, "text": "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" }, { "start": 317.61, "end": 320.809, "text": "MTS - AV: A total of 15 volunteers." }, { "start": 320.93, "end": 332.399, "text": "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." }, { "start": 333.1, "end": 341.99, "text": "MTS - AV: We have the contract code name supporting organization, or the ccNSO, where you will see the." }, { "start": 342.44, "end": 345.01, "text": "MTS - AV: Country Code Top Level Domain Managers." }, { "start": 345.44, "end": 352.9, "text": "MTS - AV: who have agreed to be members of the CCNSO, and there is also a CCNSO Council." }, { "start": 353.05, "end": 361.17, "text": "MTS - AV: the executive body in the ccNSO. And then, we have the generic name supporting organization." }, { "start": 361.31, "end": 367.94, "text": "MTS - AV: Which has the, both the contracted parties, which ICANN has contracts with." }, { "start": 368.07, "end": 382.219, "text": "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." }, { "start": 384.3, "end": 388.75, "text": "MTS - AV: So these three supporting organizations do" }, { "start": 388.76, "end": 406.85, "text": "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." }, { "start": 406.87, "end": 422.569, "text": "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." }, { "start": 422.76, "end": 435.68, "text": "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." }, { "start": 440.25, "end": 444.76, "text": "MTS - AV: So, let's go to the overview of GNSL policy development." }, { "start": 445.12, "end": 451.38, "text": "MTS - AV: And, and start with, the GNSO Council." }, { "start": 451.51, "end": 468.289, "text": "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." }, { "start": 472.24, "end": 473.7, "text": "MTS - AV: So," }, { "start": 474.0, "end": 488.279, "text": "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." }, { "start": 488.4, "end": 495.739, "text": "MTS - AV: Which have contracts with ICANN. And also, on the left, you have commercial stakeholder group." }, { "start": 495.85, "end": 504.67, "text": "MTS - AV: Which also splits into, three constituencies, the business constituency, intellectual property constituency." }, { "start": 504.79, "end": 514.53, "text": "MTS - AV: and internet service providers and connectivity providers constituency. And on the right-hand side, you have a non-commercial stakeholder group." }, { "start": 514.64, "end": 522.35, "text": "MTS - AV: Which has, two constituencies, the non-commercial users constituency and the not-for-profit." }, { "start": 522.35, "end": 534.85, "text": "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." }, { "start": 535.26, "end": 543.559, "text": "MTS - AV: And, this is how the GNSO Council is designed to, to actually, allow for this representation." }, { "start": 549.66, "end": 553.789, "text": "MTS - AV: So, on the slide, you see." }, { "start": 557.34, "end": 566.189, "text": "MTS - AV: details of the GNSO policy development process. And it all starts with the identification of an issue." }, { "start": 566.48, "end": 575.009, "text": "MTS - AV: And, it can be GNSO Council, the ICANN board, or an advisory committee who comes up with an issue." }, { "start": 575.53, "end": 587.009, "text": "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." }, { "start": 587.69, "end": 596.33, "text": "MTS - AV: And if the GNSO Council determines that it is indeed within the GNSO scope." }, { "start": 596.46, "end": 603.029, "text": "MTS - AV: Then, this would take us to the next step, which is the scoping, phase." }, { "start": 603.34, "end": 616.559, "text": "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." }, { "start": 616.84, "end": 624.539, "text": "MTS - AV: And, you may notice, there are some arrows on the both left and right-hand side." }, { "start": 624.82, "end": 644.05, "text": "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." }, { "start": 644.05, "end": 647.89, "text": "MTS - AV: And when we talk about the scoping phase, in the second step." }, { "start": 648.09, "end": 653.109, "text": "MTS - AV: When staff publishes the preliminary issue report for public comment." }, { "start": 653.24, "end": 660.049, "text": "MTS - AV: Again, the ICANN community may step in and provide their feedback into this process." }, { "start": 660.44, "end": 672.41, "text": "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." }, { "start": 673.16, "end": 680.45, "text": "MTS - AV: And this takes us to step 3, the initiation of a policy development process, or PDP." }, { "start": 680.74, "end": 684.97, "text": "MTS - AV: And the GNSO Council considers the final issue report." }, { "start": 685.14, "end": 701.29, "text": "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." }, { "start": 701.62, "end": 709.29, "text": "MTS - AV: And then there's a call for volunteers, to form the, Post Development Process Working Group." }, { "start": 709.56, "end": 726.939, "text": "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" }, { "start": 726.95, "end": 741.0889999999999, "text": "MTS - AV: representatives from, other ICANN groups, ICANN advisory committees or supporting organizations who may, take their seat in the, in the working group." }, { "start": 741.56, "end": 758.67, "text": "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" }, { "start": 758.72, "end": 762.17, "text": "MTS - AV: And then eventually." }, { "start": 762.34, "end": 772.13, "text": "MTS - AV: publishes this initial report for public comment, and this is also where you see an opportunity for feedback from the ICANN community." }, { "start": 772.42, "end": 777.099, "text": "MTS - AV: The community would provide their feedback on the initial report." }, { "start": 777.27, "end": 786.859, "text": "MTS - AV: And then, the working group Reviews all this feedback, and publishes their final report." }, { "start": 786.99, "end": 803.529, "text": "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." }, { "start": 803.71, "end": 808.659, "text": "MTS - AV: is the DNS abuse mitigation, post-development process." }, { "start": 808.98, "end": 822.91, "text": "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." }, { "start": 823.01, "end": 840.369, "text": "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." }, { "start": 840.38, "end": 854.42, "text": "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." }, { "start": 855.2, "end": 860.5889999999999, "text": "MTS - AV: In the next phase, once the final report is submitted to the GNSO Council." }, { "start": 860.69, "end": 867.109, "text": "MTS - AV: The GNSO Council would review it, and considers whether to adopt it." }, { "start": 867.21, "end": 868.479, "text": "MTS - AV: Of course, this…" }, { "start": 869.13, "end": 880.769, "text": "MTS - AV: GNSO Council doesn't see it as a surprise, right? As the post-development process working group progresses its work." }, { "start": 880.8, "end": 892.7090000000001, "text": "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." }, { "start": 892.89, "end": 907.689, "text": "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" }, { "start": 907.76, "end": 920.43, "text": "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." }, { "start": 920.51, "end": 928.42, "text": "MTS - AV: Before they take a vote on adopting the recommendations coming from this working group." }, { "start": 928.63, "end": 937.0889999999999, "text": "MTS - AV: And after the, the, This consultation, the board takes a vote, and…" }, { "start": 937.21, "end": 948.049, "text": "MTS - AV: If adopted, the recommendations from the post-development process become effective." }, { "start": 949.51, "end": 958.169, "text": "MTS - AV: So, these are the steps for the GNSO post-development process. I just wanted to pause and see any…" }, { "start": 958.53, "end": 964.53, "text": "MTS - AV: If you have any questions on this, or what have been presented so far." }, { "start": 969.96, "end": 970.929, "text": "Louis Marius ANDRIAMPARANY: What should promote?" }, { "start": 970.93, "end": 972.929, "text": "MTS - AV: Alfredo? Alfredo, please." }, { "start": 977.93, "end": 991.34, "text": "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." }, { "start": 992.07, "end": 993.06, "text": "MTS - AV: Oh." }, { "start": 994.14, "end": 1000.359, "text": "MTS - AV: policy to comment on it. Why does the GAC have to do that, and not just the board?" }, { "start": 1000.85, "end": 1001.71, "text": "MTS - AV: Thank you." }, { "start": 1003.13, "end": 1014.01, "text": "MTS - AV: Thank you, Alfredo. Yes, there's a specific status of the GAC in this…" }, { "start": 1014.6, "end": 1032.809, "text": "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." }, { "start": 1033.119, "end": 1035.9, "text": "MTS - AV: That's… that's written in the bylaws." }, { "start": 1037.68, "end": 1041.549, "text": "MTS - AV: Just a reminder that GAC is the Governmental Advisory Committee." }, { "start": 1042.42, "end": 1043.88, "text": "MTS - AV: Thank you, Fernanda." }, { "start": 1044.26, "end": 1054.98, "text": "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." }, { "start": 1055.42, "end": 1059.239, "text": "MTS - AV: So, I was also wondering why they need to…" }, { "start": 1059.47, "end": 1066.17, "text": "MTS - AV: be consulted again separately with the board before it's been voted for. And what if." }, { "start": 1066.87, "end": 1069.8, "text": "MTS - AV: There is a disagreement at that level. What happens?" }, { "start": 1073.1, "end": 1083.74, "text": "MTS - AV: I think then, in case, there's a disagreement between the board and GAC, Then." }, { "start": 1084.21, "end": 1090.969, "text": "MTS - AV: Set of meetings between the two groups start to iron out the differences and." }, { "start": 1091.18, "end": 1093.83, "text": "MTS - AV: See if they can come to a mutual agreement." }, { "start": 1093.97, "end": 1103.92, "text": "MTS - AV: And, I believe these are rare cases, because, as I already mentioned." }, { "start": 1104.04, "end": 1123.38, "text": "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." }, { "start": 1123.51, "end": 1129.409, "text": "MTS - AV: With the groups talking to each other at the early stages." }, { "start": 1130.0, "end": 1139.16, "text": "MTS - AV: So, but again, if there's still disagreement in the end, there's a special," }, { "start": 1140.02, "end": 1148.29, "text": "MTS - AV: There would be meetings between the groups to, again, see if there's a mutual ground to come to." }, { "start": 1149.37, "end": 1168.159, "text": "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." }, { "start": 1168.16, "end": 1172.52, "text": "MTS - AV: It goes the other way around, where they also have a final decision to make." }, { "start": 1172.55, "end": 1175.03, "text": "MTS - AV: You know, at the end of the day, it goes in their favor." }, { "start": 1175.38, "end": 1180.07, "text": "MTS - AV: Because they will now make decision with the board, yeah, so that's why I was just present that. Thank you." }, { "start": 1181.24, "end": 1188.87, "text": "MTS - AV: NCUC and CSG, they are part of non-commercial stakeholder group, and we will learn about them tomorrow." }, { "start": 1189.03, "end": 1193.599, "text": "MTS - AV: But just to know that those acronyms will coming up." }, { "start": 1200.42, "end": 1221.999, "text": "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…" }, { "start": 1222.0, "end": 1238.649, "text": "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?" }, { "start": 1239.72, "end": 1241.859, "text": "MTS - AV: Thank you for the question. So…" }, { "start": 1242.25, "end": 1257.74, "text": "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." }, { "start": 1257.99, "end": 1269.4, "text": "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." }, { "start": 1269.7, "end": 1276.63, "text": "MTS - AV: But if the working group decides not to follow the, comments received." }, { "start": 1276.76, "end": 1282.3, "text": "MTS - AV: They would probably do that and maybe explain why they didn't follow it." }, { "start": 1282.57, "end": 1285.83, "text": "MTS - AV: They don't have to, but that's usually the case." }, { "start": 1286.1, "end": 1292.489, "text": "MTS - AV: And you may expect some, different comments." }, { "start": 1292.62, "end": 1304.22, "text": "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." }, { "start": 1304.41, "end": 1319.83, "text": "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." }, { "start": 1319.99, "end": 1331.31, "text": "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." }, { "start": 1333.07, "end": 1338.97, "text": "MTS - AV: Jen, I saw you. You have your hand raised in the zoom. Please go ahead. If you have a question." }, { "start": 1338.97, "end": 1355.58, "text": "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?" }, { "start": 1356.33, "end": 1361.399, "text": "MTS - AV: in the board? Is it because they don't have voting power that they are extra consulted?" }, { "start": 1362.48, "end": 1364.45, "text": "MTS - AV: Before the voting happens." }, { "start": 1364.99, "end": 1376.419, "text": "MTS - AV: Exactly, these are, you know, not waiting until the final vote, and they'd like to have a discussion." }, { "start": 1376.49, "end": 1386.13, "text": "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" }, { "start": 1387.5, "end": 1388.38, "text": "MTS - AV: That's true." }, { "start": 1391.71, "end": 1395.279, "text": "MTS - AV: I see a couple of questions here. Yes, please go ahead." }, { "start": 1396.34, "end": 1406.16, "text": "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." }, { "start": 1406.16, "end": 1420.44, "text": "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?" }, { "start": 1420.44, "end": 1422.07, "text": "MTS - AV: Delays. Thank you." }, { "start": 1423.69, "end": 1432.01, "text": "MTS - AV: Thank you. Yes, the post-development process may take long in Many cases, couple of years." }, { "start": 1432.3, "end": 1444.86, "text": "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…" }, { "start": 1445.0, "end": 1453.5, "text": "MTS - AV: come to come to an agreement with colleagues representing other interests." }, { "start": 1453.72, "end": 1456.93, "text": "MTS - AV: But in time," }, { "start": 1457.94, "end": 1466.729, "text": "MTS - AV: I think the ICANN community and the organization and the board heard so many feedback about, post-development process taking too long." }, { "start": 1466.84, "end": 1476.31, "text": "MTS - AV: And, what happens today, when the GNSO Council, initiates a PDP is that there's a more." }, { "start": 1476.71, "end": 1490.0, "text": "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." }, { "start": 1490.18, "end": 1500.06, "text": "MTS - AV: And, of course, there can be updates to the timelines based on how the discussions are going, but." }, { "start": 1500.52, "end": 1502.83, "text": "MTS - AV: The effort is to ensure." }, { "start": 1502.95, "end": 1517.08, "text": "MTS - AV: The PDP, you know, concludes, based on this, projections, and then, and then…" }, { "start": 1517.14, "end": 1528.8, "text": "MTS - AV: Because of the regular reporting, the GNSO Council, keeps, informed about the progress, and if any And." }, { "start": 1529.47, "end": 1544.519, "text": "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." }, { "start": 1544.65, "end": 1554.659, "text": "MTS - AV: Apply a more structured approach, to, you know, to make the process more efficient." }, { "start": 1557.18, "end": 1558.54, "text": "MTS - AV: Okay, thank you." }, { "start": 1559.49, "end": 1568.46, "text": "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." }, { "start": 1568.49, "end": 1579.71, "text": "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?" }, { "start": 1579.78, "end": 1593.61, "text": "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?" }, { "start": 1598.15, "end": 1607.959, "text": "MTS - AV: Thank you for the question. Now, talking about different, national, jurisdiction or legislation." }, { "start": 1609.1, "end": 1624.849, "text": "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." }, { "start": 1624.85, "end": 1639.93, "text": "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…" }, { "start": 1639.94, "end": 1643.9, "text": "MTS - AV: You typically don't see a contract." }, { "start": 1644.1, "end": 1647.57, "text": "MTS - AV: Getting changed afterwards, after it's signed." }, { "start": 1647.74, "end": 1661.289, "text": "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." }, { "start": 1661.5, "end": 1676.23, "text": "MTS - AV: And, you know, that's regardless of the national, national, rules or… legislation, so… And." }, { "start": 1677.78, "end": 1680.489, "text": "MTS - AV: I don't know if that answers the question." }, { "start": 1682.61, "end": 1691.749, "text": "MTS - AV: But, that's what it relates to the GNSO policy development process here. There can be." }, { "start": 1692.86, "end": 1706.24, "text": "MTS - AV: Examples, of, you know, how, The differences in national policies may affect how these contracted parties would function." }, { "start": 1706.42, "end": 1724.94, "text": "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." }, { "start": 1727.62, "end": 1731.91, "text": "MTS - AV: Thank you. We have a question. Amruta? Yes, please go ahead." }, { "start": 1732.42, "end": 1748.209, "text": "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?" }, { "start": 1748.44, "end": 1753.61, "text": "MTS - AV: So I was just curious, like, have you ever experienced this? Like, yeah." }, { "start": 1754.7, "end": 1763.58, "text": "MTS - AV: Thank you for the question. Now, the policies that we're talking about, specific to the GNSL post-development process, would…" }, { "start": 1763.85, "end": 1769.82, "text": "MTS - AV: affect the contracted parties, again, the registrars and registries." }, { "start": 1769.97, "end": 1781.32, "text": "MTS - AV: So, if a contracted party would violate that, if someone has a complaint about it, ICANN has a contractual compliance function." }, { "start": 1781.49, "end": 1794.94, "text": "MTS - AV: And, somebody can report this complaint about this violation to, this function, and then the, contractual compliance, team would review it." }, { "start": 1795.1, "end": 1802.91, "text": "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." }, { "start": 1804.92, "end": 1817.86, "text": "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." }, { "start": 1819.03, "end": 1824.69, "text": "MTS - AV: You were… you wanted to ask a question, right? Yes, go ahead. Hello?" }, { "start": 1824.81, "end": 1837.66, "text": "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." }, { "start": 1837.66, "end": 1845.079, "text": "MTS - AV: In your experience, is it better to move slowly with a board agreement or other some kind of disagreement like that?" }, { "start": 1850.1, "end": 1854.889, "text": "MTS - AV: Thanks. It may be taking a long time, but in the end." }, { "start": 1856.0, "end": 1858.79, "text": "MTS - AV: If you think about why it's taken a long time." }, { "start": 1859.04, "end": 1863.32, "text": "MTS - AV: This is to, make sure that everyone" }, { "start": 1863.77, "end": 1869.98, "text": "MTS - AV: Everyone's concerns and issues are heard, if possible, addressed." }, { "start": 1870.26, "end": 1879.21, "text": "MTS - AV: And, it's, it's basically taken a long time, because they want the end result to be." }, { "start": 1879.41, "end": 1890.44, "text": "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." }, { "start": 1890.49, "end": 1901.52, "text": "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." }, { "start": 1902.68, "end": 1911.57, "text": "MTS - AV: Which is usually not the case, you know, in a setting where, the, there are different views, and…" }, { "start": 1912.2, "end": 1918.06, "text": "MTS - AV: And you need to find a mutual ground. You can…" }, { "start": 1918.78, "end": 1935.07, "text": "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." }, { "start": 1936.67, "end": 1938.409, "text": "MTS - AV: Godswing, please go ahead." }, { "start": 1940.55, "end": 1955.419, "text": "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." }, { "start": 1955.61, "end": 1973.669, "text": "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" }, { "start": 1973.8, "end": 1991.22, "text": "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?" }, { "start": 1991.22, "end": 1994.48, "text": "MTS - AV: Those who put in the comments, are they able to know that, okay." }, { "start": 1994.48, "end": 2003.99, "text": "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?" }, { "start": 2005.85, "end": 2014.44, "text": "MTS - AV: Thank you. There's no requirement to, for the post-development process working group to" }, { "start": 2015.2, "end": 2020.93, "text": "MTS - AV: Explain why they didn't accept a particular comment or not." }, { "start": 2021.12, "end": 2028.37, "text": "MTS - AV: But some of them do. Some of them take all the comments and have a discussion." }, { "start": 2028.39, "end": 2045.62, "text": "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." }, { "start": 2045.82, "end": 2047.13, "text": "MTS - AV: comment or not." }, { "start": 2047.49, "end": 2048.65, "text": "MTS - AV: But no requirement." }, { "start": 2050.32, "end": 2053.419, "text": "MTS - AV: Please come closer to the mic and ask your question." }, { "start": 2055.28, "end": 2055.969, "text": "MTS - AV: Okay." }, { "start": 2056.25, "end": 2063.309, "text": "MTS - AV: Hello, I'm Islam Khalid from the Fellowship program. My question is." }, { "start": 2063.6, "end": 2072.269, "text": "MTS - AV: Since the policy development maybe take, like, 2 years or more for whatever the core issue." }, { "start": 2072.33, "end": 2091.969, "text": "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?" }, { "start": 2092.96, "end": 2093.73, "text": "MTS - AV: Does it?" }, { "start": 2096.05, "end": 2106.74, "text": "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?" }, { "start": 2106.94, "end": 2109.11, "text": "MTS - AV: Then, what would we do, or…" }, { "start": 2110.16, "end": 2121.14, "text": "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?" }, { "start": 2122.97, "end": 2138.86, "text": "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…" }, { "start": 2139.21, "end": 2150.459, "text": "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…" }, { "start": 2150.84, "end": 2155.459, "text": "MTS - AV: Pay attention to is, you know, the…" }, { "start": 2156.79, "end": 2163.859, "text": "MTS - AV: GNSO Council and the working group has a specific scope." }, { "start": 2163.87, "end": 2177.1, "text": "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." }, { "start": 2177.1, "end": 2188.32, "text": "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." }, { "start": 2191.59, "end": 2198.01, "text": "MTS - AV: We have a question from Roshate and one more over there from Camila and then we'll continue." }, { "start": 2198.7, "end": 2206.119, "text": "MTS - AV: Hi, my name is Roshate. My question is related to the policy process within ICANN." }, { "start": 2206.35, "end": 2216.79, "text": "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" }, { "start": 2216.79, "end": 2241.76, "text": "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?" }, { "start": 2241.76, "end": 2244.47, "text": "MTS - AV: Back to the original policy process." }, { "start": 2245.12, "end": 2258.029, "text": "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." }, { "start": 2258.03, "end": 2265.82, "text": "MTS - AV: So, yes, there may be times, when, it is obvious for everyone that." }, { "start": 2265.82, "end": 2272.949, "text": "MTS - AV: The previously adopted recommendations could be unadopted." }, { "start": 2273.17, "end": 2286.179, "text": "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." }, { "start": 2286.97, "end": 2291.879, "text": "MTS - AV: A more common theme nowadays wants to…" }, { "start": 2291.96, "end": 2306.729, "text": "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." }, { "start": 2306.73, "end": 2312.189, "text": "MTS - AV: How the feasibility would go in terms of implementation, so…" }, { "start": 2312.19, "end": 2325.11, "text": "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." }, { "start": 2327.39, "end": 2330.04, "text": "MTS - AV: Camila Yep, no?" }, { "start": 2332.26, "end": 2340.28, "text": "MTS - AV: Hello, I'm Zainab. Zainab. And I'm an ICANN Fellow from Pakistan. So, I wanted to ask that." }, { "start": 2340.63, "end": 2359.209, "text": "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…" }, { "start": 2359.29, "end": 2367.31, "text": "MTS - AV: Policy development body makes sure that with the new technical expansions, how does it make sure that." }, { "start": 2367.41, "end": 2371.859, "text": "MTS - AV: The technical advancements, they do not outpace" }, { "start": 2372.13, "end": 2382.68, "text": "MTS - AV: The policy development process, like, how does this policy development body keep up with technical advancements and expansion of the domain namespace?" }, { "start": 2385.68, "end": 2389.01, "text": "MTS - AV: Thank you, Zeynep, for the question. I believe this is." }, { "start": 2390.94, "end": 2399.27, "text": "MTS - AV: Based on the projections that the, the working group members would make during the, policy development process phase." }, { "start": 2399.6, "end": 2403.089, "text": "MTS - AV: So, they," }, { "start": 2403.26, "end": 2419.179, "text": "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…" }, { "start": 2419.3, "end": 2428.929, "text": "MTS - AV: some, questions get answered, that would inform the post-development process. So, they would have this discussion within the working group." }, { "start": 2429.04, "end": 2436.509, "text": "MTS - AV: And determine whether that's… that is sufficient for them to come to a conclusion and conclude the post-development process." }, { "start": 2437.81, "end": 2438.67, "text": "MTS - AV: Thank you." }, { "start": 2439.02, "end": 2439.72, "text": "MTS - AV: Thank you." }, { "start": 2440.56, "end": 2443.31, "text": "MTS - AV: Do we want to continue or take more questions?" }, { "start": 2443.7, "end": 2448.179, "text": "MTS - AV: Are you okay? We have one more question. You're good?" }, { "start": 2449.2, "end": 2451.13, "text": "MTS - AV: Okay, let's go ahead." }, { "start": 2451.26, "end": 2454.439, "text": "MTS - AV: Gentlemen, please come closer to the mic." }, { "start": 2459.74, "end": 2471.989, "text": "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." }, { "start": 2472.11, "end": 2489.34, "text": "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." }, { "start": 2490.04, "end": 2498.23, "text": "MTS - AV: And now we are in a situation where we can join the RYSG as a… Oh!" }, { "start": 2498.65, "end": 2500.32, "text": "MTS - AV: As an observing member." }, { "start": 2500.58, "end": 2507.03, "text": "MTS - AV: But many of the decisions have already been made by parties that do not have our interests at heart." }, { "start": 2507.22, "end": 2517.37, "text": "MTS - AV: How… or presumably this has been thought of, but how is this generally considered in the ICANN policy development process?" }, { "start": 2526.8, "end": 2530.03, "text": "MTS - AV: So, I'm trying to understand…" }, { "start": 2530.6, "end": 2538.08, "text": "MTS - AV: how that relates to post-development process. Could you please tell me again about your case, and…" }, { "start": 2538.58, "end": 2544.57, "text": "MTS - AV: Where you are having trouble in the post-development process? So, to be more specific." }, { "start": 2544.73, "end": 2550.05, "text": "MTS - AV: Many of the policies around prioritization." }, { "start": 2550.63, "end": 2555.349, "text": "MTS - AV: Prioritization is the big one that I've been considering recently." }, { "start": 2555.68, "end": 2564.599, "text": "MTS - AV: were considered, prior to, many of the applicants… or supported applicants, from the Applicant Support Program." }, { "start": 2566.93, "end": 2576.8, "text": "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." }, { "start": 2577.51, "end": 2588.09, "text": "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." }, { "start": 2588.39, "end": 2593.959, "text": "MTS - AV: Oh, there was no opportunity for a… there was no reason that you would have consulted us." }, { "start": 2594.89, "end": 2597.18, "text": "MTS - AV: How would… Okay." }, { "start": 2598.2, "end": 2603.979, "text": "MTS - AV: How is the process designed to take considerate or take this sort of situation to account?" }, { "start": 2604.13, "end": 2609.289, "text": "MTS - AV: Where the set of stakeholders changes as a policy is being developed." }, { "start": 2610.25, "end": 2612.41, "text": "MTS - AV: Because that's really the core of my question." }, { "start": 2613.59, "end": 2618.269, "text": "MTS - AV: I see, thank you. So, in terms of the order of things, what happens is." }, { "start": 2618.54, "end": 2627.23, "text": "MTS - AV: You, set up a working group to work on a specific policy development process." }, { "start": 2627.34, "end": 2642.689, "text": "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." }, { "start": 2642.85, "end": 2649.149, "text": "MTS - AV: And then, they… they've done their job, and then." }, { "start": 2649.5, "end": 2656.019, "text": "MTS - AV: you know, now we have the 2026 rounds of that. So." }, { "start": 2658.21, "end": 2662.199, "text": "MTS - AV: I don't know if that… at that point, they… there's a…" }, { "start": 2662.3, "end": 2676.209, "text": "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." }, { "start": 2676.34, "end": 2679.93, "text": "MTS - AV: So, if there are…" }, { "start": 2680.09, "end": 2695.609, "text": "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" }, { "start": 2695.69, "end": 2702.729, "text": "MTS - AV: complete step one, and then a new PDP may be set up to address the issue that's being raised." }, { "start": 2707.34, "end": 2711.32, "text": "MTS - AV: Okay, I… yes, I see. Fia, please go ahead." }, { "start": 2713.02, "end": 2724.889, "text": "MTS - AV: Talofalava, everyone. I'm Tupe Tulomalafaele, an academic from the National University of Samoa. Just a quick question with regards to." }, { "start": 2725.54, "end": 2733.639, "text": "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?" }, { "start": 2735.73, "end": 2738.17, "text": "MTS - AV: Thank you for the question. I am" }, { "start": 2739.69, "end": 2751.449, "text": "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…" }, { "start": 2751.63, "end": 2754.02, "text": "MTS - AV: For the recommendations to be adopted." }, { "start": 2756.01, "end": 2760.79, "text": "MTS - AV: So in this sense, I don't know what happens if there's a tie." }, { "start": 2760.91, "end": 2763.35, "text": "MTS - AV: But…" }, { "start": 2764.22, "end": 2779.22, "text": "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." }, { "start": 2779.3, "end": 2792.18, "text": "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." }, { "start": 2793.68, "end": 2799.799, "text": "MTS - AV: But we can get back to you about it with… after consulting the board colleagues." }, { "start": 2800.66, "end": 2802.11, "text": "MTS - AV: Thank you. Okay." }, { "start": 2802.59, "end": 2803.42, "text": "MTS - AV: Cliff?" }, { "start": 2803.69, "end": 2805.09, "text": "MTS - AV: Go ahead, please." }, { "start": 2806.56, "end": 2811.03, "text": "MTS - AV: Thank you. My name is Cliff, Fellow from Uganda." }, { "start": 2811.36, "end": 2818.079, "text": "MTS - AV: From my understanding, a policy is usually framed around a problem." }, { "start": 2818.57, "end": 2827.43, "text": "MTS - AV: My question is, what if, along the way, the definition of the problem changes? Is there a provision for adjustment?" }, { "start": 2828.67, "end": 2831.73, "text": "MTS - AV: Excuse me, can you repeat what if what changes?" }, { "start": 2832.1, "end": 2837.84, "text": "MTS - AV: In case the definition of the problem changes, especially now that we live." }, { "start": 2838.18, "end": 2848.219, "text": "MTS - AV: in a world where there's Technology advancement that causes different factors to change around the problem." }, { "start": 2848.43, "end": 2855.94, "text": "MTS - AV: Is there a provision for changing how you define the problem? Is there… For example." }, { "start": 2856.58, "end": 2862.29, "text": "MTS - AV: Things like, a midterm review of the definition of the problem." }, { "start": 2869.96, "end": 2881.449, "text": "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." }, { "start": 2882.99, "end": 2896.26, "text": "MTS - AV: So, again, it starts with a specific issue, and then the GNSO Council deciding whether it would result in a consensus policy." }, { "start": 2897.08, "end": 2903.54, "text": "MTS - AV: If the nature of the issue changes in time when the PDP working group is working on it." }, { "start": 2903.68, "end": 2918.37, "text": "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." }, { "start": 2918.66, "end": 2923.119, "text": "MTS - AV: And if they determine so, I think they would continue." }, { "start": 2923.23, "end": 2931.75, "text": "MTS - AV: But if the answer is no, then again, that would take us to step one, and under these new, you know, circumstances." }, { "start": 2931.75, "end": 2949.759, "text": "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." }, { "start": 2951.27, "end": 2952.11, "text": "MTS - AV: Thank you." }, { "start": 2955.0, "end": 2960.7, "text": "MTS - AV: Don't see any hand raised here, and nobody in the Zoom, so we can continue." }, { "start": 2962.77, "end": 2972.659, "text": "MTS - AV: Thanks, everyone, for the questions, and on the slide deck, next, we will talk about the advice development at ICANN" }, { "start": 2972.82, "end": 2985.989, "text": "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." }, { "start": 2986.95, "end": 2993.839, "text": "MTS - AV: Within… At-Large Advisory Committee, we have 15 members." }, { "start": 2994.0, "end": 3005.169, "text": "MTS - AV: As you may know, there are five Regional At-Large organizations within different geographic regions." }, { "start": 3005.17, "end": 3020.82, "text": "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." }, { "start": 3021.12, "end": 3023.4, "text": "MTS - AV: So, we have 15 members." }, { "start": 3024.71, "end": 3031.869, "text": "MTS - AV: The Governmental Advisory Committee provides advice on public policy issues." }, { "start": 3032.05, "end": 3043.009, "text": "MTS - AV: And, it has, it has members, some of the organizations are, also members of the…" }, { "start": 3043.05, "end": 3062.55, "text": "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." }, { "start": 3062.62, "end": 3079.85, "text": "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." }, { "start": 3079.98, "end": 3088.53, "text": "MTS - AV: open to, ICANN community at ICANN87, so you can… you can also follow their meetings." }, { "start": 3088.63, "end": 3103.33, "text": "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." }, { "start": 3103.62, "end": 3109.22, "text": "MTS - AV: For instance, these two advisory committees, RSSAC and SSAC, will be offering" }, { "start": 3109.33, "end": 3119.809, "text": "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." }, { "start": 3120.3, "end": 3132.87, "text": "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." }, { "start": 3132.92, "end": 3141.96, "text": "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." }, { "start": 3142.02, "end": 3149.0, "text": "MTS - AV: So, there's now a link in the chat for this infographic." }, { "start": 3150.5, "end": 3165.7, "text": "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." }, { "start": 3166.04, "end": 3170.689, "text": "MTS - AV: And, provides advice, to the ICANN board." }, { "start": 3172.64, "end": 3183.289, "text": "MTS - AV: So, in this advice development process. Any At-Large Committee member can bring up an issue to the consideration of the ALAC." }, { "start": 3183.47, "end": 3188.359, "text": "MTS - AV: or at-large advisory committee, And again, you see." }, { "start": 3189.35, "end": 3195.31, "text": "MTS - AV: similar step here, identification of the issue. It all starts with the identification of the issue, right?" }, { "start": 3195.54, "end": 3205.33, "text": "MTS - AV: And then the second step is, again, scoping phase. The At-Large Advisory Committee would have a discussion." }, { "start": 3205.51, "end": 3218.109, "text": "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." }, { "start": 3219.32, "end": 3230.67, "text": "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." }, { "start": 3230.87, "end": 3236.73, "text": "MTS - AV: And then what happens is that the ALAC would designate an issue shepherd." }, { "start": 3236.91, "end": 3243.149, "text": "MTS - AV: Within At-Large, there's a… there's a consolidated policy working group." }, { "start": 3243.34, "end": 3263.17, "text": "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." }, { "start": 3263.43, "end": 3274.6, "text": "MTS - AV: And then, the small team would report on, potential end-user impacts. To the Consolidated Post Working Group." }, { "start": 3274.82, "end": 3282.9, "text": "MTS - AV: And then, if the Consolidated Policy Working Group, or CPWG, would like to continue drafting a statement." }, { "start": 3283.06, "end": 3284.84, "text": "MTS - AV: Then," }, { "start": 3285.63, "end": 3295.929, "text": "MTS - AV: Then, the small team would work on, drafting this statement, would present it to, Consolidate Post Working Group." }, { "start": 3296.2, "end": 3305.94, "text": "MTS - AV: And then, based on the feedback received from CPWG, the small group would also" }, { "start": 3306.13, "end": 3310.07, "text": "MTS - AV: Draft a final statement." }, { "start": 3310.53, "end": 3328.29, "text": "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." }, { "start": 3328.34, "end": 3330.619, "text": "MTS - AV: for ReViva and Ratification." }, { "start": 3330.77, "end": 3345.39, "text": "MTS - AV: And at the end of the ratification process, if ratified, the ALAC would send the advice to the ICANN board, ICANN organization, or other advisory committees or supporting organizations." }, { "start": 3348.24, "end": 3353.519, "text": "MTS - AV: So that's how the advice development would work for the At-Large Advisory Committee." }, { "start": 3354.81, "end": 3360.069, "text": "MTS - AV: And, on the next one, I'd like to talk about" }, { "start": 3360.27, "end": 3373.149, "text": "MTS - AV: How you can participate in this policy and advice development, because, especially for newcomers, it can be, hard to, you know." }, { "start": 3374.64, "end": 3387.86, "text": "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." }, { "start": 3387.97, "end": 3401.88, "text": "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" }, { "start": 3402.06, "end": 3407.169, "text": "MTS - AV: Working group or a community, and." }, { "start": 3408.54, "end": 3423.23, "text": "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." }, { "start": 3423.52, "end": 3432.979, "text": "MTS - AV: And this way, you would be informed about the hot topics, common discussion items." }, { "start": 3433.14, "end": 3445.96, "text": "MTS - AV: And then, this would… this would help you, make your own contribution to the, Policy and advice development process." }, { "start": 3446.1, "end": 3454.489, "text": "MTS - AV: Also, feel free to join mailing list to see the discussions and observe it." }, { "start": 3454.71, "end": 3473.789, "text": "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." }, { "start": 3473.9, "end": 3477.539, "text": "MTS - AV: And that's what also you can also consider doing." }, { "start": 3477.83, "end": 3497.169, "text": "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." }, { "start": 3497.57, "end": 3503.47, "text": "MTS - AV: see organizations, and we talked about supporting organizations, advisory committees." }, { "start": 3503.84, "end": 3512.47, "text": "MTS - AV: Submitting their comment as a group, And if… if they can, And." }, { "start": 3513.48, "end": 3523.609, "text": "MTS - AV: finalize a statement, finalize the group comment, and ratify it. Then they can submit this comment as a group input." }, { "start": 3523.8, "end": 3537.539, "text": "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." }, { "start": 3537.95, "end": 3540.86, "text": "MTS - AV: And participate in the public comment process." }, { "start": 3543.89, "end": 3549.04, "text": "MTS - AV: We… Oh, we did have a question. Let's go ahead. Let's go." }, { "start": 3550.53, "end": 3557.56, "text": "MTS - AV: Hello, my name is Sanjina Chhetri. I'm from Nepal. I'm a Nixon participant, here." }, { "start": 3557.56, "end": 3579.14, "text": "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." }, { "start": 3579.14, "end": 3586.269, "text": "MTS - AV: So I just wanted to know the process. Is there a pathway? Is it open to all or I don't know?" }, { "start": 3586.29, "end": 3588.73, "text": "MTS - AV: Just a bit about a pathway." }, { "start": 3589.53, "end": 3591.26, "text": "MTS - AV: Thank you." }, { "start": 3591.55, "end": 3609.389, "text": "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." }, { "start": 3609.39, "end": 3617.04, "text": "MTS - AV: an At-Large structure, see how they work, and see if you can get engaged with them." }, { "start": 3617.07, "end": 3620.75, "text": "MTS - AV: And then, and." }, { "start": 3621.49, "end": 3626.829, "text": "MTS - AV: with these At-Large structures, you have the regional At-Large organizations within your regions, right?" }, { "start": 3626.94, "end": 3634.949, "text": "MTS - AV: It may be the case that there's no At-Large structure within your region. You may consider, setting up one." }, { "start": 3635.07, "end": 3649.83, "text": "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." }, { "start": 3649.9, "end": 3662.779, "text": "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." }, { "start": 3663.6, "end": 3674.809, "text": "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." }, { "start": 3675.2, "end": 3689.14, "text": "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." }, { "start": 3689.36, "end": 3706.8, "text": "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." }, { "start": 3708.01, "end": 3720.2, "text": "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." }, { "start": 3720.58, "end": 3734.0, "text": "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." }, { "start": 3734.0, "end": 3743.61, "text": "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." }, { "start": 3743.61, "end": 3753.83, "text": "MTS - AV: and talking to us, and specifically talking and explaining about their particular community. So, this is the overview." }, { "start": 3753.83, "end": 3764.52, "text": "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" }, { "start": 3764.59, "end": 3775.329, "text": "MTS - AV: major overview of each community, and then you will have the opportunity to ask the question directly to At-Large, to GNSO." }, { "start": 3775.63, "end": 3779.979, "text": "MTS - AV: to non-commercial stakeholder groups, etc." }, { "start": 3782.43, "end": 3795.949, "text": "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?" }, { "start": 3796.07, "end": 3813.76, "text": "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?" }, { "start": 3813.88, "end": 3819.89, "text": "MTS - AV: No, on the slide, you saw the, This…" }, { "start": 3820.92, "end": 3827.36, "text": "MTS - AV: Yeah, this one? No, I think it was referring to the post-development slide, I guess." }, { "start": 3827.65, "end": 3837.25, "text": "MTS - AV: Let's see… here in the final step, yes, the board consults community and the GAC. So…" }, { "start": 3837.39, "end": 3842.129, "text": "MTS - AV: The GAC is called out here because it's, called out in the bylaws." }, { "start": 3842.35, "end": 3854.019, "text": "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." }, { "start": 3854.07, "end": 3863.68, "text": "MTS - AV: And, all the ICANN community groups and individuals may submit their comments to this public comment proceeding, including the GAC." }, { "start": 3863.79, "end": 3868.19, "text": "MTS - AV: But that doesn't mean others are left out. The…" }, { "start": 3869.24, "end": 3875.349, "text": "MTS - AV: The reason that Yak is all called out on the slide is that it's called out in the bylaws." }, { "start": 3878.7, "end": 3886.34, "text": "MTS - AV: And by the way, during the week, the ICANN board will be meeting with, separately, with those" }, { "start": 3886.39, "end": 3895.62, "text": "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" }, { "start": 3895.62, "end": 3908.61, "text": "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…" }, { "start": 3908.61, "end": 3922.029, "text": "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?" }, { "start": 3924.63, "end": 3944.46, "text": "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." }, { "start": 3944.54, "end": 3952.75, "text": "MTS - AV: you know, in addition to the GAC, other advisory committees are also invited, so if they wish to participate, they can" }, { "start": 3952.75, "end": 3968.9, "text": "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." }, { "start": 3968.9, "end": 3985.819, "text": "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," }, { "start": 3986.07, "end": 3992.66, "text": "MTS - AV: At-Large also has representatives within the PDP working group, just like GAC." }, { "start": 3992.73, "end": 4007.19, "text": "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" }, { "start": 4007.27, "end": 4020.23, "text": "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." }, { "start": 4024.83, "end": 4039.52, "text": "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" }, { "start": 4039.52, "end": 4053.129, "text": "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." }, { "start": 4053.16, "end": 4061.889, "text": "MTS - AV: The ones that are pending their, reports, and the ones that have been, closed." }, { "start": 4062.27, "end": 4080.339, "text": "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." }, { "start": 4082.68, "end": 4085.49, "text": "MTS - AV: On the next slide, so this is…" }, { "start": 4085.86, "end": 4100.849, "text": "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." }, { "start": 4100.91, "end": 4108.6, "text": "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." }, { "start": 4108.72, "end": 4120.849, "text": "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…" }, { "start": 4120.91, "end": 4131.81, "text": "MTS - AV: you will be able to do that. And if you need to contact, the ICANN Org staff member, opening this" }, { "start": 4132.09, "end": 4142.75, "text": "MTS - AV: Public comment to ask for clarification, before you submit your comment, you can also see a contact information there. To do so." }, { "start": 4145.01, "end": 4148.77, "text": "MTS - AV: Do we have any other questions around public comment, or anything else?" }, { "start": 4151.229, "end": 4152.39, "text": "MTS - AV: Yes, sounds fine." }, { "start": 4156.689, "end": 4172.45, "text": "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." }, { "start": 4172.529, "end": 4181.58, "text": "MTS - AV: And I participate in some of the working groups, especially the Consolidated Policy Working Group." }, { "start": 4181.96, "end": 4191.82, "text": "MTS - AV: We are one of the committees or the community groups that oversees most of the policies within ICANN." }, { "start": 4192.0, "end": 4201.75, "text": "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" }, { "start": 4201.92, "end": 4214.099, "text": "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" }, { "start": 4214.55, "end": 4217.169, "text": "MTS - AV: organization and structure." }, { "start": 4217.9, "end": 4219.6, "text": "MTS - AV: to rule my country." }, { "start": 4219.72, "end": 4225.78, "text": "MTS - AV: I can also write individual as an individual, a public comment." }, { "start": 4226.04, "end": 4245.159, "text": "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…" }, { "start": 4245.53, "end": 4261.619, "text": "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." }, { "start": 4261.78, "end": 4272.0, "text": "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" }, { "start": 4272.11, "end": 4273.91, "text": "MTS - AV: is important." }, { "start": 4274.03, "end": 4283.449, "text": "MTS - AV: It contributes to the resolution or the proceeding that is being consulted, and that it's documented." }, { "start": 4283.65, "end": 4288.26, "text": "MTS - AV: Don't write something for the sake of writing it. It has to…" }, { "start": 4288.63, "end": 4293.809, "text": "MTS - AV: Contribute in some ways to, the policy process." }, { "start": 4294.18, "end": 4294.98, "text": "MTS - AV: Thank you." }, { "start": 4298.68, "end": 4300.809, "text": "MTS - AV: Do we have one more question?" }, { "start": 4301.88, "end": 4308.9, "text": "MTS - AV: Okay, I think we have a few minutes left. How many questions do you think we can take? Two?" }, { "start": 4309.65, "end": 4316.69, "text": "MTS - AV: We will take one question here and one there. Those who didn't ask questions during We'll come back." }, { "start": 4317.1, "end": 4317.98, "text": "MTS - AV: Okay." }, { "start": 4318.27, "end": 4326.22, "text": "MTS - AV: Hello, everyone. My name is Solange Olude. I'm from Bene. I'm a Folo." }, { "start": 4326.4, "end": 4332.749, "text": "MTS - AV: And thank you very much for this opportunity, and… Thank you for your presentation." }, { "start": 4333.34, "end": 4334.51, "text": "MTS - AV: I have." }, { "start": 4335.54, "end": 4338.27, "text": "MTS - AV: One question. My question is." }, { "start": 4338.6, "end": 4352.92, "text": "MTS - AV: For a fellows who want to remain actively involved in ICANN's policy development process After the meeting, Wal wool." }, { "start": 4353.07, "end": 4359.01, "text": "MTS - AV: Your recommendation… your recommendation as most first step." }, { "start": 4359.39, "end": 4364.81, "text": "MTS - AV: to take, especially for someone who still builds them experience." }, { "start": 4365.44, "end": 4379.52, "text": "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." }, { "start": 4380.87, "end": 4386.33, "text": "MTS - AV: Thank you. Thank you. So again, based on your interest, profession." }, { "start": 4386.51, "end": 4400.65, "text": "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." }, { "start": 4400.65, "end": 4407.209, "text": "MTS - AV: For the, non-commercial users, not-for-profit organizations." }, { "start": 4407.21, "end": 4413.92, "text": "MTS - AV: And then for commercial part, you have business constituency, intellectual property constituency." }, { "start": 4414.03, "end": 4421.439, "text": "MTS - AV: Internal service providers, and then the contracted parties. Let's say if you are." }, { "start": 4421.59, "end": 4433.14, "text": "MTS - AV: technical person who is interested in the DNS, and also working on DNS root server system, maybe." }, { "start": 4433.14, "end": 4445.599, "text": "MTS - AV: then in this case, you can apply to become a member of RSSAC Caucus, which is composed of DNS experts" }, { "start": 4445.6, "end": 4460.529, "text": "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." }, { "start": 4460.61, "end": 4473.23, "text": "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" }, { "start": 4473.33, "end": 4492.469, "text": "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…" }, { "start": 4492.52, "end": 4505.4, "text": "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." }, { "start": 4505.4, "end": 4516.65, "text": "MTS - AV: And then observing mailing lists are… is always a good step in the initial stages. So, And…" }, { "start": 4517.1, "end": 4536.579, "text": "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." }, { "start": 4536.58, "end": 4539.459, "text": "MTS - AV: When there is a report" }, { "start": 4539.46, "end": 4546.91, "text": "MTS - AV: Offer public comment. There's a detail, information, and you can go read it, and then." }, { "start": 4546.91, "end": 4548.31, "text": "Jovita Kanza, ICANN87 Fellow: Great meeting." }, { "start": 4548.6, "end": 4550.33, "text": "Jovita Kanza, ICANN87 Fellow: Reading room…" }, { "start": 4553.63, "end": 4570.879, "text": "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." }, { "start": 4571.6, "end": 4572.789, "text": "MTS - AV: Thank you." }, { "start": 4573.51, "end": 4575.83, "text": "MTS - AV: Very brief, 10 seconds." }, { "start": 4577.42, "end": 4578.84, "text": "MTS - AV: AL" }, { "start": 4578.84, "end": 4602.979, "text": "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." }, { "start": 4605.68, "end": 4609.27, "text": "MTS - AV: Thank you for the question. So…" }, { "start": 4612.24, "end": 4620.49, "text": "MTS - AV: Defining the consensus or, you know, determining a consensus, is often…" }, { "start": 4620.65, "end": 4634.13, "text": "MTS - AV: left to, working group leadership. And the working group leadership should be, working under certain, You know." }, { "start": 4638.8, "end": 4644.75, "text": "MTS - AV: talents, I would say, and, some." }, { "start": 4645.01, "end": 4661.429, "text": "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." }, { "start": 4661.43, "end": 4665.309, "text": "MTS - AV: Encouraging that kind of atmosphere within the working group." }, { "start": 4665.4, "end": 4674.8, "text": "MTS - AV: So, when it comes to, determining consensus, the working group leadership may say." }, { "start": 4675.43, "end": 4693.529, "text": "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." }, { "start": 4693.64, "end": 4697.65, "text": "MTS - AV: They could ask the question if, you know." }, { "start": 4700.61, "end": 4711.3, "text": "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." }, { "start": 4711.3, "end": 4735.279, "text": "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." }, { "start": 4735.37, "end": 4750.499, "text": "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." }, { "start": 4751.88, "end": 4758.549, "text": "MTS - AV: Thank you, Ozan, and thank you very much for this very interesting session. I hope…" }, { "start": 4758.68, "end": 4777.89, "text": "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." }, { "start": 4777.89, "end": 4786.779, "text": "MTS - AV: And, before we go to the next session, we are starting the series of Get to Know ICANN Community." }, { "start": 4786.78, "end": 4798.17, "text": "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." }, { "start": 4798.17, "end": 4803.34, "text": "MTS - AV: Please go enjoy and come back here in 25 minutes. Thank you." } ], "text": "MTS - AV: Thank you, everyone.\nMTS - AV: Thank you.\nMTS - 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?\nMTS - 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.\nMTS - 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.\nMTS - 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.\nMTS - 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.\nMTS - AV: On-site participants will use a physical microphone to speak.\nMTS - 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.\nMTS - 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.\nMTS - AV: Thank you. And Siranush, back to you.\nMTS - 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.\nMTS - 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.\nMTS - AV: And…\nMTS - 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.\nMTS - 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…\nMTS - AV: the entire process. And I will encourage all of you to use the opportunity to ask questions to Ozan.\nMTS - AV: And without further ado, Ozan, the floor is yours.\nMTS - AV: Thank you, Siranush. Hello, everyone. My name is Ozan Sahin, and it is great to be here with you this afternoon.\nMTS - AV: In this presentation, I will talk about ICANN policy and advice development, and I will start with an overview of the.\nMTS - AV: ICANN community, and also try to address your questions throughout the presentation.\nMTS - 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.\nMTS - AV: And, what ICANN Committee does is to, develop the, policy.\nMTS - AV: and make recommendations to ICANN board.\nMTS - AV: And then ICANN board is the part, which reviews these recommendations and, and adopts them.\nMTS - 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.\nMTS - AV: And also, you see a line between ICANN organization and ICANN community. The organization also supports the ICANN community in the development of\nMTS - AV: these policies and in the\nMTS - AV: slides to come, I will explain how the ICANN Post-Development Support Team supports these efforts.\nMTS - 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.\nMTS - AV: And, this is the, numbers community, which work on… Policies on global, number resources.\nMTS - 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\nMTS - AV: A total of 15 volunteers.\nMTS - 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.\nMTS - AV: We have the contract code name supporting organization, or the ccNSO, where you will see the.\nMTS - AV: Country Code Top Level Domain Managers.\nMTS - AV: who have agreed to be members of the CCNSO, and there is also a CCNSO Council.\nMTS - AV: the executive body in the ccNSO. And then, we have the generic name supporting organization.\nMTS - AV: Which has the, both the contracted parties, which ICANN has contracts with.\nMTS - 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.\nMTS - AV: So these three supporting organizations do\nMTS - 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.\nMTS - 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.\nMTS - 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.\nMTS - AV: So, let's go to the overview of GNSL policy development.\nMTS - AV: And, and start with, the GNSO Council.\nMTS - 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.\nMTS - AV: So,\nMTS - 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.\nMTS - AV: Which have contracts with ICANN. And also, on the left, you have commercial stakeholder group.\nMTS - AV: Which also splits into, three constituencies, the business constituency, intellectual property constituency.\nMTS - AV: and internet service providers and connectivity providers constituency. And on the right-hand side, you have a non-commercial stakeholder group.\nMTS - AV: Which has, two constituencies, the non-commercial users constituency and the not-for-profit.\nMTS - 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.\nMTS - AV: And, this is how the GNSO Council is designed to, to actually, allow for this representation.\nMTS - AV: So, on the slide, you see.\nMTS - AV: details of the GNSO policy development process. And it all starts with the identification of an issue.\nMTS - AV: And, it can be GNSO Council, the ICANN board, or an advisory committee who comes up with an issue.\nMTS - 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.\nMTS - AV: And if the GNSO Council determines that it is indeed within the GNSO scope.\nMTS - AV: Then, this would take us to the next step, which is the scoping, phase.\nMTS - 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.\nMTS - AV: And, you may notice, there are some arrows on the both left and right-hand side.\nMTS - 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.\nMTS - AV: And when we talk about the scoping phase, in the second step.\nMTS - AV: When staff publishes the preliminary issue report for public comment.\nMTS - AV: Again, the ICANN community may step in and provide their feedback into this process.\nMTS - 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.\nMTS - AV: And this takes us to step 3, the initiation of a policy development process, or PDP.\nMTS - AV: And the GNSO Council considers the final issue report.\nMTS - 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.\nMTS - AV: And then there's a call for volunteers, to form the, Post Development Process Working Group.\nMTS - 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\nMTS - AV: representatives from, other ICANN groups, ICANN advisory committees or supporting organizations who may, take their seat in the, in the working group.\nMTS - 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\nMTS - AV: And then eventually.\nMTS - AV: publishes this initial report for public comment, and this is also where you see an opportunity for feedback from the ICANN community.\nMTS - AV: The community would provide their feedback on the initial report.\nMTS - AV: And then, the working group Reviews all this feedback, and publishes their final report.\nMTS - 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.\nMTS - AV: is the DNS abuse mitigation, post-development process.\nMTS - 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.\nMTS - 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.\nMTS - 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.\nMTS - AV: In the next phase, once the final report is submitted to the GNSO Council.\nMTS - AV: The GNSO Council would review it, and considers whether to adopt it.\nMTS - AV: Of course, this…\nMTS - AV: GNSO Council doesn't see it as a surprise, right? As the post-development process working group progresses its work.\nMTS - 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.\nMTS - 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\nMTS - 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.\nMTS - AV: Before they take a vote on adopting the recommendations coming from this working group.\nMTS - AV: And after the, the, This consultation, the board takes a vote, and…\nMTS - AV: If adopted, the recommendations from the post-development process become effective.\nMTS - AV: So, these are the steps for the GNSO post-development process. I just wanted to pause and see any…\nMTS - AV: If you have any questions on this, or what have been presented so far.\nLouis Marius ANDRIAMPARANY: What should promote?\nMTS - AV: Alfredo? Alfredo, please.\nMTS - 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.\nMTS - AV: Oh.\nMTS - AV: policy to comment on it. Why does the GAC have to do that, and not just the board?\nMTS - AV: Thank you.\nMTS - AV: Thank you, Alfredo. Yes, there's a specific status of the GAC in this…\nMTS - 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.\nMTS - AV: That's… that's written in the bylaws.\nMTS - AV: Just a reminder that GAC is the Governmental Advisory Committee.\nMTS - AV: Thank you, Fernanda.\nMTS - 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.\nMTS - AV: So, I was also wondering why they need to…\nMTS - AV: be consulted again separately with the board before it's been voted for. And what if.\nMTS - AV: There is a disagreement at that level. What happens?\nMTS - AV: I think then, in case, there's a disagreement between the board and GAC, Then.\nMTS - AV: Set of meetings between the two groups start to iron out the differences and.\nMTS - AV: See if they can come to a mutual agreement.\nMTS - AV: And, I believe these are rare cases, because, as I already mentioned.\nMTS - 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.\nMTS - AV: With the groups talking to each other at the early stages.\nMTS - AV: So, but again, if there's still disagreement in the end, there's a special,\nMTS - AV: There would be meetings between the groups to, again, see if there's a mutual ground to come to.\nMTS - 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.\nMTS - AV: It goes the other way around, where they also have a final decision to make.\nMTS - AV: You know, at the end of the day, it goes in their favor.\nMTS - AV: Because they will now make decision with the board, yeah, so that's why I was just present that. Thank you.\nMTS - AV: NCUC and CSG, they are part of non-commercial stakeholder group, and we will learn about them tomorrow.\nMTS - AV: But just to know that those acronyms will coming up.\nMTS - 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…\nMTS - 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?\nMTS - AV: Thank you for the question. So…\nMTS - 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.\nMTS - 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.\nMTS - AV: But if the working group decides not to follow the, comments received.\nMTS - AV: They would probably do that and maybe explain why they didn't follow it.\nMTS - AV: They don't have to, but that's usually the case.\nMTS - AV: And you may expect some, different comments.\nMTS - 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.\nMTS - 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.\nMTS - 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.\nMTS - AV: Jen, I saw you. You have your hand raised in the zoom. Please go ahead. If you have a question.\nMTS - 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?\nMTS - AV: in the board? Is it because they don't have voting power that they are extra consulted?\nMTS - AV: Before the voting happens.\nMTS - AV: Exactly, these are, you know, not waiting until the final vote, and they'd like to have a discussion.\nMTS - 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\nMTS - AV: That's true.\nMTS - AV: I see a couple of questions here. Yes, please go ahead.\nMTS - AV: Okay, hello, everyone. My name is Jifanida Sabila. I'm from ICANN Fellows and from Rawijaya University, Indonesia. So, this is my question.\nMTS - 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?\nMTS - AV: Delays. Thank you.\nMTS - AV: Thank you. Yes, the post-development process may take long in Many cases, couple of years.\nMTS - 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…\nMTS - AV: come to come to an agreement with colleagues representing other interests.\nMTS - AV: But in time,\nMTS - AV: I think the ICANN community and the organization and the board heard so many feedback about, post-development process taking too long.\nMTS - AV: And, what happens today, when the GNSO Council, initiates a PDP is that there's a more.\nMTS - 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.\nMTS - AV: And, of course, there can be updates to the timelines based on how the discussions are going, but.\nMTS - AV: The effort is to ensure.\nMTS - AV: The PDP, you know, concludes, based on this, projections, and then, and then…\nMTS - AV: Because of the regular reporting, the GNSO Council, keeps, informed about the progress, and if any And.\nMTS - 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.\nMTS - AV: Apply a more structured approach, to, you know, to make the process more efficient.\nMTS - AV: Okay, thank you.\nMTS - 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.\nMTS - 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?\nMTS - 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?\nMTS - AV: Thank you for the question. Now, talking about different, national, jurisdiction or legislation.\nMTS - 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.\nMTS - 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…\nMTS - AV: You typically don't see a contract.\nMTS - AV: Getting changed afterwards, after it's signed.\nMTS - 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.\nMTS - AV: And, you know, that's regardless of the national, national, rules or… legislation, so… And.\nMTS - AV: I don't know if that answers the question.\nMTS - AV: But, that's what it relates to the GNSO policy development process here. There can be.\nMTS - AV: Examples, of, you know, how, The differences in national policies may affect how these contracted parties would function.\nMTS - 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.\nMTS - AV: Thank you. We have a question. Amruta? Yes, please go ahead.\nMTS - 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?\nMTS - AV: So I was just curious, like, have you ever experienced this? Like, yeah.\nMTS - AV: Thank you for the question. Now, the policies that we're talking about, specific to the GNSL post-development process, would…\nMTS - AV: affect the contracted parties, again, the registrars and registries.\nMTS - AV: So, if a contracted party would violate that, if someone has a complaint about it, ICANN has a contractual compliance function.\nMTS - AV: And, somebody can report this complaint about this violation to, this function, and then the, contractual compliance, team would review it.\nMTS - AV: See if it follows the contract, or if it's a violation, and then they may take the corrective action in this case.\nMTS - 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.\nMTS - AV: You were… you wanted to ask a question, right? Yes, go ahead. Hello?\nMTS - 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.\nMTS - AV: In your experience, is it better to move slowly with a board agreement or other some kind of disagreement like that?\nMTS - AV: Thanks. It may be taking a long time, but in the end.\nMTS - AV: If you think about why it's taken a long time.\nMTS - AV: This is to, make sure that everyone\nMTS - AV: Everyone's concerns and issues are heard, if possible, addressed.\nMTS - AV: And, it's, it's basically taken a long time, because they want the end result to be.\nMTS - 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.\nMTS - 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.\nMTS - AV: Which is usually not the case, you know, in a setting where, the, there are different views, and…\nMTS - AV: And you need to find a mutual ground. You can…\nMTS - 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.\nMTS - AV: Godswing, please go ahead.\nMTS - 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.\nMTS - 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\nMTS - 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?\nMTS - AV: Those who put in the comments, are they able to know that, okay.\nMTS - 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?\nMTS - AV: Thank you. There's no requirement to, for the post-development process working group to\nMTS - AV: Explain why they didn't accept a particular comment or not.\nMTS - AV: But some of them do. Some of them take all the comments and have a discussion.\nMTS - 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.\nMTS - AV: comment or not.\nMTS - AV: But no requirement.\nMTS - AV: Please come closer to the mic and ask your question.\nMTS - AV: Okay.\nMTS - AV: Hello, I'm Islam Khalid from the Fellowship program. My question is.\nMTS - AV: Since the policy development maybe take, like, 2 years or more for whatever the core issue.\nMTS - 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?\nMTS - AV: Does it?\nMTS - 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?\nMTS - AV: Then, what would we do, or…\nMTS - 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?\nMTS - 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…\nMTS - AV: review, the issue report that's available to them, and any additional input that may come throughout the discussion. So, one thing to…\nMTS - AV: Pay attention to is, you know, the…\nMTS - AV: GNSO Council and the working group has a specific scope.\nMTS - 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.\nMTS - 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.\nMTS - AV: We have a question from Roshate and one more over there from Camila and then we'll continue.\nMTS - AV: Hi, my name is Roshate. My question is related to the policy process within ICANN.\nMTS - 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\nMTS - 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?\nMTS - AV: Back to the original policy process.\nMTS - 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.\nMTS - AV: So, yes, there may be times, when, it is obvious for everyone that.\nMTS - AV: The previously adopted recommendations could be unadopted.\nMTS - AV: But the other side of your question is, you know, to, the implementability of the recommendations. To address that, we see a more.\nMTS - AV: A more common theme nowadays wants to…\nMTS - 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.\nMTS - AV: How the feasibility would go in terms of implementation, so…\nMTS - AV: To make sure that the adopted recommendations would be implemented in the intended way, and also do the assessment that you just mentioned.\nMTS - AV: Camila Yep, no?\nMTS - AV: Hello, I'm Zainab. Zainab. And I'm an ICANN Fellow from Pakistan. So, I wanted to ask that.\nMTS - 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…\nMTS - AV: Policy development body makes sure that with the new technical expansions, how does it make sure that.\nMTS - AV: The technical advancements, they do not outpace\nMTS - AV: The policy development process, like, how does this policy development body keep up with technical advancements and expansion of the domain namespace?\nMTS - AV: Thank you, Zeynep, for the question. I believe this is.\nMTS - AV: Based on the projections that the, the working group members would make during the, policy development process phase.\nMTS - AV: So, they,\nMTS - 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…\nMTS - AV: some, questions get answered, that would inform the post-development process. So, they would have this discussion within the working group.\nMTS - AV: And determine whether that's… that is sufficient for them to come to a conclusion and conclude the post-development process.\nMTS - AV: Thank you.\nMTS - AV: Thank you.\nMTS - AV: Do we want to continue or take more questions?\nMTS - AV: Are you okay? We have one more question. You're good?\nMTS - AV: Okay, let's go ahead.\nMTS - AV: Gentlemen, please come closer to the mic.\nMTS - 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.\nMTS - 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.\nMTS - AV: And now we are in a situation where we can join the RYSG as a… Oh!\nMTS - AV: As an observing member.\nMTS - AV: But many of the decisions have already been made by parties that do not have our interests at heart.\nMTS - AV: How… or presumably this has been thought of, but how is this generally considered in the ICANN policy development process?\nMTS - AV: So, I'm trying to understand…\nMTS - AV: how that relates to post-development process. Could you please tell me again about your case, and…\nMTS - AV: Where you are having trouble in the post-development process? So, to be more specific.\nMTS - AV: Many of the policies around prioritization.\nMTS - AV: Prioritization is the big one that I've been considering recently.\nMTS - AV: were considered, prior to, many of the applicants… or supported applicants, from the Applicant Support Program.\nMTS - 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.\nMTS - 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.\nMTS - AV: Oh, there was no opportunity for a… there was no reason that you would have consulted us.\nMTS - AV: How would… Okay.\nMTS - AV: How is the process designed to take considerate or take this sort of situation to account?\nMTS - AV: Where the set of stakeholders changes as a policy is being developed.\nMTS - AV: Because that's really the core of my question.\nMTS - AV: I see, thank you. So, in terms of the order of things, what happens is.\nMTS - AV: You, set up a working group to work on a specific policy development process.\nMTS - 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.\nMTS - AV: And then, they… they've done their job, and then.\nMTS - AV: you know, now we have the 2026 rounds of that. So.\nMTS - AV: I don't know if that… at that point, they… there's a…\nMTS - 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.\nMTS - AV: So, if there are…\nMTS - 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\nMTS - AV: complete step one, and then a new PDP may be set up to address the issue that's being raised.\nMTS - AV: Okay, I… yes, I see. Fia, please go ahead.\nMTS - AV: Talofalava, everyone. I'm Tupe Tulomalafaele, an academic from the National University of Samoa. Just a quick question with regards to.\nMTS - AV: the process number 6 vote by ICANN board. What's going to happen if there's a tie in the number of votes?\nMTS - AV: Thank you for the question. I am\nMTS - 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…\nMTS - AV: For the recommendations to be adopted.\nMTS - AV: So in this sense, I don't know what happens if there's a tie.\nMTS - AV: But…\nMTS - 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.\nMTS - 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.\nMTS - AV: But we can get back to you about it with… after consulting the board colleagues.\nMTS - AV: Thank you. Okay.\nMTS - AV: Cliff?\nMTS - AV: Go ahead, please.\nMTS - AV: Thank you. My name is Cliff, Fellow from Uganda.\nMTS - AV: From my understanding, a policy is usually framed around a problem.\nMTS - AV: My question is, what if, along the way, the definition of the problem changes? Is there a provision for adjustment?\nMTS - AV: Excuse me, can you repeat what if what changes?\nMTS - AV: In case the definition of the problem changes, especially now that we live.\nMTS - AV: in a world where there's Technology advancement that causes different factors to change around the problem.\nMTS - AV: Is there a provision for changing how you define the problem? Is there… For example.\nMTS - AV: Things like, a midterm review of the definition of the problem.\nMTS - 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.\nMTS - AV: So, again, it starts with a specific issue, and then the GNSO Council deciding whether it would result in a consensus policy.\nMTS - AV: If the nature of the issue changes in time when the PDP working group is working on it.\nMTS - 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.\nMTS - AV: And if they determine so, I think they would continue.\nMTS - AV: But if the answer is no, then again, that would take us to step one, and under these new, you know, circumstances.\nMTS - 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.\nMTS - AV: Thank you.\nMTS - AV: Don't see any hand raised here, and nobody in the Zoom, so we can continue.\nMTS - AV: Thanks, everyone, for the questions, and on the slide deck, next, we will talk about the advice development at ICANN\nMTS - 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.\nMTS - AV: Within… At-Large Advisory Committee, we have 15 members.\nMTS - AV: As you may know, there are five Regional At-Large organizations within different geographic regions.\nMTS - 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.\nMTS - AV: So, we have 15 members.\nMTS - AV: The Governmental Advisory Committee provides advice on public policy issues.\nMTS - AV: And, it has, it has members, some of the organizations are, also members of the…\nMTS - 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.\nMTS - 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.\nMTS - AV: open to, ICANN community at ICANN87, so you can… you can also follow their meetings.\nMTS - AV: And the Security and Stability Advisory Committee, are, made of, experts on the security and integrity of internets. Naming and address allocation systems.\nMTS - AV: For instance, these two advisory committees, RSSAC and SSAC, will be offering\nMTS - 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.\nMTS - 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.\nMTS - 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.\nMTS - AV: So, there's now a link in the chat for this infographic.\nMTS - 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.\nMTS - AV: And, provides advice, to the ICANN board.\nMTS - AV: So, in this advice development process. Any At-Large Committee member can bring up an issue to the consideration of the ALAC.\nMTS - AV: or at-large advisory committee, And again, you see.\nMTS - AV: similar step here, identification of the issue. It all starts with the identification of the issue, right?\nMTS - AV: And then the second step is, again, scoping phase. The At-Large Advisory Committee would have a discussion.\nMTS - 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.\nMTS - 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.\nMTS - AV: And then what happens is that the ALAC would designate an issue shepherd.\nMTS - AV: Within At-Large, there's a… there's a consolidated policy working group.\nMTS - 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.\nMTS - AV: And then, the small team would report on, potential end-user impacts. To the Consolidated Post Working Group.\nMTS - AV: And then, if the Consolidated Policy Working Group, or CPWG, would like to continue drafting a statement.\nMTS - AV: Then,\nMTS - AV: Then, the small team would work on, drafting this statement, would present it to, Consolidate Post Working Group.\nMTS - AV: And then, based on the feedback received from CPWG, the small group would also\nMTS - AV: Draft a final statement.\nMTS - 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.\nMTS - AV: for ReViva and Ratification.\nMTS - AV: And at the end of the ratification process, if ratified, the ALAC would send the advice to the ICANN board, ICANN organization, or other advisory committees or supporting organizations.\nMTS - AV: So that's how the advice development would work for the At-Large Advisory Committee.\nMTS - AV: And, on the next one, I'd like to talk about\nMTS - AV: How you can participate in this policy and advice development, because, especially for newcomers, it can be, hard to, you know.\nMTS - 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.\nMTS - 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\nMTS - AV: Working group or a community, and.\nMTS - 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.\nMTS - AV: And this way, you would be informed about the hot topics, common discussion items.\nMTS - AV: And then, this would… this would help you, make your own contribution to the, Policy and advice development process.\nMTS - AV: Also, feel free to join mailing list to see the discussions and observe it.\nMTS - 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.\nMTS - AV: And that's what also you can also consider doing.\nMTS - 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.\nMTS - AV: see organizations, and we talked about supporting organizations, advisory committees.\nMTS - AV: Submitting their comment as a group, And if… if they can, And.\nMTS - AV: finalize a statement, finalize the group comment, and ratify it. Then they can submit this comment as a group input.\nMTS - 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.\nMTS - AV: And participate in the public comment process.\nMTS - AV: We… Oh, we did have a question. Let's go ahead. Let's go.\nMTS - AV: Hello, my name is Sanjina Chhetri. I'm from Nepal. I'm a Nixon participant, here.\nMTS - 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.\nMTS - AV: So I just wanted to know the process. Is there a pathway? Is it open to all or I don't know?\nMTS - AV: Just a bit about a pathway.\nMTS - AV: Thank you.\nMTS - 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.\nMTS - AV: an At-Large structure, see how they work, and see if you can get engaged with them.\nMTS - AV: And then, and.\nMTS - AV: with these At-Large structures, you have the regional At-Large organizations within your regions, right?\nMTS - AV: It may be the case that there's no At-Large structure within your region. You may consider, setting up one.\nMTS - 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.\nMTS - 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.\nMTS - AV: you don't have to be in the At-Large Advisory Committee to, contribute to all these processes. You can just, you know.\nMTS - 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.\nMTS - 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.\nMTS - 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.\nMTS - 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.\nMTS - 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.\nMTS - AV: and talking to us, and specifically talking and explaining about their particular community. So, this is the overview.\nMTS - 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\nMTS - AV: major overview of each community, and then you will have the opportunity to ask the question directly to At-Large, to GNSO.\nMTS - AV: to non-commercial stakeholder groups, etc.\nMTS - 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?\nMTS - 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?\nMTS - AV: No, on the slide, you saw the, This…\nMTS - AV: Yeah, this one? No, I think it was referring to the post-development slide, I guess.\nMTS - AV: Let's see… here in the final step, yes, the board consults community and the GAC. So…\nMTS - AV: The GAC is called out here because it's, called out in the bylaws.\nMTS - 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.\nMTS - AV: And, all the ICANN community groups and individuals may submit their comments to this public comment proceeding, including the GAC.\nMTS - AV: But that doesn't mean others are left out. The…\nMTS - AV: The reason that Yak is all called out on the slide is that it's called out in the bylaws.\nMTS - AV: And by the way, during the week, the ICANN board will be meeting with, separately, with those\nMTS - AV: SO and ACs. So if you are interested, for example, in At-Large, it will be very interesting for you to go to\nMTS - 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…\nMTS - 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?\nMTS - 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.\nMTS - AV: you know, in addition to the GAC, other advisory committees are also invited, so if they wish to participate, they can\nMTS - 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.\nMTS - 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,\nMTS - AV: At-Large also has representatives within the PDP working group, just like GAC.\nMTS - 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\nMTS - 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.\nMTS - 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\nMTS - 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.\nMTS - AV: The ones that are pending their, reports, and the ones that have been, closed.\nMTS - 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.\nMTS - AV: On the next slide, so this is…\nMTS - 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.\nMTS - AV: If you look at the right-hand side, you can see when the proceeding was open for submissions, when it will be closed.\nMTS - 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…\nMTS - AV: you will be able to do that. And if you need to contact, the ICANN Org staff member, opening this\nMTS - AV: Public comment to ask for clarification, before you submit your comment, you can also see a contact information there. To do so.\nMTS - AV: Do we have any other questions around public comment, or anything else?\nMTS - AV: Yes, sounds fine.\nMTS - 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.\nMTS - AV: And I participate in some of the working groups, especially the Consolidated Policy Working Group.\nMTS - AV: We are one of the committees or the community groups that oversees most of the policies within ICANN.\nMTS - 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\nMTS - 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\nMTS - AV: organization and structure.\nMTS - AV: to rule my country.\nMTS - AV: I can also write individual as an individual, a public comment.\nMTS - 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…\nMTS - 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.\nMTS - 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\nMTS - AV: is important.\nMTS - AV: It contributes to the resolution or the proceeding that is being consulted, and that it's documented.\nMTS - AV: Don't write something for the sake of writing it. It has to…\nMTS - AV: Contribute in some ways to, the policy process.\nMTS - AV: Thank you.\nMTS - AV: Do we have one more question?\nMTS - AV: Okay, I think we have a few minutes left. How many questions do you think we can take? Two?\nMTS - AV: We will take one question here and one there. Those who didn't ask questions during We'll come back.\nMTS - AV: Okay.\nMTS - AV: Hello, everyone. My name is Solange Olude. I'm from Bene. I'm a Folo.\nMTS - AV: And thank you very much for this opportunity, and… Thank you for your presentation.\nMTS - AV: I have.\nMTS - AV: One question. My question is.\nMTS - AV: For a fellows who want to remain actively involved in ICANN's policy development process After the meeting, Wal wool.\nMTS - AV: Your recommendation… your recommendation as most first step.\nMTS - AV: to take, especially for someone who still builds them experience.\nMTS - 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.\nMTS - AV: Thank you. Thank you. So again, based on your interest, profession.\nMTS - 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.\nMTS - AV: For the, non-commercial users, not-for-profit organizations.\nMTS - AV: And then for commercial part, you have business constituency, intellectual property constituency.\nMTS - AV: Internal service providers, and then the contracted parties. Let's say if you are.\nMTS - AV: technical person who is interested in the DNS, and also working on DNS root server system, maybe.\nMTS - AV: then in this case, you can apply to become a member of RSSAC Caucus, which is composed of DNS experts\nMTS - 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.\nMTS - 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\nMTS - 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…\nMTS - 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.\nMTS - AV: And then observing mailing lists are… is always a good step in the initial stages. So, And…\nMTS - 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.\nMTS - AV: When there is a report\nMTS - AV: Offer public comment. There's a detail, information, and you can go read it, and then.\nJovita Kanza, ICANN87 Fellow: Great meeting.\nJovita Kanza, ICANN87 Fellow: Reading room…\nMTS - 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.\nMTS - AV: Thank you.\nMTS - AV: Very brief, 10 seconds.\nMTS - AV: AL\nMTS - 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.\nMTS - AV: Thank you for the question. So…\nMTS - AV: Defining the consensus or, you know, determining a consensus, is often…\nMTS - AV: left to, working group leadership. And the working group leadership should be, working under certain, You know.\nMTS - AV: talents, I would say, and, some.\nMTS - 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.\nMTS - AV: Encouraging that kind of atmosphere within the working group.\nMTS - AV: So, when it comes to, determining consensus, the working group leadership may say.\nMTS - 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.\nMTS - AV: They could ask the question if, you know.\nMTS - 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.\nMTS - 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.\nMTS - 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.\nMTS - AV: Thank you, Ozan, and thank you very much for this very interesting session. I hope…\nMTS - 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.\nMTS - AV: And, before we go to the next session, we are starting the series of Get to Know ICANN Community.\nMTS - 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.\nMTS - AV: Please go enjoy and come back here in 25 minutes. Thank you.", "scope": "whole_published_caption_track", "source_sha256": "fe6be885d2611b136e8a3216ed01cf0a064e04fa914e25c5009ecfa18c6aebfa", "attribution": "Made by AgentCommunity // Balázs Némethi", "terminology_correction": { "accepted": [ { "segment_id": 34, "before": "CCNSO", "after": "ccNSO", "evidence": [ "D1" ], "reason": "Canonical capitalization of the ccNSO acronym." }, { "segment_id": 37, "before": "CCNSO", "after": "ccNSO", "evidence": [ "D1" ], "reason": "Canonical capitalization of the ccNSO acronym." }, { "segment_id": 46, "before": "GTLD", "after": "gTLD", "evidence": [ "D1" ], "reason": "Canonical capitalization of the gTLD acronym." }, { "segment_id": 105, "before": "Gac", "after": "GAC", "evidence": [ "D1" ], "reason": "Canonical capitalization of the GAC acronym." }, { "segment_id": 328, "before": "RSEC", "after": "RSSAC", "evidence": [ "D1" ], "reason": "Corrects mis-transcribed acronym to RSSAC." }, { "segment_id": 328, "before": "SSEC", "after": "SSAC", "evidence": [ "D1" ], "reason": "Corrects mis-transcribed acronym to SSAC." }, { "segment_id": 352, "before": "ALEC", "after": "ALAC", "evidence": [ "D1" ], "reason": "Corrects mis-transcribed acronym to ALAC." }, { "segment_id": 461, "before": "RSEC", "after": "RSSAC", "evidence": [ "D1" ], "reason": "Corrects mis-transcribed acronym to RSSAC." } ], "rejected": [ { "proposal": { "segment_id": 34, "before": "contract code name supporting organization", "after": "Country Code Names Supporting Organization", "evidence": [ "D1" ], "reason": "Corrects mis-transcribed expansion to the canonical SO name." }, "reason": "Replacement must be a canonical glossary term" }, { "proposal": { "segment_id": 36, "before": "CCNSO", "after": "ccNSO", "evidence": [ "D1" ], "reason": "Canonical capitalization of the ccNSO acronym." }, "reason": "Source term must occur exactly once; duplicate edits are rejected" }, { "proposal": { "segment_id": 36, "before": "CCNSO Council", "after": "ccNSO Council", "evidence": [ "D1" ], "reason": "Canonical capitalization of the ccNSO Council." }, "reason": "Replacement must be a canonical glossary term" }, { "proposal": { "segment_id": 37, "before": "generic name supporting organization", "after": "Generic Names Supporting Organization", "evidence": [ "D1" ], "reason": "Canonical expansion of GNSO." }, "reason": "Replacement must be a canonical glossary term" }, { "proposal": { "segment_id": 43, "before": "Generic Name Supporting Organization", "after": "Generic Names Supporting Organization", "evidence": [ "D1" ], "reason": "Canonical expansion of GNSO." }, "reason": "Replacement must be a canonical glossary term" }, { "proposal": { "segment_id": 43, "before": "Generic Name Supporting Organization", "after": "Generic Names Supporting Organization", "evidence": [ "D1" ], "reason": "Canonical expansion of GNSO." }, "reason": "Replacement must be a canonical glossary term" }, { "proposal": { "segment_id": 58, "before": "generic name supporting organization", "after": "Generic Names Supporting Organization", "evidence": [ "D1" ], "reason": "Canonical expansion of GNSO." }, "reason": "Replacement must be a canonical glossary term" }, { "proposal": { "segment_id": 461, "before": "RSEC Caucus", "after": "RSSAC Caucus", "evidence": [ "D1" ], "reason": "Corrects mis-transcribed acronym to RSSAC." }, "reason": "Replacement must be a canonical glossary term" }, { "proposal": { "segment_id": 462, "before": "RSEC", "after": "RSSAC", "evidence": [ "D1" ], "reason": "Corrects mis-transcribed acronym to RSSAC." }, "reason": "Source term must occur exactly once; duplicate edits are rejected" }, { "proposal": { "segment_id": 462, "before": "RSEC", "after": "RSSAC", "evidence": [ "D1" ], "reason": "Corrects mis-transcribed acronym to RSSAC." }, "reason": "Source term must occur exactly once; duplicate edits are rejected" }, { "proposal": { "segment_id": 462, "before": "RSEC caucus", "after": "RSSAC Caucus", "evidence": [ "D1" ], "reason": "Corrects mis-transcribed acronym to RSSAC." }, "reason": "Replacement must be a canonical glossary term" }, { "proposal": { "segment_id": 467, "before": "RSEC Caucus", "after": "RSSAC Caucus", "evidence": [ "D1" ], "reason": "Corrects mis-transcribed acronym to RSSAC." }, "reason": "Replacement must be a canonical glossary term" } ], "response_sha256": "5011b176e503b78ecac5722c7b342a28bf40738c8f8d48ffccbdf464ffd8d40f" } }