WEBVTT 1 00:00:01.030 --> 00:00:10.450 MTS - AV: Good morning and in progress. Welcome to the ICANN 87 GAC discussion on new GTLDs on Saturday, 17 October at 1500 local time. 2 00:00:10.560 --> 00:00:26.779 MTS - AV: Please note that this session is being recorded and is governed by the ICANN Expected Stance of Behavior, ICANN Community Participant Code of Conduct, and the ICANN Community Anti-Harassment Policy. During this session, questions or comments will be read aloud if submitted in the proper form in the Zoom chat pod. 3 00:00:26.960 --> 00:00:44.409 MTS - AV: Interpretation for this session will include all 61 languages and Portuguese. If you would like to speak during this session, please raise your hand in the Zoom room. Please remember to state your name for the record and the language you will be speaking, in case speaking a language other than English. And please speak in a reasonable pace to allow for accurate interpretation. 4 00:00:44.550 --> 00:00:49.799 MTS - AV: I will now leave the floor to Marco Hojwani, GAC Vice Chair. Please, over to you, thank you. 5 00:00:50.570 --> 00:01:03.320 MTS - AV: Thank you, Julia. Good afternoon, colleagues. I'll be guiding you through as our chair, Nico, is unavailable, busy with a board meeting this afternoon. Can I have the next slide, please? 6 00:01:03.710 --> 00:01:21.609 MTS - AV: As mentioned, more new GTLDs. So we again have a couple of colleagues from ICANN organization on stage to provide us even with more information about the next round and what has happened in the last few months. 7 00:01:21.610 --> 00:01:39.560 MTS - AV: And then, as we were discussing, we leave about half the session open, in which Benedetta and I will guide you through what is done so far in terms of CAC readiness, and pick up on the questions we just had left over from the… 8 00:01:39.790 --> 00:01:55.129 MTS - AV: previous session. Before we go on, next slide, please. As, the CAC new GTLD topic leads, I'm, I'm here as your vice chair. I'm also one of the CAC topic leads, 9 00:01:55.130 --> 00:02:18.840 MTS - AV: You see probably a few familiar names here, but this is the team within the GAC that has been working on this topic also very extensively with ICANN Org to plan these sessions. So Tracy Heckscher in the room, Niu Piu, Rita Tahir from Canada, who unfortunately couldn't join us. Ken Ying, I believe, is in the room. 10 00:02:18.840 --> 00:02:32.990 MTS - AV: from Chinese Taipei, and, and Tiago, you already heard this morning. So, this is a joint operation. I drew the short straw. I'm with you here this afternoon. And, with that, I'll hand over to, Marika, I guess? 11 00:02:34.250 --> 00:02:42.470 MTS - AV: Thank you very much, Marco. I'll kick this off. And hello, welcome back, everyone, again. I think this is session three out of four. 12 00:02:42.530 --> 00:02:59.399 MTS - AV: That we're talking about, new GTLD, program-related topics. So, my name is, Marika Konings, I'm the, the lead for the new GTLD program, joined here by, Jared and Eduardo! And other team members are in the room as well, to help, address any questions, you may have. 13 00:02:59.400 --> 00:03:03.649 MTS - AV: I think the next slide has our agenda. We'll do one more. 14 00:03:03.740 --> 00:03:27.799 MTS - AV: So, what we'll be covering as part of our overview is basically items two to five. We'll first have a look at the 2026 round timeline, where we're currently at and what is coming next. Looking at 2026 round application highlights, I hope you're all very excited when you saw the Reveal Day results earlier this 15 00:03:27.800 --> 00:03:29.560 MTS - AV: This week. Last week. 16 00:03:29.560 --> 00:03:47.849 MTS - AV: Where are we at? Last year. And then looking at as well what's next in the evaluation process. And then a quick look at the application publication and statistics before we'll hand you back to Marco and Benedetta to look at GAC operational readiness. 17 00:03:47.910 --> 00:03:49.580 MTS - AV: Go to the next slide, please. 18 00:03:52.000 --> 00:04:14.009 MTS - AV: Just a quick disclaimer, and you will have already heard this in previous sessions. Again, a lot of the information we're sharing is for informational purposes. The authoritative information is contained in the applicant guidebook. So please use that for your reference if you're looking for the rules and procedures that govern the program. 19 00:04:14.450 --> 00:04:16.310 MTS - AV: If we go to the next slide, please. 20 00:04:18.680 --> 00:04:43.669 MTS - AV: This is a quick plug for all the other sessions that are happening this week. The program has been here with you today, and I think we still have another session tomorrow with you as well. But we've also prepared for a number of community sessions that are really intended to help as well applicants as well as community members to understand and prepare for what is next and what their role is in the different processes. 21 00:04:43.670 --> 00:04:51.649 MTS - AV: So, on Sunday, that starts with a pre-evaluation stage overview. Tuesday, we focus on application community input. 22 00:04:51.650 --> 00:04:57.070 MTS - AV: On Wednesday, string evaluation. On Thursday, we have a general wrap-up. 23 00:04:57.070 --> 00:05:09.289 MTS - AV: And on Monday, we are having a bit of a more plenary type session where we're having a high level overview of the timeline, what is next, what have we seen on reveal day, which again is open, of course, for everyone. 24 00:05:09.290 --> 00:05:33.389 MTS - AV: And then I also want to mention we do have a booth here. It's right next to the entrance. Staff members will be there on various moments of time. If you do have further questions that you would like answers to, please come and find us at the booth if you're not able to attend any of these sessions. And we'll, of course, try to address your questions there. Anyone who's participating remotely, we do have 25 00:05:33.390 --> 00:05:47.999 MTS - AV: Other channels as well, global support@icann.org for those that have general questions. And if you're an applicant, we have TAMS available, the TLD application management system where you can submit your questions directly. 26 00:05:48.400 --> 00:05:50.109 MTS - AV: We'll go to the next slide, please. 27 00:05:51.590 --> 00:05:52.899 MTS - AV: And the next one? 28 00:05:54.100 --> 00:05:55.390 MTS - AV: Thanks. 29 00:05:55.730 --> 00:06:03.270 MTS - AV: So this is a timeline that I think most of you will have seen previously, but now we actually have some confirmed dates in there as well. 30 00:06:03.270 --> 00:06:16.349 MTS - AV: I think you're all aware that we had a submission period running from the 30th of April to the 12th of August. That has now closed. That was then followed by a reveal day, which happened on the 7th of October. 31 00:06:16.350 --> 00:06:37.499 MTS - AV: That at the same time that marked the start of what is referred to as the replacement period, a 14 day period, a 14 day window that runs until the 21st of October, during which those applicants that submitted an eligible replacement string have an opportunity to switch to that replacement string. 32 00:06:37.610 --> 00:06:48.100 MTS - AV: That then will lead us into String Confirmation Day on the 17th of November, and then shortly after that, String Evaluation will begin as well. 33 00:06:48.150 --> 00:06:58.940 MTS - AV: String Confirmation Day will also mark the start of the community input and objection period, and Elisa provided details on what that entails in the previous session. 34 00:06:59.020 --> 00:07:14.680 MTS - AV: And that will run until the 16th of March 2027. There are, of course, still further milestones that will follow that, amongst others, the prioritization draw, publication of string evaluation results, and the start of, 35 00:07:14.810 --> 00:07:29.899 MTS - AV: Applicant and application evaluations and, and, timelines and dates for those will be published in the near future as well, as the team is going through its further, planning for those activities, as we, as we progress. 36 00:07:30.840 --> 00:07:32.810 MTS - AV: We go to the next slide, please. 37 00:07:35.050 --> 00:07:36.300 MTS - AV: And the next one? 38 00:07:38.740 --> 00:07:45.710 MTS - AV: So this is just a quick reminder around the objectives of the program, and I think someone 39 00:07:45.740 --> 00:08:05.089 MTS - AV: in a previous session asked when we would be looking at, you know, assessment, you know, what did we find on Reveal Day. But taking a step back, looking at the overall objective that was affirmed by the subsequent procedures final report, the report that the community developed that set out the rules and guidance for the program, is that 40 00:08:05.090 --> 00:08:13.299 MTS - AV: Primary purposes of the new GTLDs are to foster diversity, encourage competition, and enhance the utility of the DNS. 41 00:08:13.760 --> 00:08:14.690 MTS - AV: And. 42 00:08:14.990 --> 00:08:32.210 MTS - AV: It is important to note that although we have also the SOPRO final report as well as the Competition, Consumer Trust and Consumer Choice Review Team recommendations, the CCT, they do not establish success indicators or benchmarks. 43 00:08:32.230 --> 00:08:45.040 MTS - AV: They look at establishing metrics, basically aspects that we need to measure, and areas in which the program can be assessed, but there's no numerical benchmark that determines whether a round is a success. 44 00:08:46.080 --> 00:09:01.100 MTS - AV: The CCT work is explicitly focusing on assessing the effects of new GTLD expansion on competition, consumer choice, and consumer trust, as well as the effectiveness of the application and evaluation processes and safeguards. 45 00:09:01.400 --> 00:09:20.439 MTS - AV: And ICANN has worked with the community to develop the metrics and baseline data that support those assessments. And many of those are focused on what happens after the evaluation process completes and GTLD applicants are hopefully successful and able to sign their agreement with ICANN. 46 00:09:21.900 --> 00:09:46.650 MTS - AV: Important to note, there is a specific success indicator for the applicant support program, and I think we'll talk more about that tomorrow, where there is a numerical success factor that has been created. So, as I said, I think it's important to note there is, of course, an objective, and we are looking at what the data tell us, but there's no overall numerical threshold that was set. And, of course, this is just a first look at the data based on 47 00:09:46.650 --> 00:09:51.980 MTS - AV: what Reveal Day has told us, but there's still many and more steps to come in the process. 48 00:09:52.660 --> 00:09:54.109 MTS - AV: Go to the next slide. 49 00:09:56.910 --> 00:09:57.760 MTS - AV: Thank you. 50 00:09:58.360 --> 00:10:21.409 MTS - AV: So this is a snapshot of the current data following Reveal Day. An important disclaimer here at the top, these statistics will remain subject to change until String Confirmation Day on the 17th of November. And obviously further changes may occur after that as well, depending on evaluation results and other processes that are applicable. 51 00:10:21.850 --> 00:10:29.220 MTS - AV: So there are 1,650 total applications that are proceeding in the application process. 52 00:10:29.360 --> 00:10:38.949 MTS - AV: Of those, 1,169 submitted a replacement string, but of those, only 442 are eligible. 53 00:10:39.190 --> 00:10:47.799 MTS - AV: And I think we discussed this previously, this means that they are not identical to another applicant's primary applied for string or replacement string. 54 00:10:48.670 --> 00:11:00.700 MTS - AV: 481 organizations submitted new GDD applications. There are 263 contention sets that include 891 applications in contention. 55 00:11:00.980 --> 00:11:13.000 MTS - AV: And the map in the middle highlights the regional distribution of applicants and applications. And we'll have a further look on that in a future slide. 56 00:11:13.000 --> 00:11:21.549 MTS - AV: We were happy to report that from the 1,650 applications from 481 applicant organizations, they come from all five ICANN regions. 57 00:11:23.440 --> 00:11:31.109 MTS - AV: You can also see here the number of types of applications here, which we'll also cover in a bit more detail on the next slide. 58 00:11:31.860 --> 00:11:49.990 MTS - AV: I said, you know, Reveal Day, of course, provides an important early indicator, but diversity in the DNS is broader than a single application category, and they may therefore, of course, be too early to draw any conclusions at this point, based on what we've seen here. 59 00:11:51.020 --> 00:11:57.200 MTS - AV: And I think with that, we can go to the next slide. We're diving a little bit deeper into some of the numbers. 60 00:11:57.320 --> 00:12:01.810 MTS - AV: Here, so this is looking a bit more detail on the contention sets. 61 00:12:02.010 --> 00:12:17.189 MTS - AV: As I said, 263 contention sets were identified following reveal day. 891 applications are currently in contention, which basically means that most of the contention sets contain multiple applications. 62 00:12:17.870 --> 00:12:22.530 MTS - AV: I did just lose my Zoom, but that's okay. 63 00:12:22.530 --> 00:12:46.350 MTS - AV: We've discussed this as well in some of the previous sessions. There are a number of contention resolution mechanisms that are in place. Replacement string is one of those. Applicants have the current period to make that determination if they have an eligible replacement string. There's an opportunity for brand applicants that are in contention to use the string change process that is available to them. 64 00:12:46.550 --> 00:12:57.529 MTS - AV: Community priority evaluation, another process that's available to community applicants. And then there's of course the ICANN Nutritility Auction process. 65 00:13:00.310 --> 00:13:13.399 MTS - AV: Maybe an important reminder here as well, although applicants may be able to, get out of the current or existing contention set through replacement string, that may not mean that 66 00:13:13.540 --> 00:13:28.349 MTS - AV: They are guaranteed being out of contention, because there are, of course, other processes that could place an applicant in contention, such as string similarity or single and plural notifications, which we've also spoken about previously. 67 00:13:29.120 --> 00:13:38.019 MTS - AV: And maybe an important note as well to remind everyone that private resolution of contention is prohibited under the application applicant guidebook section. 68 00:13:38.570 --> 00:13:40.300 MTS - AV: 5.2.3. 69 00:13:41.770 --> 00:13:43.570 MTS - AV: Go to the next slide. 70 00:13:46.810 --> 00:14:06.639 MTS - AV: Here, a further breakdown of the applicant geographic distribution. As said, we have all five ICANN regions represented with Europe having the highest percentage of applications. It's 53.5% from 198 applicants. 71 00:14:06.660 --> 00:14:07.950 MTS - AV: And. 72 00:14:08.110 --> 00:14:12.779 MTS - AV: Oh, I see here that the number does not align. I'll need to look at that. Sorry, I mixed them up. 73 00:14:13.270 --> 00:14:35.860 MTS - AV: But it's, I think, important to remember here as well that just because an applicant may be incorporated in a certain location, that of course doesn't necessarily mean that they do business there. So again, this gives us some indication but does not necessarily tell the whole picture about applications and what it means for the DNS and how GTLD may be used in the future. 74 00:14:37.550 --> 00:14:50.289 MTS - AV: If we go to the next slide, I think it's the last one I had in my section. This just gives a more detailed breakdown in the different aspects of, you know, participation and intended use. We have 75 00:14:50.290 --> 00:15:00.550 MTS - AV: You know, 21 IDN applications or internationalized domain names. That's representing a 1.3 share of all applications. Community designated applications. 76 00:15:00.550 --> 00:15:16.980 MTS - AV: 16 geographic name applications, 15 dot brand, 333. And ASP-supported, applicants, 51 that submitted, an application. And we'll have more time tomorrow to talk about the applicant support program. 77 00:15:16.980 --> 00:15:21.110 MTS - AV: And what the Reveal Day data has shown. 78 00:15:22.870 --> 00:15:25.820 MTS - AV: I think with that, I'm handing it to Jared. 79 00:15:27.670 --> 00:15:35.009 MTS - AV: Thanks, Marika. Excuse me. Thanks, Marika. Hi, everyone. My name is Jared Erwin. I'm also on the NuGE program team. 80 00:15:35.040 --> 00:15:54.879 MTS - AV: And one of the GAP co-leads, GAP — sorry, we can go to the next slides. GAP refers to the gTLD application process, which is the function under the NUGI program that houses all the different stages, which we now see on the screen of the application lifecycle. 81 00:15:54.980 --> 00:16:05.000 MTS - AV: And so I'm going to walk you through a couple of the key points about where we are in the process and what's coming up next. 82 00:16:06.400 --> 00:16:26.949 MTS - AV: So you can see here, and if you were in our earlier sessions, you probably saw this already. But we are in the pre-evaluation stage, which precedes things like string evaluation and application evaluation and also the community input and objections period and contention. 83 00:16:27.090 --> 00:16:45.040 MTS - AV: And, just to note here that this is the general lifecycle for applications, but, it's not necessarily linear, as some applications may go through, the community input, or be subject to an objection, or if they're in contingent, have to go through, 84 00:16:45.080 --> 00:16:49.430 MTS - AV: Those processes before moving on to subsequent steps. 85 00:16:50.700 --> 00:16:52.910 MTS - AV: And we'll talk a little bit more about 86 00:16:53.030 --> 00:16:59.110 MTS - AV: What pre-evaluation means and other steps related to that on the next slides. 87 00:16:59.430 --> 00:17:01.359 MTS - AV: Next slide, please. 88 00:17:04.280 --> 00:17:24.259 MTS - AV: So again, you may have already seen this in earlier sessions but we are now there at step three following reveal day which occurred on the 7th of October. As you, as you know, the application submission period ended on the 12th of August a couple months ago already. 89 00:17:24.260 --> 00:17:44.170 MTS - AV: And, following that, there was an administrative check, and then reveal day, and now we are in the replacement period, where applicants with, eligible replacement strings can, choose the… they'll have the option now to choose to proceed with their replacement string application, or not. 90 00:17:44.200 --> 00:17:50.189 MTS - AV: And again, this is designed to help them potentially avoid contention. 91 00:17:50.450 --> 00:18:09.980 MTS - AV: This period will end in a couple days, on the 21st, and that will lead us to String Confirmation Day on the 17th of November, which is when the final applied-for strings and applications, will be published, as well as the updated list of contention sets, 92 00:18:10.100 --> 00:18:13.020 MTS - AV: Based on the outcome of the replacement period. 93 00:18:13.420 --> 00:18:20.440 MTS - AV: This will also mark, the beginning of the community input and string evaluation periods. 94 00:18:23.030 --> 00:18:34.469 MTS - AV: And then you also note here the step five, the prioritization draw, which is to occur in the first half of 2027. 95 00:18:34.540 --> 00:18:44.140 MTS - AV: We talked, again, quite a bit about this earlier, in the earlier sessions, but this is the draw to determine priority numbers for application processing. 96 00:18:45.320 --> 00:18:53.079 MTS - AV: And, this becomes relevant only after string evaluation, for things like application evaluation. 97 00:18:53.610 --> 00:18:59.450 MTS - AV: So, the draw will occur in the first half of 2027, which more aligns with when 98 00:18:59.660 --> 00:19:03.090 MTS - AV: The priority numbers come into play. 99 00:19:03.800 --> 00:19:06.129 MTS - AV: After the conclusion of string evaluation. 100 00:19:08.990 --> 00:19:09.720 MTS - AV: Okay. 101 00:19:10.880 --> 00:19:12.839 MTS - AV: Next slide, please. 102 00:19:14.880 --> 00:19:31.579 MTS - AV: So, now moving into, a little bit more detail about what happens, during the community input period, as well as the string evaluation period, which again, you may have already seen a lot about, earlier. 103 00:19:32.090 --> 00:19:47.300 MTS - AV: But the community input, period includes, different processes related to, application comments, GAC member early warnings, GAC consensus advice, singular plural notifications, and objections. 104 00:19:47.930 --> 00:20:02.469 MTS - AV: For application comments, this is, allows anyone to bring issues to the intention of ICANN applicants and evaluators. Those can be submitted from string confirmation day. 105 00:20:03.500 --> 00:20:07.880 MTS - AV: Within 104 days or 30 days, 106 00:20:08.050 --> 00:20:11.989 MTS - AV: The 104 days following Trin Confirmation Day, or 30 days, 107 00:20:12.400 --> 00:20:29.699 MTS - AV: after, specific change requests, that require a comment period. The outcome of those comments is there's no direct impact on applications, but they… those comments might be considered by evaluators as they conduct, evaluations. 108 00:20:30.460 --> 00:20:48.179 MTS - AV: Gac member early warnings, again, we, we just talked a lot about this in the previous session, but these, allow GAC, members and observers to, provide an early indication that an application is potentially problematic. 109 00:20:49.350 --> 00:20:53.570 MTS - AV: And again, those are submitted during the community input period. 110 00:20:54.260 --> 00:21:05.050 MTS - AV: And again, no direct impact on the application based on that early warning, but it may be a signal that the application could be the subject of GAC consensus advice. 111 00:21:05.960 --> 00:21:21.379 MTS - AV: And, CAC consensus advice, I think you're probably aware of what that consists of, but this is advice to the ICANN board, related to applications which are sensitive or potentially violate, 112 00:21:21.500 --> 00:21:23.559 MTS - AV: Public policy or laws. 113 00:21:25.930 --> 00:21:38.589 MTS - AV: And that can be submitted at any time, and the outcome there is that the board will make a decision as to whether the application can proceed or not, or needs to proceed with modifications. 114 00:21:41.850 --> 00:21:50.329 MTS - AV: During this period, there's also a process for Singular Plural Notification, which is… 115 00:21:50.330 --> 00:22:02.010 MTS - AV: open to anyone who, identifies, if an I applied for string is the singular or plural of another applied for string, or delegated TLD, or a string, from a previous new GLT. 116 00:22:02.170 --> 00:22:04.610 MTS - AV: New GTLD round or block name. 117 00:22:04.960 --> 00:22:20.279 MTS - AV: Which would trigger an evaluation period. And then finally, objections, which can be, submitted on different grounds, string confusion, legal rights, limited public interest, or community objections, and that's available to those parties, withstanding. 118 00:22:20.350 --> 00:22:25.690 MTS - AV: And the panel will determine whether the application can proceed or needs to be modified. 119 00:22:27.340 --> 00:22:29.250 MTS - AV: Next slide, please. 120 00:22:29.460 --> 00:22:31.629 MTS - AV: Oh, I see a hand from Jorge. 121 00:22:34.640 --> 00:22:35.680 MTS - AV: Switzerland? 122 00:22:36.900 --> 00:22:55.290 MTS - AV: Thank you, Marco. Jorge Gancio, Switzerland, for the record. I just was thinking whether in the interest of time and as we've seen these slides a while ago, whether we could go to those aspects that are really new. 123 00:22:55.670 --> 00:22:57.780 MTS - AV: And we haven't discussed before. 124 00:22:58.830 --> 00:22:59.760 MTS - AV: Thank you. 125 00:23:03.140 --> 00:23:13.719 MTS - AV: Yes, I think that makes sense, but I think this slide here is, I don't think we've discussed this as yet, these are the key components of the string evaluation, so. 126 00:23:13.830 --> 00:23:18.030 MTS - AV: I think that sounds okay, I can proceed with this slide. 127 00:23:19.040 --> 00:23:21.010 MTS - AV: I do see there's another hand. 128 00:23:23.290 --> 00:23:25.380 MTS - AV: India, you have the floor, please. 129 00:23:30.310 --> 00:23:33.290 MTS - AV: Thank you, Santosh for the record. 130 00:23:33.630 --> 00:23:40.479 MTS - AV: So regarding the GAC consensus as, making a preliminary research of. 131 00:23:40.730 --> 00:23:44.089 MTS - AV: 1,615 strings. 132 00:23:45.020 --> 00:23:49.789 MTS - AV: It has been seen seen that certain strings like. 133 00:23:50.600 --> 00:23:52.209 MTS - AV: Dot passport. 134 00:23:53.040 --> 00:23:54.480 MTS - AV: Dot Railway. 135 00:23:55.140 --> 00:23:56.700 MTS - AV: Dot defense. 136 00:23:57.530 --> 00:23:59.040 MTS - AV: Dot Civic. 137 00:24:00.310 --> 00:24:02.190 MTS - AV: And dot aid. 138 00:24:02.470 --> 00:24:08.429 MTS - AV: So these are the 5 preliminary strings which has to which has come to the notice. 139 00:24:08.920 --> 00:24:10.050 MTS - AV: By which? 140 00:24:10.340 --> 00:24:13.910 MTS - AV: It is used for public services. 141 00:24:14.980 --> 00:24:17.070 MTS - AV: In most of the countries. 142 00:24:17.790 --> 00:24:18.670 MTS - AV: So. 143 00:24:19.450 --> 00:24:22.030 MTS - AV: Could a whether. 144 00:24:22.650 --> 00:24:25.270 MTS - AV: A GAC consensus can be raised. 145 00:24:25.440 --> 00:24:27.369 MTS - AV: On these strings. 146 00:24:27.740 --> 00:24:31.339 MTS - AV: So it is not limited to these strings there could be. 147 00:24:31.590 --> 00:24:33.139 MTS - AV: Further strings also. 148 00:24:33.830 --> 00:24:36.319 MTS - AV: As mentioned in the. 149 00:24:36.620 --> 00:24:42.030 MTS - AV: GATT consensus, Advice. It is problematic. 150 00:24:42.320 --> 00:24:45.829 MTS - AV: And it is interested to the national. 151 00:24:45.980 --> 00:24:46.890 MTS - AV: Laws. 152 00:24:47.590 --> 00:24:51.109 MTS - AV: So could these strengths be considered as a GAC? 153 00:24:51.260 --> 00:24:53.200 MTS - AV: Consensus advice. 154 00:24:54.830 --> 00:24:55.540 MTS - AV: Thank you. 155 00:24:58.170 --> 00:25:00.979 MTS - AV: I don't know if any of the ICANN 156 00:25:01.470 --> 00:25:14.370 MTS - AV: colleagues have any comments, but, as we learned in the previous session, GAC advice is always possible, and we have further slots on Tuesday where 157 00:25:14.370 --> 00:25:27.090 MTS - AV: It might be useful for us as GAC members to talk a bit about the issues you just raised and what we think is the best way forward, GAC advice being one of them. 158 00:25:27.560 --> 00:25:40.290 MTS - AV: But as far as I understood, yeah, if we see an issue with a string, the GAC can produce advice. Anything from ICANN work on that part? 159 00:25:41.650 --> 00:26:06.600 MTS - AV: Thanks, Marco. No, nothing to add that is up to the GAC to determine. I think the only thing I would say, and I think there have been other questions about this as well, is that this may also be where the safeguard assessment comes in, where we have a safeguard assessment panel that will review all the strings and whether they fall into specific categories that would require additional safeguards in their contract. 160 00:26:06.600 --> 00:26:10.260 MTS - AV: Safeguard picks public interest commitments. 161 00:26:10.260 --> 00:26:17.140 MTS - AV: So that may, based on the strings that you mentioned, may be a place where they might be 162 00:26:17.470 --> 00:26:19.940 MTS - AV: Subject to additional safeguards. 163 00:26:20.450 --> 00:26:36.530 MTS - AV: And as I was going to mention anyway, and I'll just mention now, but, and of course, the safeguards are based on GAC advice from the 2012 round, the Beijing communique, which listed out different categories of strings that would require additional safeguards to ensure. 164 00:26:36.730 --> 00:26:37.770 MTS - AV: Public Safety. 165 00:26:38.030 --> 00:26:38.810 MTS - AV: Thanks. 166 00:26:41.450 --> 00:26:43.250 MTS - AV: Thank you for clarification. 167 00:26:43.680 --> 00:26:50.669 MTS - AV: Now… If we use safeguards also, but there is a chance of DNS abuse. 168 00:26:51.000 --> 00:26:52.620 MTS - AV: Using these strings. 169 00:26:53.490 --> 00:26:56.949 MTS - AV: Most of the internet users are used to. 170 00:26:57.460 --> 00:26:58.580 MTS - AV: Book there. 171 00:26:59.140 --> 00:27:03.920 MTS - AV: Flight tickets or railway tickets using similar kind of a domain. 172 00:27:04.050 --> 00:27:05.570 MTS - AV: Which is existing. 173 00:27:06.200 --> 00:27:12.409 MTS - AV: Now, if we have a similar kind of a, I'm just taking an example of dot passport. 174 00:27:14.110 --> 00:27:14.930 MTS - AV: So. 175 00:27:15.590 --> 00:27:22.709 MTS - AV: It could be, I mean, there could be a chance of DNS abuse using dot passport. 176 00:27:25.750 --> 00:27:26.440 MTS - AV: Thank you. 177 00:27:32.670 --> 00:27:38.080 MTS - AV: Thank you. I'm not sure I heard a question, or if that's more of a comment, 178 00:27:38.280 --> 00:27:49.179 MTS - AV: I don't know if I can comment on potential DNS abuse related to that string, but again, there's GAC advice, that could be issued for strings, or… 179 00:27:49.310 --> 00:27:54.729 MTS - AV: Where the GAC has concerns, or safeguards potentially might be another mechanism. 180 00:27:55.610 --> 00:27:57.489 MTS - AV: Based on that evaluation. 181 00:27:57.660 --> 00:27:58.460 MTS - AV: Panel. 182 00:27:59.420 --> 00:28:19.489 MTS - AV: And this is Marika, maybe just to add, obviously all successful applicants that go through the contracting process are required as well to meet all the other requirements that already exist, or that will come into play at some point in relation to DNS abuse. I think you may be aware that there are actively ongoing processes, so any 183 00:28:19.620 --> 00:28:30.480 MTS - AV: consensus policy that is developed by the community and adopted by the ICANN board will become applicable to all GTLDs, including successful new GTLD applicants. 184 00:28:33.120 --> 00:28:40.639 MTS - AV: Thank you. There's a bit of a queue forming right now. I've got Switzerland in the UK, so Switzerland's your floor, Gore. 185 00:28:42.280 --> 00:28:52.550 MTS - AV: I'll try to be brief. In the other session, we had a… An initial discussion on safeguards. 186 00:28:52.550 --> 00:29:14.670 MTS - AV: And we were told that there would be a session on safeguards later in the week, but which conflicts with the GAC community. So maybe as an internal question, let's try to have the right people of this safeguards panel on Tuesday morning in the other session we have so we can 187 00:29:14.840 --> 00:29:33.939 MTS - AV: discuss that during our GAC plenary time. If that would be possible, I think we would very much benefit, because as Santosh and others are mentioning, there are already some strings that raise safeguard questions, and 188 00:29:34.390 --> 00:29:47.790 MTS - AV: I guess we should use the opportunity of the in-person meeting we have here, because later on we have to wait to Lisboa, which is wonderful, of course, but only in March. 189 00:29:51.740 --> 00:30:02.590 MTS - AV: Thank you, Jorge. Yeah, I think we can, and as I mentioned, we've got more time scheduled later this week to come back to certain topics. 190 00:30:02.590 --> 00:30:13.260 MTS - AV: if we can't resolve them right here, right now, and then I guess we'll never be able to resolve everything right here, right now. Maybe, UK? 191 00:30:13.280 --> 00:30:14.120 MTS - AV: Paul? 192 00:30:15.770 --> 00:30:22.770 MTS - AV: thank you Paul Blaker for the record I just wanted to support Jorge's request 193 00:30:23.130 --> 00:30:34.140 MTS - AV: I think it will be really important that we, as GAC members, understand in detail how the safeguard assessment will work. 194 00:30:34.670 --> 00:30:41.859 MTS - AV: We probably need to be reminded about the previous GAC advice on this. 195 00:30:42.120 --> 00:30:51.670 MTS - AV: We would like to know what the process will be, what the timeline will be, what the criteria will be, what the possible commitments would be. 196 00:30:51.880 --> 00:30:55.200 MTS - AV: Because I think This will be… 197 00:30:55.210 --> 00:31:15.120 MTS - AV: Incredibly important when we look at the applied force strings in regulated sectors whether that's medicine or finance or education or fundraising, so if we could have that kind of detailed information at the session on Tuesday, I think it will be a really valuable use of time. Thank you. 198 00:31:16.140 --> 00:31:25.319 MTS - AV: Thank you, Kane, noted. I'm very quickly looking at ICANN Org. We can also take this offline, but do you see Fit on joining us on Tuesday? 199 00:31:26.300 --> 00:31:27.310 MTS - AV: For this? 200 00:31:29.290 --> 00:31:32.470 MTS - AV: Tuesday morning, I think, first slot? 201 00:31:33.350 --> 00:31:48.949 MTS - AV: I think we'll look at our calendars and we can kind of check. So we also make sure that we provide you with some level setting information on the safeguard assessments because we understand that indeed there's a great interest that will hopefully then inform your further conversation as well. 202 00:31:50.360 --> 00:32:00.280 MTS - AV: Thank you. That's appreciated. And I just checked indeed. It's Tuesday 9. Then currently in my queue, it's Giacomo WBU. 203 00:32:03.940 --> 00:32:06.429 MTS - AV: Yes, I moved in the room in the meantime. 204 00:32:08.890 --> 00:32:17.200 MTS - AV: Thank you for the floor. I have some general comments, because it seems that now this is the session to make general comments on the whole 205 00:32:17.380 --> 00:32:26.560 MTS - AV: Around, and these comments are made on behalf of the Human Rights and International Law Working group. 206 00:32:26.960 --> 00:32:34.319 MTS - AV: The first… It's useful that Marika remembered us, which were the three main goals of this round. 207 00:32:35.910 --> 00:32:39.660 MTS - AV: The main one was foster diversity, number one. 208 00:32:40.170 --> 00:32:49.749 MTS - AV: If I look at the statistics on the base of what we have received until now, we have 16 applications from Africa, that is less than 1%, 209 00:32:50.470 --> 00:32:55.560 MTS - AV: We have, Latin America is 0.93%. 210 00:32:55.830 --> 00:33:01.060 MTS - AV: And the IDN application are 1.3 Percent of the total. 211 00:33:01.830 --> 00:33:10.410 MTS - AV: Even if you include the Asia Pacific, so let's say most of the world, we arrive at 13.5%. 212 00:33:10.670 --> 00:33:15.480 MTS - AV: of the application. So, if this is promoting the diversity. 213 00:33:16.210 --> 00:33:29.790 MTS - AV: I think that this rings another bell. And probably we need to think that as GAC and in general as ICANN, that we need to change the way we try to achieve diversity. 214 00:33:30.080 --> 00:33:31.750 MTS - AV: Apparently, it didn't work. 215 00:33:33.500 --> 00:33:41.110 MTS - AV: And I hope that on this, we will, as a GAC, we have a bigger reflection. The second point is, I've not… 216 00:33:41.420 --> 00:33:44.909 MTS - AV: Got the time to go through all of it, but… 217 00:33:45.560 --> 00:33:48.020 MTS - AV: I see that there are, some 218 00:33:48.480 --> 00:33:52.039 MTS - AV: Strings that, in theory, we were supposed to 219 00:33:52.210 --> 00:33:58.609 MTS - AV: Have agreed that we have not rights to be there. Like, for instance. 220 00:33:58.900 --> 00:34:04.989 MTS - AV: I see that there are, 8 applications for DOT official, That, for me, seems… 221 00:34:05.190 --> 00:34:14.090 MTS - AV: It's quite dangerous as an application. And, there was also .state that seems deactivated, I don't know… 222 00:34:14.210 --> 00:34:18.070 MTS - AV: Exactly what this means, but it's still in the list. 223 00:34:18.500 --> 00:34:24.799 MTS - AV: About not official, just to give you an example, when I was preparing my application for the visa. 224 00:34:25.230 --> 00:34:32.330 MTS - AV: It appears to me at least 10 different applications, that all of them pretend to be the government of Indonesia. 225 00:34:32.449 --> 00:34:41.970 MTS - AV: And I have to go carefully, one by one, to see which one was the real one. I imagine that if there is .state or .official that are for sale. 226 00:34:42.360 --> 00:34:45.300 MTS - AV: the risk that I will be, 227 00:34:48.330 --> 00:34:57.340 MTS - AV: Misunderstood, or I will make the wrong application, is very high. Then, Another point about… 228 00:34:57.490 --> 00:35:03.669 MTS - AV: The statistics. I haven't seen any list of the community application. 229 00:35:04.860 --> 00:35:19.469 MTS - AV: When it will be available, which they are, because we know that this is a category that deserves special attention from that, from the GAC. And the last point is about the, as I mentioned before. 230 00:35:19.740 --> 00:35:29.679 MTS - AV: For GEO application, that there is no supporting letter in the documentation available, I think, is a mistake. 231 00:35:29.880 --> 00:35:39.739 MTS - AV: I mentioned this morning, and I hope that now this will be made available. I understand that there is a problem about the autograph signature, but we don't need that. We need to know 232 00:35:40.040 --> 00:35:42.060 MTS - AV: Who are the supporting authorities? 233 00:35:42.320 --> 00:35:43.470 MTS - AV: Thank you very much. 234 00:35:45.290 --> 00:35:46.080 MTS - AV: But… 235 00:35:46.080 --> 00:36:10.000 MTS - AV: Thank you for those questions and comments. Maybe starting at the end, as I said or as we explained previously, the support letter not being publicly posted is a result of the applicant guidebook and the questions there. This is similar to 2012. In 2012, there were a number of applicants or supporting authorities that submitted their letters to ICANN through correspondence. 236 00:36:10.000 --> 00:36:23.470 MTS - AV: I think that is still a process that's open to anyone. And of course, there are ways in which GAC members kind of can express their desire to have that information available, which will hopefully then help have applicants kind of come forward. 237 00:36:23.530 --> 00:36:34.829 MTS - AV: I said we're following the process as it was set out in 2012, but I said there are other means in which applicants can at least make that information available should they wish so. 238 00:36:34.830 --> 00:36:44.610 MTS - AV: On the question on the community applications, you can already see that if you go to APS and if you select under TLD type community. 239 00:36:44.630 --> 00:37:00.640 MTS - AV: It will bring up all the applications that have selected community as their type of application. I think you mentioned also the question on deactivated. If it shows deactivated, it means that's an application that's not proceeding forward. 240 00:37:00.640 --> 00:37:05.889 MTS - AV: It's most likely a replacement string that was deemed not eligible. 241 00:37:06.700 --> 00:37:31.569 MTS - AV: And then on your first question, and I think indeed that's a good question as the program progresses and looks at the objectives that were set, what can we do more of, less of or different? I think we have shared previously with the GAC the outreach and engagement report where it shows kind of the spread of engagement activities that our teams 242 00:37:31.570 --> 00:37:56.040 MTS - AV: work through to kind of raise awareness. But it's of course very important to note as well that awareness does not equate to an application. There are many other factors that play into that somewhere. Some that where ICANN may play a role, others maybe depending on local market situations or regulation or other areas. But I think it's something where jointly we can of course look at 243 00:37:56.330 --> 00:38:05.510 MTS - AV: what more, less, better can be done. And of course, very important to notice as well, this is one round of 244 00:38:05.800 --> 00:38:12.860 MTS - AV: many, so I think also, at least from our approach on the outreach and engagement activities, it has always been with 245 00:38:13.030 --> 00:38:20.090 MTS - AV: Having in mind that having that first conversation, having that first awareness may not immediately lead to 246 00:38:20.610 --> 00:38:44.639 MTS - AV: an ability to apply, but at least it allows an open door to start a conversation, start thinking through it. Because again, it's of course a significant undertaking applying for a gTLD. So I said from our perspective, this is a longer term effort and not necessarily something, of course, we would've liked to see maybe different numbers here, but we're also very aware that this is not a one-off 247 00:38:44.640 --> 00:38:57.730 MTS - AV: engagement or opportunity, but a longer-term effort for which we need, I think, everyone's support to get, kind of, the word out and look at what more or different we can do to achieve the goals of the program. 248 00:38:59.900 --> 00:39:21.000 MTS - AV: Thank you, Marika. Thank you, Giacomo. Just on the point, and of course, diversity is really important, helping people from underserved regions. Tomorrow morning, 9:00 AM, we have a session dedicated to the ASP so we can further delve into diversity lessons learned. 249 00:39:21.000 --> 00:39:38.290 MTS - AV: And again, we have some ICANN org staff available for us to guide us through some of what they've seen, some of the data, but plenty of opportunity. In the interest of time, may I ask you to quickly move on to the last bit of the presentation? 250 00:39:44.270 --> 00:40:00.730 MTS - AV: Thank you, yes, and we're gonna go pretty quickly on the following slides, because it involves some information that we've already seen, but we do want to show a quick walkthrough on the website of the Application Publication and Statistics System, or APS for short. So just a quick recap. 251 00:40:00.730 --> 00:40:10.450 MTS - AV: The website is already available, has been since Reveal Day on 7th of October, and this is where you can find all of the submitted applications and their current status. 252 00:40:10.450 --> 00:40:15.509 MTS - AV: And it will be updated once again once we get to String Confirmation Day in November. 253 00:40:15.990 --> 00:40:18.539 MTS - AV: Next slide, please. 254 00:40:19.640 --> 00:40:30.339 MTS - AV: On the section of the applications, here we see on top highlighted the four main sections of APS. Right now, the ones that are available. 255 00:40:30.420 --> 00:40:48.500 MTS - AV: until String Confirmation Day are just statistics and applications. The one with the highlight number 2 is where you will be able to find all of the submitted applications, with the relevant details, of those, including the applicant, the strings, the geographic region. 256 00:40:48.960 --> 00:40:54.239 MTS - AV: And all of the filters that we see further down below is what will let you. 257 00:40:55.220 --> 00:41:01.259 MTS - AV: Focus your search a little bit better to identify which, maybe, applications have a… 258 00:41:01.380 --> 00:41:08.670 MTS - AV: Related field, or, or details that are more relevant to what you might be concerned with reviewing? 259 00:41:10.040 --> 00:41:26.250 MTS - AV: And just a quick reminder here, because the section of contention sets right now is… it's going to be updated at a later date, the actual list of contention sets, for those that are interested in looking at those, are linked in the initial paragraph of this page. 260 00:41:26.420 --> 00:41:28.010 MTS - AV: Next slide, please. 261 00:41:30.530 --> 00:41:40.169 MTS - AV: So, in terms of the search filters, this kind of relates to the question we just received and what Marika spoke about. You will be able to type here, 262 00:41:40.270 --> 00:41:49.510 MTS - AV: To search for specific strings, specific applicants, or identifiers of the applications, if you know what specific one you're looking for. 263 00:41:49.510 --> 00:42:12.940 MTS - AV: On the top search box and then the second box that's highlighted here with number 7, you will be able to have a number of filters where you can check by region, you can search by the application type, you can search by the string or TLD type that was applied for the part about application labels, which is the rightmost field that we see on screen is where you can search for other relevant details such as. 264 00:42:12.990 --> 00:42:20.070 MTS - AV: If the application is from applicant supported in the ASP program, if it's 265 00:42:20.520 --> 00:42:23.759 MTS - AV: If, if, it provided, 266 00:42:24.330 --> 00:42:42.749 MTS - AV: code of conduct exemption, a number of other, details, that are relevant. If it requested the community priority evaluation, all of those can be searched, using these fields. The more you put in this form, the more 267 00:42:44.680 --> 00:42:56.400 MTS - AV: the more conditions the applications need to meet to be listed in the results that are shown below. And you can see the actual details of each individual application by clicking on the… 268 00:42:56.400 --> 00:43:13.060 MTS - AV: string or the application ID that's shown in the list. For those that are more comfortable working with spreadsheets, like in Google Docs or Excel, you can also download your list into a CSV format so that you can work offline. That will allow you to see 269 00:43:13.060 --> 00:43:27.279 MTS - AV: all of the high-level details of the applications in the resulting list below. And that might be more helpful for those of you that are interested in filtering or looking at applications based on their attributes. 270 00:43:29.120 --> 00:43:38.030 MTS - AV: And that's it for me. I do encourage people to, if you have more questions or want to know more about APS, we do have the booth downstairs, so feel free to 271 00:43:38.360 --> 00:43:40.610 MTS - AV: Basically us over there. Thanks. 272 00:43:42.500 --> 00:43:50.410 MTS - AV: Thank you. Just out of curiosity, who of you in the room has already looked at the actual ASP website? 273 00:43:53.690 --> 00:44:03.370 MTS - AV: No? Phew, phew, well… do try, do give it a… do give it a… it might look mighty impressive, but it's, 274 00:44:03.430 --> 00:44:20.279 MTS - AV: It's relatively easy to use once you get the hang of it. And as was mentioned, there's people around here who can help you, so better try it while we have them around. Thank you for that. Unless there are any pressing questions. 275 00:44:20.280 --> 00:44:35.680 MTS - AV: Regarding what was just presented, I'd like to turn it over to our next section. We have about 15 minutes left in this session. So thank you once again for all your time and see you back soon. 276 00:44:36.550 --> 00:44:59.940 MTS - AV: With that and the CAC operational readiness, which is me and Benedetta here to my right, and we have some slides prepared, but I think most of them were shown this morning. If I can have the next slide, I think we kind of would like to skip. 277 00:45:00.370 --> 00:45:18.250 MTS - AV: straight to the discussion, if that's okay, Benedetta? Do you want it? Okay, then let's just move straight into the discussion, and I kind of like to pick up from the… Uk's comment from the previous session, because I thought it was valuable, 278 00:45:18.450 --> 00:45:25.670 MTS - AV: So far, what we have been doing, and then if you flip to the next slide… 279 00:45:27.330 --> 00:45:30.010 MTS - AV: And the next slide. 280 00:45:31.950 --> 00:45:45.609 MTS - AV: This is sort of, this is where we are, in terms of timeline. We've, we've talked you through this this morning, so we have various pathways open for the GAC. 281 00:45:45.920 --> 00:45:47.010 MTS - AV: to… 282 00:45:47.140 --> 00:45:55.399 MTS - AV: make comments, and of course, for the rest of the community as well, they can make comments, the CAC can issue early warnings. 283 00:45:55.580 --> 00:46:08.000 MTS - AV: We can, of course, issue consensus advice if we think the matter is pressing and we feel like taking it that way. 284 00:46:08.620 --> 00:46:22.229 MTS - AV: This is all nice. We have a system to deliver our comments to the applicants, and then especially with the early warnings, that that's sort of the starting point to have a conversation. 285 00:46:22.230 --> 00:46:41.599 MTS - AV: This morning, our Swiss colleague Jorge already mentioned, like, maybe that's not the best start to go immediately public. So looking back at what we've done so far is how to deliver these comments via early warning or via the comments or via GAC advice. 286 00:46:41.730 --> 00:46:48.639 MTS - AV: So, what my takeaway there is, they're all public, and my readout from the Swiss government is. 287 00:46:48.850 --> 00:46:57.260 MTS - AV: Maybe that's not the best start, to immediately go public. Maybe we want to have a conversation with the applicants. 288 00:46:57.510 --> 00:47:02.219 MTS - AV: Beforehand, before we go in all guns blazing and make public comments. 289 00:47:02.830 --> 00:47:16.870 MTS - AV: And then the other thing that was sort of for me and like, ever thought about that is yes, we start that conversation, people make adjustments, maybe we make adjustments, compromise is found. 290 00:47:17.300 --> 00:47:30.729 MTS - AV: we're okay, how do we want to let the applicant, how do we want to let the rest of the ICANN community know that, yes, our comments, we feel, have been addressed? We're okay. 291 00:47:31.310 --> 00:47:46.450 MTS - AV: Now, of course, we can reopen the readiness documents. My immediate suggestion would be to seek, then, a third item, especially regarding what to do when we feel satisfied, but… 292 00:47:46.790 --> 00:48:00.950 MTS - AV: In that, as a vice chair, as one of the GTLD topic leads, also in your hands, how would such a process look like? What do you feel is important? 293 00:48:00.970 --> 00:48:10.010 MTS - AV: Maybe United Kingdom. Paul, you want to come back to your comments this morning or Gorgen? What are you thinking? 294 00:48:11.060 --> 00:48:11.950 MTS - AV: Paul? 295 00:48:14.220 --> 00:48:17.510 MTS - AV: Thank you, Marco. Paul Blake, for the record. 296 00:48:18.220 --> 00:48:23.790 MTS - AV: Yes, I think… Obviously, it's important to remember that 297 00:48:24.230 --> 00:48:31.050 MTS - AV: GAC member early warnings are… they're not from the GAC as a whole, they're from a member… 298 00:48:31.170 --> 00:48:34.180 MTS - AV: of the GAC or a group of members of the GAC. 299 00:48:35.710 --> 00:48:39.700 MTS - AV: And I'm thinking, for example, in our case, if the United Kingdom 300 00:48:40.800 --> 00:48:44.140 MTS - AV: Issued an early warning about an application. 301 00:48:45.100 --> 00:48:47.420 MTS - AV: And then we spoke to the applicant. 302 00:48:47.790 --> 00:48:52.639 MTS - AV: And we found that all of our concerns were addressed, and we were okay. 303 00:48:53.200 --> 00:49:01.199 MTS - AV: then we would like to be able to communicate that. We would like to close the early warning in some way. 304 00:49:01.910 --> 00:49:05.950 MTS - AV: And not having it exist permanently. 305 00:49:06.710 --> 00:49:11.949 MTS - AV: So I think it would be good if we could introduce the ability for 306 00:49:12.530 --> 00:49:17.280 MTS - AV: GAC members to close early warnings if they choose to do so. 307 00:49:17.950 --> 00:49:21.769 MTS - AV: It's important for us as GAC members to have that ability 308 00:49:22.580 --> 00:49:30.739 MTS - AV: But it might also be important for applicants to have the certainty to know formally that the early warning is no longer extant. 309 00:49:31.070 --> 00:49:33.339 MTS - AV: And perhaps we could introduce that. 310 00:49:34.540 --> 00:49:43.400 MTS - AV: Without changing all of the operational frameworks, I don't think it needs to be a big change. But if we could introduce that ability, it would be helpful. Thank you. 311 00:49:47.180 --> 00:50:03.960 MTS - AV: Thank you. I'm not going to put you on the spot, but of course, Marika, if ICANN has themselves any useful input on what might be possible, you're more than welcome. Meanwhile, my queue is… 312 00:50:03.970 --> 00:50:10.639 MTS - AV: Switzerland, Jorge, and then I think from China, so Jorge, and please keep it slightly short. 313 00:50:11.490 --> 00:50:22.010 MTS - AV: Thank you, Marco. So before I go back to what I raised before, I would like to support what Paul just mentioned. 314 00:50:22.120 --> 00:50:31.559 MTS - AV: I think that's a good idea. And on the point I made, yeah, before. 315 00:50:31.940 --> 00:50:39.439 MTS - AV: issuing a CAC early warning, even if it's from an individual member or from a number of members. 316 00:50:39.440 --> 00:50:52.920 MTS - AV: There might be, the, the need to, to seek clarifications or more information about the application, to have, an informal exchange with the applicant. 317 00:50:52.920 --> 00:51:07.500 MTS - AV: from the member state or the member states or the observers concerned. So I would suggest and I hope Benedetta takes note of this that we have some 318 00:51:07.630 --> 00:51:16.850 MTS - AV: Communicate language or something in that sense that states that we would like to have 319 00:51:17.150 --> 00:51:23.699 MTS - AV: a means of communication between interested GAC, 320 00:51:23.710 --> 00:51:37.359 MTS - AV: Community members with the respective applicants in order to seek clarifications or place questions about the application. 321 00:51:37.480 --> 00:51:47.710 MTS - AV: in order to consider issuing or not NGAC early warning. Of course, some members 322 00:51:47.710 --> 00:52:11.740 MTS - AV: might always find their way to find the right communication channel with the applicant, but it would be good, I think, to have this opportunity equally available for all GAC community members without considering their resources and their knowledge of the ICANN system. 323 00:52:11.830 --> 00:52:12.660 MTS - AV: Thank you. 324 00:52:14.180 --> 00:52:29.969 MTS - AV: Thank you, Switzerland. And of course, with the disclaimer that the EGB is what it is. Yeah, I'm again happy to hear, see any ideas within the existing framework. What can we. 325 00:52:30.790 --> 00:52:35.349 MTS - AV: Do, meanwhile then maybe Feng, China? 326 00:52:35.800 --> 00:52:38.279 MTS - AV: Hope you have the solution for us. 327 00:52:38.810 --> 00:52:49.749 MTS - AV: Thank you, Marco. Actually, I'd like to briefly comment on this round of applications. So, Guofeng from China, for the record. 328 00:52:50.050 --> 00:52:58.639 MTS - AV: So at this critical juncture, I'd like to share some preliminary considerations. 329 00:52:59.110 --> 00:53:08.129 MTS - AV: So as previous speakers pointed out, top-level domain strings may carry multiple semantic meanings. 330 00:53:08.260 --> 00:53:16.100 MTS - AV: Subjected to different linguistic and cultural contexts, they are prone to varied interpretations. 331 00:53:16.220 --> 00:53:25.619 MTS - AV: So inevitably, some strings may trigger controversies and even create potential risks to public interest. 332 00:53:26.060 --> 00:53:33.360 MTS - AV: Over the past week, we have received continuous feedback from Chinese Internet community and stakeholders. 333 00:53:33.540 --> 00:53:43.330 MTS - AV: The community had, has raised some concerns over certain strings, holding that these strings entail potential public policy risks. 334 00:53:43.620 --> 00:54:00.409 MTS - AV: Which may raise issues related to public interest, linguistic culture, and social governance. So, at this, current stage, we still keep collecting comments, proposals, and evidence from Chinese community and stakeholders. 335 00:54:00.410 --> 00:54:08.430 MTS - AV: And conduct assessment of the public policy implications raised by certain application. 336 00:54:08.430 --> 00:54:22.609 MTS - AV: So going forward, we may engage with relevant applicants as appropriate based on assessment progress to clarify concerns and explore feasible risk mitigation measures. 337 00:54:22.610 --> 00:54:30.339 MTS - AV: And later on, we may also use CAIC early warning and other tools to express our views. 338 00:54:30.430 --> 00:54:48.169 MTS - AV: China will maintain close communication and exchange with ICANN and GAC members to jointly safeguard the public interest of the Internet. We will also continue to listen to the opinion of the community and engage in friendly consultation with all parties. Thank you very much. 339 00:54:50.200 --> 00:54:53.019 MTS - AV: And thank you, China. 340 00:54:53.220 --> 00:55:00.829 MTS - AV: Very much appreciate, you're standing here, and of course, we're in this together, the community, the applicants. 341 00:55:00.830 --> 00:55:18.830 MTS - AV: us as CAC members, and then let's try and keep, keep to, find each other. Looking at my clock, we're, we're running out of time, but, again, we can pick up tomorrow morning, especially where it regards to lessons learned, looking back. 342 00:55:18.830 --> 00:55:26.010 MTS - AV: Looking forward, and of course, there's room for more discussion on Tuesday. Marika, you have the final comment then? 343 00:55:26.010 --> 00:55:50.190 MTS - AV: Yes, maybe just to one reminder, this, of course, changes may occur to the strings as a result of the string replacement period. And I think you're all aware, but String Confirmation Day marks kind of the final set of strings that are proceeding. And that, of course, then marks as well the start of the community input processes that are available to flag issues or concerns, including a GAC early warning. 344 00:55:50.310 --> 00:56:07.859 MTS - AV: Just to note, and I think the team is discussing a little bit on the background, we heard the question on, is there a way to mark GAC early warning complete? Maybe that is something that, you know, the GAC team can look at as you post those on, I think, your website or wiki page, you know, to kind of add resolved or addressed. 345 00:56:07.860 --> 00:56:17.060 MTS - AV: But I think at least on our side, we don't have a mechanism currently to kind of change the flag because GAC early warning was received. So we do mark that. 346 00:56:17.060 --> 00:56:24.990 MTS - AV: But maybe linking back to the Wiki page, which is potentially an easy path to mark where a resolution has taken place or 347 00:56:25.040 --> 00:56:33.849 MTS - AV: Concerns have been addressed, but we're actively talking to colleagues here to see what, if anything, is possible, and I'm sure they'll come back to that as well. Thank you. 348 00:56:34.810 --> 00:56:45.480 MTS - AV: Thank you for, coming along. Benedetta, you have any, anything from your side? Then I guess then, with your comments heard, we'll, 349 00:56:45.820 --> 00:56:52.019 MTS - AV: Take those back. We'll come back to some of these points later this week. I'm… 350 00:56:52.020 --> 00:57:16.700 MTS - AV: I'm afraid not everything will be resolved this week, but also, and I think important, Marika, as you just said, not everything's set in stone yet. So especially when it comes to particular individual strings, we might also want to wait a bit and see what string confirmation brings. Notwithstanding, of course, we can have a preliminary discussion weekend. 351 00:57:16.700 --> 00:57:22.530 MTS - AV: Like, especially, broader issues that we as CAC might… 352 00:57:22.610 --> 00:57:40.999 MTS - AV: identify. With that, we're on top of the hour, so I'm about to let you go for coffee, not before I announce the next session, which will start in half an hour, in which we will be talking about universal acceptance. 353 00:57:41.030 --> 00:57:53.100 MTS - AV: So another take on inclusivity and broadening the reach of the DNS and broadening the reach of Internet. So please be back for that session at 4:30. Enjoy your coffee.