WEBVTT

1
00:00:02.360 --> 00:00:10.290
MTS - AV: Thank you very much. And before we start, let me hand over to my colleague Fernanda to read the script, please.

2
00:00:18.390 --> 00:00:27.480
MTS - AV: Hello, and welcome to the How It Works IROS and IANA session. My name is Fernanda Younes, and I am Participation Manager for the session.

3
00:00:27.750 --> 00:00:39.629
MTS - AV: Please note that this session is being recorded and is governed by the ICANN Community Participant Code of Conduct, the ICANN Expected Standards of Behavior, and the ICANN Community Anti-Harassment Policy.

4
00:00:39.760 --> 00:00:48.540
MTS - AV: Please observe the following guidelines to participate in the session. I'll also post them in the chat for your reference, or Siranush actually will be posting them in the chat.

5
00:00:49.150 --> 00:00:54.830
MTS - AV: During the session, questions will only be read aloud if submitted within the Q&A pod.

6
00:00:55.500 --> 00:01:09.809
MTS - AV: Interpretation for the session is available in English, French, and Indonesian. 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.

7
00:01:10.230 --> 00:01:21.599
MTS - AV: On-site participants will use a physical microphone to speak. 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.

8
00:01:21.650 --> 00:01:31.410
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. And with that, I'll hand it back to Siranush.

9
00:01:31.610 --> 00:01:39.060
MTS - AV: Thank you, Fernanda. Thank you, everyone, and welcome to one of the most important sessions.

10
00:01:39.310 --> 00:01:59.049
MTS - AV: As you may know, ICANN has two directions, two pillars, so technical and policy. And we will be covering both sessions, both topics during today. But now at this session, we will speak about how ICANN works from technical point of view.

11
00:01:59.050 --> 00:02:09.610
MTS - AV: Recently, I came across through the metaphor internet oxygen. So we compare internet to the air. We don't.

12
00:02:10.580 --> 00:02:11.740
MTS - AV: seed

13
00:02:12.000 --> 00:02:26.019
MTS - AV: When air is there, don't, like, notice, but when it's not there, we definitely notice that something is wrong, correct? The same with the internet. We're taking it for granted, but.

14
00:02:26.020 --> 00:02:36.889
MTS - AV: There are so much work behind it, so internet, it's like an air for us when it's there. So when internet is shut down.

15
00:02:37.110 --> 00:02:38.590
MTS - AV: We all feel like.

16
00:02:38.970 --> 00:02:41.110
MTS - AV: very stressed.

17
00:02:41.290 --> 00:02:59.019
MTS - AV: So and it's my real pleasure to introduce the people who are behind of that technical aspect, how internet works in ICANN and I would like to introduce John Crane and Kim Davis.

18
00:02:59.020 --> 00:03:14.350
MTS - AV: Who will be our panelists and presenters, and you will learn about IROS and IANA, those two new acronyms for you, what does it mean, and what stands behind of this. John, the floor is yours.

19
00:03:15.290 --> 00:03:21.779
MTS - AV: Thank you, Siranesh. Firstly, how many people is this their first ICANN meeting?

20
00:03:22.660 --> 00:03:23.720
MTS - AV: I'm lying.

21
00:03:24.560 --> 00:03:30.429
MTS - AV: Okay, so quite a few people, so… Welcome to the family, welcome to ICANN.

22
00:03:32.170 --> 00:03:33.810
MTS - AV: I'm gonna start with some advice.

23
00:03:34.440 --> 00:03:35.610
MTS - AV: Relax.

24
00:03:35.890 --> 00:03:37.419
MTS - AV: Enjoy yourself.

25
00:03:37.950 --> 00:03:39.800
MTS - AV: Get to meet people.

26
00:03:40.840 --> 00:03:43.629
MTS - AV: Don't get worried about…

27
00:03:43.760 --> 00:03:53.379
MTS - AV: The depth of technology, if you're not a technologist, and don't get worried about the policy complications if you're not a policy person.

28
00:03:53.680 --> 00:03:58.190
MTS - AV: This is a mixture of both, if you're a deep tech person.

29
00:03:59.140 --> 00:04:01.540
MTS - AV: You're probably in the wrong place.

30
00:04:02.090 --> 00:04:08.749
MTS - AV: ICANN is not super deep technology when we have these meetings. It's about technology and policy.

31
00:04:08.960 --> 00:04:20.289
MTS - AV: But you're gonna meet a lot of really interesting technologists who do attend ICANN meetings, and you will learn about the importance of policy.

32
00:04:20.510 --> 00:04:22.180
MTS - AV: for technology.

33
00:04:22.450 --> 00:04:29.510
MTS - AV: And if you're the policy people, you're going to learn about the importance of understanding the technology if you're going to

34
00:04:29.770 --> 00:04:33.710
MTS - AV: Set policies, or make policies, so it's a really good…

35
00:04:33.880 --> 00:04:37.750
MTS - AV: Mix. This is where those two worlds really meet.

36
00:04:37.930 --> 00:04:43.380
MTS - AV: So I'm John Crane. I am ICANN's Chief Technology Officer.

37
00:04:43.570 --> 00:04:49.159
MTS - AV: I've been at ICANN for about years. It's been a long while.

38
00:04:50.690 --> 00:05:00.800
MTS - AV: two different ways of counting it. One from when I started working at ICANN, and one from when they employed me, which was a couple of years or a year or so later.

39
00:05:00.830 --> 00:05:11.070
MTS - AV: that's a discussion over a coffee or a beer at some point, but quarter of a… quarter of a cent… of a century, basically, working at ICANN. I've been here for a while.

40
00:05:11.170 --> 00:05:23.699
MTS - AV: So these are actually relatively old slide set because we don't really use the term IROS anymore, but it was an acronym that we made up to describe what we do.

41
00:05:24.190 --> 00:05:35.279
MTS - AV: One of the things you're going to find here at the ICANN, which is of course itself an initialization of something, is we love these acronyms and initializations.

42
00:05:35.560 --> 00:05:39.089
MTS - AV: You will hear hundreds of them.

43
00:05:39.240 --> 00:05:40.400
MTS - AV: This week.

44
00:05:40.970 --> 00:05:46.740
MTS - AV: There is a page, and I'm sure you've probably been sent a link to it, where they're all laid out.

45
00:05:47.150 --> 00:05:52.880
MTS - AV: If somebody uses one and they don't explain it, including myself in this presentation.

46
00:05:53.830 --> 00:05:57.580
MTS - AV: Just ask them politely, call them out, say, could you explain that to me?

47
00:05:57.740 --> 00:06:06.170
MTS - AV: I do not know all of the acronyms. There are so many, and sometimes we use the same acronym for two different things.

48
00:06:06.930 --> 00:06:08.579
MTS - AV: It's like we ran out of…

49
00:06:08.970 --> 00:06:12.530
MTS - AV: Arabic letters or something, it's very strange.

50
00:06:12.650 --> 00:06:21.370
MTS - AV: So the Office of the Chief Technology Officer, that's basically a fancy way of saying the people who at some level work for me.

51
00:06:21.580 --> 00:06:29.560
MTS - AV: Are all people that are responsible for, basically delivering technology.

52
00:06:29.940 --> 00:06:41.350
MTS - AV: understanding of technology, for doing research about technology and for explaining technology to the community and the world.

53
00:06:41.850 --> 00:06:47.210
MTS - AV: And it's made up, basically, of about 5 different functions that all have

54
00:06:47.320 --> 00:06:51.760
MTS - AV: unique characteristics and things they do.

55
00:06:52.300 --> 00:07:06.669
MTS - AV: Sitting here to my right is Kim Davis. He works in a function that's called IANA that's part of an organization called PTI. And I'll let him tell you what that means, because he's going to have his own presentation.

56
00:07:07.810 --> 00:07:11.490
MTS - AV: The IANA, the Internet Assigned Numbers Authority.

57
00:07:12.120 --> 00:07:14.539
MTS - AV: is the reason that ICANN exists.

58
00:07:15.840 --> 00:07:19.550
MTS - AV: If you go back, 30 years.

59
00:07:20.350 --> 00:07:24.780
MTS - AV: into the days when we talked about the need for a global body.

60
00:07:24.940 --> 00:07:28.910
MTS - AV: for coordination of the Internet's unique identifiers.

61
00:07:29.060 --> 00:07:34.200
MTS - AV: Something we called NUCO back then in the late 90s.

62
00:07:34.550 --> 00:07:39.749
MTS - AV: It was all about housing the functions of the Internet Assigned Number Authority.

63
00:07:40.080 --> 00:07:46.970
MTS - AV: And that's… You know, as a technologist, and in my mind, is still one of the most critical things.

64
00:07:47.150 --> 00:07:48.820
MTS - AV: That ICANN does.

65
00:07:49.490 --> 00:07:52.929
MTS - AV: And you probably won't hear a lot about it.

66
00:07:53.810 --> 00:07:59.799
MTS - AV: Because it's not necessarily the most exciting thing, unless you're a geek like myself.

67
00:08:01.150 --> 00:08:13.340
MTS - AV: So, I'm gonna hand over… I'm gonna go about halfway through, and then I'm gonna hand over to Kim, and he'll talk about what the IANA does, which is the area that he leads. So… Let's see where these slides go.

68
00:08:14.330 --> 00:08:17.529
MTS - AV: And it didn't move it. Yes, it did. Oh, I went too.

69
00:08:18.440 --> 00:08:26.140
MTS - AV: So Yeah, this is… Basically, how we talk about them, the IANAs

70
00:08:26.350 --> 00:08:29.310
MTS - AV: A little different, because it has its own

71
00:08:29.560 --> 00:08:35.939
MTS - AV: sub-organization called PTI, its own board, etc. But these all reports up to me, and then there's the…

72
00:08:36.600 --> 00:08:38.370
MTS - AV: Technology functions…

73
00:08:38.909 --> 00:08:46.110
MTS - AV: I'm gonna add one to here, that's because these are slightly out-of-date slides. We have a group we call Business Operations.

74
00:08:46.500 --> 00:08:56.660
MTS - AV: So, I have about… Depending on how you count and what day it is, About 120… Staff.

75
00:08:56.900 --> 00:09:01.980
MTS - AV: Reporting up to me through various technical areas of the organization.

76
00:09:02.140 --> 00:09:06.879
MTS - AV: We manage a budget, in the millions of dollars.

77
00:09:07.260 --> 00:09:13.880
MTS - AV: We have… Tens and tens of projects.

78
00:09:14.200 --> 00:09:16.540
MTS - AV: That we have ongoing. We have…

79
00:09:18.040 --> 00:09:20.290
MTS - AV: I keep picking something up in the microphone, I think.

80
00:09:20.540 --> 00:09:26.050
MTS - AV: So… so we… to manage that, we actually have our own little internal business operations group.

81
00:09:26.440 --> 00:09:31.270
MTS - AV: So, you know, when you run something like a business, you have people that do…

82
00:09:32.330 --> 00:09:41.060
MTS - AV: contracting, and budgets, and project management, and all that kind of stuff. That's those guys. We have the technical engagement folks.

83
00:09:41.470 --> 00:09:45.470
MTS - AV: You'll see a lot of engagement happening from ICANN.

84
00:09:45.810 --> 00:09:48.730
MTS - AV: We have 3 engagement groups.

85
00:09:49.290 --> 00:09:57.930
MTS - AV: by actual individual groups inside ICANN whose role it is to communicate with the world and to engage in two-way dialogue.

86
00:09:58.300 --> 00:10:00.390
MTS - AV: We have a government engagement group.

87
00:10:00.890 --> 00:10:03.020
MTS - AV: Self-explanatory, I think.

88
00:10:03.160 --> 00:10:07.240
MTS - AV: We have a global stakeholders group, which is very generic.

89
00:10:07.620 --> 00:10:10.660
MTS - AV: And then we have a technical engagement group.

90
00:10:10.830 --> 00:10:18.290
MTS - AV: And there's a couple of folks from this region in the technical engagement group, and they're looking at me as though I'm going to ask them to stand up and wave.

91
00:10:18.770 --> 00:10:21.620
MTS - AV: If you insist, Chan Pika, Mei Chan, if…

92
00:10:22.610 --> 00:10:30.320
MTS - AV: So, both based here in region, we have people around the regions, but those are folks who go out and do things like

93
00:10:30.590 --> 00:10:33.600
MTS - AV: Trained on technical issues.

94
00:10:33.800 --> 00:10:36.690
MTS - AV: DNS ECO, or many other things.

95
00:10:36.960 --> 00:10:39.910
MTS - AV: We have a couple of research groups.

96
00:10:40.290 --> 00:10:47.600
MTS - AV: folks who are researching things about the identifier system. I'm going to go a little bit more detail to some of these as I go through.

97
00:10:48.600 --> 00:10:54.270
MTS - AV: Basically in two groups, one that really focuses on…

98
00:10:55.360 --> 00:11:02.599
MTS - AV: protocols and parameters, working with the IETF, etc, and one that is very much focused on how

99
00:11:02.990 --> 00:11:05.080
MTS - AV: identifiers are used.

100
00:11:05.930 --> 00:11:09.159
MTS - AV: So you'll notice I use the term identifiers.

101
00:11:10.130 --> 00:11:15.959
MTS - AV: You probably all thought you were at a DNS conference, domain name system.

102
00:11:16.290 --> 00:11:24.800
MTS - AV: Domain names are identifiers, but ICANN does so much more in the identifier space, and you'll see more about that when Kim gets on.

103
00:11:25.240 --> 00:11:27.649
MTS - AV: microphone. So…

104
00:11:28.330 --> 00:11:38.100
MTS - AV: We do research about how those identifiers are used and misused. You will hear a lot of talk this week about something called DNS, Domain Name System Abuse.

105
00:11:38.430 --> 00:11:42.489
MTS - AV: Some of you have probably studied this. Some of you are probably studying this.

106
00:11:43.120 --> 00:11:50.939
MTS - AV: It's a term that's sort of made up for the ICANN world and the ICANN Policy Forum. It doesn't really exist outside this world.

107
00:11:51.340 --> 00:12:00.389
MTS - AV: Many of these terms… originated within the ICANN world, even the term SSR, Security Stability Resilience.

108
00:12:00.710 --> 00:12:03.479
MTS - AV: came initially out of the ICANN world.

109
00:12:03.700 --> 00:12:08.909
MTS - AV: So, a lot of studies around what's happening there, and some of those stuff are also…

110
00:12:09.010 --> 00:12:12.189
MTS - AV: going to be here, or are here at the ICANN meeting.

111
00:12:13.350 --> 00:12:17.010
MTS - AV: Staff, you've probably been told this. We all have ICANN Org.

112
00:12:17.690 --> 00:12:19.619
MTS - AV: We're paid to be friendly.

113
00:12:19.870 --> 00:12:27.460
MTS - AV: We have to be nice to you, so you can come and talk to us whether we want to or not, and we will be nice to you, I promise.

114
00:12:27.760 --> 00:12:32.980
MTS - AV: And if anybody's not nice to you, you tell Chanpika, and… He will tell them off.

115
00:12:34.250 --> 00:12:40.889
MTS - AV: No, don't go to the Ombuds. That's a lot of paperwork. Love the Ombuds, but it's a lot of paperwork if you do that.

116
00:12:44.250 --> 00:12:57.599
MTS - AV: So let's talk about a couple of those groups. I'm going to kind of flip through these slides because I don't want to do death by PowerPoint. I actually want to get to where you get to ask us questions because frankly, that's more interesting.

117
00:12:59.590 --> 00:13:05.760
MTS - AV: So, I talked about these in the large… this is where Champica and Major are from.

118
00:13:06.160 --> 00:13:15.140
MTS - AV: Basically, promoting best practices. We have… Some programs is… Anybody heard of kindness?

119
00:13:15.300 --> 00:13:16.580
MTS - AV: As a program.

120
00:13:18.020 --> 00:13:22.449
MTS - AV: couple of people. Anybody heard of manners as a program.

121
00:13:22.660 --> 00:13:26.689
MTS - AV: So that's… that's not one of our programs, that came out of something called

122
00:13:26.810 --> 00:13:44.249
MTS - AV: ISOC, the Internet Society, and that was about advancing norms and best practices, if you like, for the routing world, the way we use IP addresses. And it occurred to us that it'd be good to do something very similar for the DNS world.

123
00:13:44.410 --> 00:13:46.340
MTS - AV: So, because…

124
00:13:47.030 --> 00:13:54.750
MTS - AV: we're either very original or not very original. We thought to go with manners, it would be good if you also had kindness. So…

125
00:13:55.150 --> 00:13:59.679
MTS - AV: Knowledge is… and sharing and initiating norms for the DNS.

126
00:14:00.290 --> 00:14:09.970
MTS - AV: spells kindness. I mean, we even have t-shirts, so I don't know if we have any here. But we thought it was clever. But that's a… that's run by this group here.

127
00:14:10.660 --> 00:14:12.279
MTS - AV: And they do a lot.

128
00:14:12.430 --> 00:14:13.560
MTS - AV: of training.

129
00:14:14.250 --> 00:14:18.810
MTS - AV: So we have people on every continent apart from Antarctica.

130
00:14:19.340 --> 00:14:27.250
MTS - AV: that are dedicated to this. They are extremely busy people. You would be amazed, or maybe not.

131
00:14:27.480 --> 00:14:37.139
MTS - AV: How many people… likes to be trained about these obscure technologies that are actually important, like DNSSEC.

132
00:14:37.530 --> 00:14:43.080
MTS - AV: Especially when it's paid for by somebody else. So we do these for free.

133
00:14:43.480 --> 00:14:52.989
MTS - AV: Because we want to get that knowledge out there, so we can get into places and talk to people who may not normally have the budget to bring in some of these commercial folks.

134
00:14:54.310 --> 00:15:05.919
MTS - AV: So, you know, we've got people on every continent, and they are very busy. We mostly teach in English, that is our business language, but we have people that speak

135
00:15:06.050 --> 00:15:16.160
MTS - AV: other languages. Most people in ICANN, not everybody, but most people are at least dual lingual. I'm not Dutch, but I speak English and Dutch.

136
00:15:16.270 --> 00:15:18.080
MTS - AV: Many people

137
00:15:18.330 --> 00:15:25.530
MTS - AV: in our… in our staff and on our board, etc, speak many other languages, so even if we do the training.

138
00:15:26.120 --> 00:15:27.340
MTS - AV: In English.

139
00:15:27.570 --> 00:15:29.630
MTS - AV: A lot of the time, you'll be able to speak

140
00:15:29.900 --> 00:15:34.020
MTS - AV: In some local language to the people, because they're from the region.

141
00:15:37.430 --> 00:15:39.840
MTS - AV: One of the reasons we do this.

142
00:15:42.580 --> 00:15:43.930
MTS - AV: is technical.

143
00:15:44.410 --> 00:15:47.589
MTS - AV: Right? Let's have people running the DNS

144
00:15:48.380 --> 00:15:52.749
MTS - AV: In standardized ways, in ways that meet security.

145
00:15:52.960 --> 00:15:59.689
MTS - AV: needs, etc. But the other reason we do this is to inform policymakers.

146
00:16:00.170 --> 00:16:05.770
MTS - AV: Remember, I said that if you're a policy maker, you need to understand the technology.

147
00:16:06.000 --> 00:16:22.169
MTS - AV: So we don't just do this to technologists. We go out and we also talk to policymakers, governments, and inform them about the technology. Maybe slightly different material, we may be not doing hands-on laboratories like we do with the engineers, but we will be teaching them about these technologies.

148
00:16:27.000 --> 00:16:30.189
MTS - AV: So, as I said, they do many of these.

149
00:16:31.900 --> 00:16:39.029
MTS - AV: These are just some of the topics that they teach on. IDNs, international domain names.

150
00:16:39.200 --> 00:16:48.580
MTS - AV: Obviously, the domain name system in general, you know, kindness is about teaching people how to set up their name service properly, etc.

151
00:16:48.790 --> 00:17:00.150
MTS - AV: DNS security extensions, security best practices for identifier systems, routing… basically wherever we find there's a need that will help support ICANN's mission.

152
00:17:01.130 --> 00:17:06.950
MTS - AV: Remember that ICANN's mission is to ensure a secure and stable identifier system.

153
00:17:07.079 --> 00:17:08.390
MTS - AV: So if people…

154
00:17:08.690 --> 00:17:15.019
MTS - AV: Can't manage their part of the identifier system securely, then obviously it has an effect on the overall system.

155
00:17:15.140 --> 00:17:27.949
MTS - AV: That doesn't mean that it is our role to go and teach everybody on the planet how to configure a router or a DNS server. But we try and reach out, you know, we'll do things like we'll work with universities to build

156
00:17:28.270 --> 00:17:29.530
MTS - AV: their curriculum.

157
00:17:29.670 --> 00:17:32.310
MTS - AV: So we're trying to push knowledge.

158
00:17:38.000 --> 00:17:42.470
MTS - AV: These are… That's an outdated slide.

159
00:17:43.960 --> 00:17:45.040
MTS - AV: I'm sorry.

160
00:17:45.880 --> 00:17:47.220
MTS - AV: Oh, she's not even looking.

161
00:17:48.010 --> 00:17:51.090
MTS - AV: May Chan is not on that slide, so that's an outdated slide.

162
00:17:51.290 --> 00:17:55.130
MTS - AV: I should have looked at these before I came. These are just people out there.

163
00:17:55.580 --> 00:17:59.310
MTS - AV: Giving lots of talks about stuff.

164
00:17:59.860 --> 00:18:05.739
MTS - AV: We've got Nico on the top left there. He's down in Latin America.

165
00:18:06.040 --> 00:18:09.000
MTS - AV: based in Uruguay.

166
00:18:09.430 --> 00:18:15.289
MTS - AV: Montevideo. We've got Aldish, who's Based in Sweden.

167
00:18:15.760 --> 00:18:24.200
MTS - AV: He's actually German, but he's based in Sweden. And then we've got David Huberman there, who's North America, which is, you know, USA, Canada.

168
00:18:26.040 --> 00:18:29.449
MTS - AV: parts of Mexico also. They're just out there giving training.

169
00:18:30.530 --> 00:18:33.650
MTS - AV: They're very, very busy people.

170
00:18:35.370 --> 00:18:36.550
MTS - AV: Research.

171
00:18:39.950 --> 00:18:45.369
MTS - AV: So, how many of you have been to an Internet Engineering Task Force, or an ITF?

172
00:18:46.810 --> 00:18:53.670
MTS - AV: I asked a few of you. I mean, considering you, you know the group that it is. That's Good.

173
00:18:53.780 --> 00:19:02.379
MTS - AV: You know, because I sit in conferences and things, and I teach, and people have never heard of them. So we send a lot of our staff

174
00:19:02.650 --> 00:19:05.910
MTS - AV: to the IETF to help with protocols.

175
00:19:06.190 --> 00:19:16.289
MTS - AV: So, this group… Really engages with the DNS and the identifier technologies communities, very active in the IETF.

176
00:19:16.950 --> 00:19:18.819
MTS - AV: If you read some of the DNS,

177
00:19:19.760 --> 00:19:29.869
MTS - AV: RFCs, the request for comments documents, you will find that they've been written by ICANN staff, either before they became ICANN staff, or while they're ICANN staff.

178
00:19:30.120 --> 00:19:40.949
MTS - AV: So… you know, very, very active there. ITF, like ICANN, happens 3 times a year around the world.

179
00:19:41.320 --> 00:19:50.549
MTS - AV: You can join pretty much everything remotely. In fact, the ITF is interesting in that it doesn't make decisions at the meetings.

180
00:19:50.990 --> 00:19:52.660
MTS - AV: It's a rule they have.

181
00:19:52.850 --> 00:20:12.590
MTS - AV: It's like, it has to be made in the mailing list with the groups, so that the people that can't get to the meetings can make the meet… can actually make the decisions. So we facilitate in those, we actually write protocols, we work on Ensuring that protocols can be implemented. Generally, we don't write code ourselves.

182
00:20:12.710 --> 00:20:19.969
MTS - AV: But we may, for example, fund code. We may go to one of the DNS resolver

183
00:20:20.250 --> 00:20:25.990
MTS - AV: manufacturers, that they're mainly open source, and say, hey, there's a new RFC coming.

184
00:20:26.590 --> 00:20:29.259
MTS - AV: Is this on your implementation timeline?

185
00:20:29.370 --> 00:20:34.679
MTS - AV: And they may say, well, not really. And we might say, well, we think this one's important for our mission.

186
00:20:35.470 --> 00:20:41.030
MTS - AV: Can we help you fund it? Can we do other things to get it raised on your priority list? So…

187
00:20:41.330 --> 00:20:42.699
MTS - AV: Very busy.

188
00:20:43.250 --> 00:20:50.590
MTS - AV: We do a lot of studies. Has anybody heard or read any of the Okto documents, Office of the CTO documents from ICANN?

189
00:20:51.280 --> 00:20:58.880
MTS - AV: So… These guys, they have a lot of engineering background, they write a lot of those documents, so…

190
00:20:59.100 --> 00:21:00.210
MTS - AV: They vary.

191
00:21:00.520 --> 00:21:05.719
MTS - AV: I think the strangest one is on election mechanics, and

192
00:21:05.880 --> 00:21:09.009
MTS - AV: Randomization, how you do proper randomization.

193
00:21:09.200 --> 00:21:17.090
MTS - AV: It's a little odd, but we actually do have elections and things that I can, and understanding how you do randomization properly.

194
00:21:17.800 --> 00:21:31.259
MTS - AV: thought it'd be interesting to document that, so we wrote a document on it. Post-quantum cryptography, where it affects the identifier systems, mainly the DNS and DNSSEC.

195
00:21:31.570 --> 00:21:40.199
MTS - AV: It runs the gamut. There is. There are a lot of documents in there. I do recommend, if you're interested in how some of the technology works to go read them.

196
00:21:40.320 --> 00:21:48.630
MTS - AV: We really try very hard to use plain language and make them accessible to non-engineers.

197
00:21:49.720 --> 00:21:51.300
MTS - AV: Bit hard to do with.

198
00:21:51.760 --> 00:21:57.309
MTS - AV: post-quantum cryptography, there's a lot of really long words in there. It's not easy to make hits.

199
00:21:57.800 --> 00:22:03.199
MTS - AV: manageable and digestible by people who aren't following it, but that is what we attempt to do.

200
00:22:04.700 --> 00:22:07.190
MTS - AV: And of course, We,

201
00:22:07.850 --> 00:22:12.739
MTS - AV: represent ICANN as we go around. There is something called the Root Service System Advisory Committee.

202
00:22:13.660 --> 00:22:16.869
MTS - AV: ICANN manages one of the 13 root servers.

203
00:22:17.040 --> 00:22:20.419
MTS - AV: So that also comes under the office of the CTO.

204
00:22:20.830 --> 00:22:24.230
MTS - AV: It's managed by a group that we don't mention here. It's a little group.

205
00:22:24.350 --> 00:22:30.709
MTS - AV: It's actually one of the biggest groups in ICANN, which is our engineering and information technology group that also reports to me.

206
00:22:30.820 --> 00:22:34.219
MTS - AV: They manage the deployment of the root server.

207
00:22:34.360 --> 00:22:40.580
MTS - AV: And this group, the sort of research guys, actually manage much of the strategy. We do it together.

208
00:22:40.750 --> 00:22:45.510
MTS - AV: But because they are such DNS protocol geeks, they give a lot of the input.

209
00:22:49.400 --> 00:22:57.250
MTS - AV: So this is just a list of some of these. We'll share the slides. I'm not going to go through all of these different things. DNS error…

210
00:22:57.590 --> 00:23:07.359
MTS - AV: reporting was one of those things where we actually developed the protocol in the IETF and published it. It was… we noticed something that was missing in the technology stack.

211
00:23:07.580 --> 00:23:13.130
MTS - AV: And the way you fix that is you go into the Internet Engineering Task Force, and you work with

212
00:23:13.350 --> 00:23:23.909
MTS - AV: what they call the working groups, to write a request for comments and to get that to become the standard. So it's standards development, basically. ICANN does not develop those technical standards.

213
00:23:24.280 --> 00:23:26.780
MTS - AV: The Internet Engineering Task Force does that.

214
00:23:27.740 --> 00:23:32.510
MTS - AV: I think you'll probably cover the IETF a little bit in your slides, at least on…

215
00:23:34.260 --> 00:23:40.210
MTS - AV: And, you know, I'll just leave those up for a second. So this is the other area of research I talked about.

216
00:23:42.210 --> 00:23:50.679
MTS - AV: you know. Obviously, wow! Those are small letters support supporting the security, stability, and resiliency of the identifiers.

217
00:23:51.750 --> 00:23:56.280
MTS - AV: That's what ICANN does, that's what our mission is. So, basically.

218
00:23:56.580 --> 00:23:58.190
MTS - AV: You break this down to.

219
00:23:59.220 --> 00:24:04.570
MTS - AV: two areas. One is understanding what is happening in the ecosystem.

220
00:24:04.870 --> 00:24:12.059
MTS - AV: So we developed a system to measure the reports of DNS abuse.

221
00:24:13.270 --> 00:24:17.390
MTS - AV: Note. I didn't say we're measuring DNS abuse.

222
00:24:17.780 --> 00:24:21.000
MTS - AV: We're measuring the reports of DNS abuse.

223
00:24:21.180 --> 00:24:23.399
MTS - AV: So there wasn't a system

224
00:24:23.830 --> 00:24:34.769
MTS - AV: to go in and find a domain name, and to pull together all the evidence, and to say this is 1 or 0, it is or it is not DNS abuse.

225
00:24:35.060 --> 00:24:42.160
MTS - AV: It was to measure what people were saying and the reputation of a specific name out there on the DNS.

226
00:24:42.290 --> 00:24:54.439
MTS - AV: The reason we did this is the other part of that mission, which is to actually understand the state of the art of the science around this, and then to push that science.

227
00:24:54.890 --> 00:24:57.419
MTS - AV: We did that project.

228
00:24:58.260 --> 00:25:04.249
MTS - AV: Oh my God, it must have been… it's definitely more than a decade ago, because we were told you could not measure these things.

229
00:25:04.500 --> 00:25:18.850
MTS - AV: And there's nothing you should ever say to an engineer that is worse than you cannot do something, because we will find a way. So… and it was really about pushing that science and that methodology of how you identify

230
00:25:19.360 --> 00:25:25.279
MTS - AV: Levels of abuse, or reported abuse, and how you could actually set a baseline and then

231
00:25:25.480 --> 00:25:28.789
MTS - AV: As you change policy, hopefully measure the change.

232
00:25:29.190 --> 00:25:40.469
MTS - AV: Unfortunately, with the way the internet goes, it often seems that abuse, not just DNS, all abuse just seems to go up no matter what you do. But you can measure changes. So it was very interesting.

233
00:25:40.730 --> 00:25:50.510
MTS - AV: That is still happening today. We have a tool called Metrica, that has data around what people are saying about domain names.

234
00:25:52.480 --> 00:25:53.910
MTS - AV: measuring…

235
00:25:54.800 --> 00:26:04.679
MTS - AV: every generic name, because we don't measure all the CC names, because we don't… the country code names, because we don't have all the data that is resolving on the internet.

236
00:26:05.040 --> 00:26:06.960
MTS - AV: Is not a small undertaking.

237
00:26:07.620 --> 00:26:15.090
MTS - AV: I wouldn't say it's big data in the way that, like banks and some other people measure things. But it's it's pretty big data. It's

238
00:26:15.260 --> 00:26:29.810
MTS - AV: moderate data, we'll say. It's a lot of names, but we look at every name every day, see what people are reporting about it, measure how long it's been reported as bad. That's a new module we're doing, and we're building new modules.

239
00:26:30.150 --> 00:26:39.420
MTS - AV: every year, do new ways to measure what is happening out there on the internet. But it's not just about the measurements, it's about the science.

240
00:26:39.520 --> 00:26:45.110
MTS - AV: There are other organizations. There's an organization called NetBeacon that does something very similar.

241
00:26:45.180 --> 00:26:53.769
MTS - AV: They are measuring abuse and reports of abuse, and they're actually working with industry. It's not an ICANN body. I happen to be on their advisory board.

242
00:26:53.770 --> 00:27:05.510
MTS - AV: But they used a lot of our science when they first started up, and now they're improving science. So to me, that's a success of the work we do. When other people look at what we do and they go, we can do it better.

243
00:27:06.230 --> 00:27:13.859
MTS - AV: That is fantastic, because our job is to promote improvement of the ecosystem. It's not to run all of these things.

244
00:27:13.970 --> 00:27:17.330
MTS - AV: And once again, a lot of education.

245
00:27:17.680 --> 00:27:25.949
MTS - AV: We do also facilitate discussions around cybersecurity when… When these things affect…

246
00:27:26.610 --> 00:27:32.939
MTS - AV: the domain name system is normally where it gets seen, but also the routing system. We obviously have an interest.

247
00:27:33.260 --> 00:27:43.139
MTS - AV: Things like, botnets. I think everybody may have heard of robotic networks or botnets may use domain names at scale.

248
00:27:43.700 --> 00:27:49.870
MTS - AV: And how they do this is of interest to us, and we will often work when there are cases to help

249
00:27:50.250 --> 00:27:54.210
MTS - AV: people out there, law enforcement, researchers.

250
00:27:54.420 --> 00:27:58.539
MTS - AV: understand how the naming systems are actually being abused.

251
00:27:58.800 --> 00:28:00.859
MTS - AV: also, so we can understand them.

252
00:28:01.600 --> 00:28:09.579
MTS - AV: So these guys get to have a lot of fun. They're really researching in interesting areas and trying to push the science.

253
00:28:10.370 --> 00:28:12.480
MTS - AV: Awesome. We've also funded

254
00:28:12.600 --> 00:28:29.179
MTS - AV: some projects. So if we see a project that's borderline what we should be doing to our mission. we might go and say, okay, that is actually useful for ICANN. There's a project out there called Infermal that you might hear being talked about. We funded that.

255
00:28:29.320 --> 00:28:38.660
MTS - AV: It's a neutral piece of research. We did not do the research. We, it's… we did actually advise them on some of the technology, because we're the experts.

256
00:28:39.000 --> 00:28:41.119
MTS - AV: and how the DNS works, etc.

257
00:28:41.220 --> 00:28:45.039
MTS - AV: But we funded that, so we do research, we fund research.

258
00:28:47.920 --> 00:28:53.879
MTS - AV: These are just some of the tools. Once again, I'm going to share the slides. I'm not going to go through them, because I'm watching time.

259
00:28:56.150 --> 00:28:58.179
MTS - AV: Where can you find what we're doing?

260
00:29:00.440 --> 00:29:06.320
MTS - AV: ICANN's website, type in Okto, type in… and you will find all kinds of stuff.

261
00:29:06.710 --> 00:29:12.669
MTS - AV: The best thing to do is just go and bug people, go talk to Chan Pika, come talk to me and we can help you find.

262
00:29:12.930 --> 00:29:15.720
MTS - AV: things. It's all on our

263
00:29:15.860 --> 00:29:33.520
MTS - AV: website. You'll see some numbers there, that's just our numbering terminology for the Okto documents. RBL's, classification of unsolicited email threats, that was a piece of science we did a while ago, using machine learning, I guess before it was trendy.

264
00:29:33.640 --> 00:29:39.900
MTS - AV: To go through millions of emails and see if we could classify what kind of threats were in them.

265
00:29:43.610 --> 00:29:44.910
MTS - AV: We have a blog.

266
00:29:46.600 --> 00:29:53.639
MTS - AV: And these are our things, and I am going to hand over to him, and then we can go to things.

267
00:29:56.170 --> 00:29:58.539
MTS - AV: Thanks, John. Good morning, everyone.

268
00:29:59.730 --> 00:30:16.179
MTS - AV: As you heard, I'm head of a team called IANA, the Internet Assigned Numbers Authority, and I hope that over the course of the next little while, you'll have a better understanding of what IANA is, what it does, why it's there, why ICANN was created to be the home of it.

269
00:30:16.290 --> 00:30:18.740
MTS - AV: And many other questions that you might have for us.

270
00:30:22.070 --> 00:30:25.520
MTS - AV: So if we think about IANA fundamentally.

271
00:30:25.630 --> 00:30:32.960
MTS - AV: We're just a group of record keepers. We have lots of different technical records that we keep.

272
00:30:33.330 --> 00:30:37.210
MTS - AV: We administer them according to various policies, but

273
00:30:37.320 --> 00:30:41.479
MTS - AV: I've heard it said derisively that we just maintain a big spreadsheet, and

274
00:30:41.620 --> 00:30:44.060
MTS - AV: Conceptually, that's not too far off.

275
00:30:44.620 --> 00:30:46.430
MTS - AV: Off track,

276
00:30:46.660 --> 00:30:53.079
MTS - AV: But it's a very important spreadsheet. And in fact, without this spreadsheet, the internet as we know it probably wouldn't work.

277
00:30:54.720 --> 00:31:03.279
MTS - AV: It's a spreadsheet that really predates ICANN. The IANA functions themselves really date back to the very first

278
00:31:03.440 --> 00:31:06.690
MTS - AV: experiments of what became the Internet.

279
00:31:06.880 --> 00:31:13.500
MTS - AV: My predecessor in this role, a man by the name of John Postel, was one of the original researchers that,

280
00:31:13.560 --> 00:31:32.290
MTS - AV: helped develop today's internet, and his role in a lot of those early experiments was essentially to be the guy with a notebook taking notes of what experiments happened, how they were conducted, and part of that was keeping records of, like, what device was connected to what device, and so forth. And that was happening

281
00:31:32.330 --> 00:31:38.730
MTS - AV: Like in the early 1970s. And that role has just sort of organically grown ever since then.

282
00:31:40.020 --> 00:31:59.090
MTS - AV: it was really in the 19… actually, this slide is wrong, it says 1988, should be 1998. In the mid-1990s, there was this big boom of what became the internet. It was really in the 1990s where the internet stopped being a research project and started being the commercial…

283
00:31:59.180 --> 00:32:06.029
MTS - AV: international powerhouse that, you know, continues on to this day, and part of a lot of the evolution

284
00:32:06.130 --> 00:32:11.550
MTS - AV: That was happening on the internet at the time was a recognition that

285
00:32:11.980 --> 00:32:28.450
MTS - AV: this person and his notebook and his team probably needed to evolve into something a bit more formalized, a bit more accountable, and a bit more globally established, and that was a lot of the thinking that went into the creation of ICANN. How do we create an organization that can host IANA

286
00:32:28.620 --> 00:32:38.670
MTS - AV: That had all this global accountability, participation from around the world, simply as recognizing the fact the internet has become so much more than a research project by that point.

287
00:32:40.330 --> 00:32:51.969
MTS - AV: Now, what IANA does, the records that we keep are unique identifiers. And as John mentioned, a lot of people coming here to Bali attending this conference.

288
00:32:52.190 --> 00:33:03.469
MTS - AV: your first… the first identifier that comes to mind, and probably the primary reason you're here, is domain names. And domain names are certainly a very key part of the internet identifier landscape.

289
00:33:03.490 --> 00:33:13.739
MTS - AV: It's usually the first thing people reach to when they want to get somewhere on the internet is through a domain name. But it's not the only part of the story. In fact.

290
00:33:14.210 --> 00:33:23.669
MTS - AV: Behind that domain name is many different kinds of identifiers that are required to make the internet fundamentally work.

291
00:33:24.070 --> 00:33:39.400
MTS - AV: These identifiers usually you don't see. If you're just an end user of the internet, you don't see these identifiers, but they're working behind the scenes to make sure that everything you transact and communicate over the internet works in the way that you would expect.

292
00:33:39.510 --> 00:33:48.089
MTS - AV: I'll get to why that function is necessary a bit later in the discussion.

293
00:33:49.450 --> 00:34:06.519
MTS - AV: I lead a team that is responsible for maintaining these records, and we do it in accordance to policies that we don't ourselves set. So, the IANA team itself is operational. We're not a policy body, we're not a rulemaker. We take the rules that have been developed, largely by this community.

294
00:34:06.550 --> 00:34:16.359
MTS - AV: And we operationalize them. We turn the rules into day to day operations so that when someone wants to get a unique identifier, they come to us.

295
00:34:16.590 --> 00:34:24.760
MTS - AV: We review their request against the policy, and then we'll implement it if they're eligible, and we won't if they're not. But that's at the heart of what we do.

296
00:34:29.330 --> 00:34:33.359
MTS - AV: So why do we need an IANA?

297
00:34:34.949 --> 00:34:40.799
MTS - AV: In a sense, the internet works by having everyone connect to this common network.

298
00:34:40.889 --> 00:34:49.589
MTS - AV: around the world where there's no real rule makers. Like, there's no body you have to apply to for permission to connect to the internet.

299
00:34:49.620 --> 00:35:04.559
MTS - AV: Obviously, laws and regulations in any given jurisdiction or country might differ, but generally speaking, the internet is just a general network where there's no center, there's no sanctioning body that says you are allowed to use the internet and you are not.

300
00:35:04.670 --> 00:35:10.589
MTS - AV: It's a global network free from that kind of centralized control or authority.

301
00:35:10.840 --> 00:35:22.990
MTS - AV: But, for that to work, all the devices on the internet have to speak a common language, a common technical language, so that when your device connects to the internet and starts sending transmissions to it.

302
00:35:23.050 --> 00:35:34.510
MTS - AV: the receiving party understands what it's receiving, that it all works together in a standardised way. And that is really kind of at the heart of why IANA is an essential part of the internet.

303
00:35:34.910 --> 00:35:39.719
MTS - AV: If IANA didn't have its comprehensive set of records that said

304
00:35:39.870 --> 00:35:44.890
MTS - AV: This domain has this particular purpose pointing to this particular service or…

305
00:35:44.910 --> 00:36:03.329
MTS - AV: these IP addresses are assigned for this particular network, and all sorts of other manner of identifiers that weren't standardized in a standard way globally, then the internet wouldn't be sort of a plug-and-play experience. Like, you would connect to it, and maybe you had a different

306
00:36:03.420 --> 00:36:07.990
MTS - AV: Kind of internet on your device than the person you're connecting to, and it wouldn't work.

307
00:36:08.170 --> 00:36:13.639
MTS - AV: So having this sort of global function where everyone comes together.

308
00:36:13.780 --> 00:36:23.139
MTS - AV: We globally set the policies, but there is essentially one single source of truth that says these identifiers have these particular purposes and they work a certain way.

309
00:36:23.430 --> 00:36:37.079
MTS - AV: is what makes the internet what it is. It makes the internet a network that people can participate on that works effectively, because there's this sort of common rulebook that everyone follows at a technical level.

310
00:36:37.280 --> 00:36:48.600
MTS - AV: That you will transmit, your communications using IATF standards that John mentioned, but you'll use identifiers that have been registered with the IANA.

311
00:36:48.800 --> 00:36:50.209
MTS - AV: And so the…

312
00:36:50.620 --> 00:36:58.670
MTS - AV: I mentioned domain names. Again, domain names are a bit of an unusual case, because there's so much complexity around them, so much policy, so much rulemaking.

313
00:36:58.710 --> 00:37:10.870
MTS - AV: But the vast majority of identifiers we administer are actually only really relevant to software developers. Software developers are actually the bread and butter of what we do day to day. We work closely with them.

314
00:37:10.950 --> 00:37:27.679
MTS - AV: When, you know, a software developer is creating a new technology on the internet, they'll often work directly with IANA to register the components of their new software or their new technology to make sure it works on the internet. And that is a lot of stuff that happens behind the scenes.

315
00:37:27.720 --> 00:37:41.260
MTS - AV: They'll ultimately develop a product that they'll launch into the world. You might not see the identifiers that sit within it, but they are there to make sure that that particular technology or that particular software works effectively on the internet.

316
00:37:44.940 --> 00:38:03.549
MTS - AV: When we talk about, these identifiers, particularly in the policy space, which is why we're largely here this week, we tend to divide it into three categories. We talk about protocol parameters, which are largely those sort of identifiers that are embedded in software that the end users typically don't see.

317
00:38:03.930 --> 00:38:14.290
MTS - AV: We talk about domain names, and we talk about number resources. So the protocol parameters, our core deliverables there is we manage

318
00:38:14.330 --> 00:38:25.119
MTS - AV: thousands and thousands of registries of these identifiers. Each individual registry can have anywhere between one and something to the magnitude of 100,000 identifiers in it.

319
00:38:25.490 --> 00:38:45.260
MTS - AV: And we essentially manage those according to what the policies stipulate and the technical standards. Software developers in particular will come to us, get allocations, get added to the registries, and importantly, software implementers that implement the new technologies will download our registries. They'll often embed them into software.

320
00:38:45.500 --> 00:39:03.760
MTS - AV: Just one example of a particular kind of identifier we manage is something called port numbers. And so the port number registry has countless entries in it. Software developers will embed that. I'm sure there's a copy of the port number registry in every device here in this room, whether you have a laptop or a phone.

321
00:39:04.040 --> 00:39:10.769
MTS - AV: Somewhere in your operating system is the port number registry, so that your device knows how to connect to different ports on the internet.

322
00:39:11.950 --> 00:39:18.769
MTS - AV: Domain names, our central role when it comes to domain names is administering what's called the root zone.

323
00:39:19.010 --> 00:39:30.979
MTS - AV: The root zone is, the most central piece of the DNS. It is effectively the registry of what is a top-level domain. So we have the official records of what top-level domains exist.

324
00:39:31.090 --> 00:39:42.369
MTS - AV: Along with pointers to where the technical infrastructure is that hosts those top-level domains, and other various technical elements that won't get into too many details here today.

325
00:39:42.680 --> 00:39:56.980
MTS - AV: Another part of administering the root zone is administering the cryptography around it. This is what enables us to validate the contents of the root zone is secure. The cryptographic key for the root zone is called the KSK.

326
00:39:57.210 --> 00:40:15.190
MTS - AV: You might have heard about this in the last week because we actually, for only the second time ever, changed the KSK for the Root Zone on October 11th. So that was a big operational event that took about three years of planning to conduct. It all culminated on Sunday last week.

327
00:40:15.210 --> 00:40:23.970
MTS - AV: And, glad to say, that went off more or less without a hitch, but, that is part of administering the root zone as well, is administering the cryptographic key for it.

328
00:40:24.780 --> 00:40:27.789
MTS - AV: And then number of resources. So number of resources.

329
00:40:28.200 --> 00:40:31.739
MTS - AV: I guess a show of hands, who's heard of an IP address in this room?

330
00:40:32.970 --> 00:40:50.690
MTS - AV: Few people. So the core concept here is that every device connected to the internet needs a unique number associated with it. This is how packets flow over the internet. If my device is talking to your device, how does it know where to send that information?

331
00:40:51.280 --> 00:41:06.679
MTS - AV: Under the covers, each device has this unique number that needs to be used as a source or a destination for transmission. So these IP addresses need to be assigned. Now, people don't come directly to IANA for every IP address because there is…

332
00:41:06.830 --> 00:41:24.149
MTS - AV: 10 billion people in the world, and that would be a lot of work. So, there is a structured hierarchical allocation model. What we do at IANA is we manage the global address space, but we partition it up into mostly regional blocks. So, we'll create a block for the Asia Pacific.

333
00:41:24.290 --> 00:41:28.099
MTS - AV: We'll then hand that block to an organization called APNIC,

334
00:41:28.280 --> 00:41:32.780
MTS - AV: AP NIC is responsible for making assignments within the Asia-Pacific region.

335
00:41:32.880 --> 00:41:50.339
MTS - AV: If a network operator in Indonesia, for example, wanted IP addresses, they would go to APNIC. APNIC would give that network operator a big block of numbers out of the allocation that IANA has given them. They'll subdivide that up for different network providers.

336
00:41:50.450 --> 00:42:08.510
MTS - AV: And then that network provider in turn will allocate individual IP addresses to their customers. So if you're connecting to your ISP at home, for example, you'll just get one IP address, but it's followed that chain from IANA to a regional body to a network operator, and then ultimately to you.

337
00:42:12.180 --> 00:42:14.369
MTS - AV: So who's involved in the IANA functions?

338
00:42:17.330 --> 00:42:18.299
MTS - AV: There we go.

339
00:42:20.390 --> 00:42:38.780
MTS - AV: John mentioned some of the acronyms. I think the key thing I would mention here is there's two bodies that are particularly relevant to IANA. IANA, to be clear, is not a company. IANA is a function, it's a name… it's a name that describes a collective set of services that we provide.

340
00:42:39.050 --> 00:42:52.859
MTS - AV: Now ICANN, as you heard, was created to be the home of IANA, and, you know, essentially it still is. ICANN was created in the 1990s because IANA needed a place to sit that was accountable to the world.

341
00:42:53.030 --> 00:42:59.899
MTS - AV: And so that's why ICANN was created and ICANN's duties still are to be responsible for the IANA functions.

342
00:43:00.320 --> 00:43:02.060
MTS - AV: However,

343
00:43:02.220 --> 00:43:17.780
MTS - AV: Ten years ago this month, there was a big community effort to conduct what's called the IANA stewardship transition. And if you look outside on the pillars in the in the lobby here, you'll see stickers, announcing this fact.

344
00:43:17.900 --> 00:43:29.089
MTS - AV: Essentially, the IANA stewardship transition was a big effort that, you know, I could certainly get into the details on, but in essence, there was a recognition that.

345
00:43:29.350 --> 00:43:34.110
MTS - AV: ICANN had matured to a point where it was finally ready to take on

346
00:43:34.320 --> 00:43:37.419
MTS - AV: Broad responsibility for the IANA functions without.

347
00:43:37.910 --> 00:43:41.880
MTS - AV: oversight above it. For ICANN's first 20 years.

348
00:43:42.020 --> 00:43:59.120
MTS - AV: The US government actually oversaw how ICANN did the functions. But in 2016, that changed. And so a bunch of different restructuring happened to sort of enable this change. And the one that's particularly relevant here is that ICANN actually created a subsidiary called PTI.

349
00:43:59.630 --> 00:44:05.950
MTS - AV: PTI stands for Post-Transition IANA or Public Technical Identifiers.

350
00:44:06.090 --> 00:44:23.640
MTS - AV: And essentially, PTI is a subsidiary organization of ICANN that I lead, that actually does the day-to-day work of running the IANA functions. ICANN still oversees it, but ICANN funds PTI to do the actual work.

351
00:44:23.790 --> 00:44:36.479
MTS - AV: The reason why there's two separate companies is largely to do with an oversight mechanism to make sure that the IANA functions had some legal separation from ICANN so some of the oversight mechanisms can work effectively.

352
00:44:36.660 --> 00:44:48.829
MTS - AV: But, at the end of the day, my team, we sit in ICANN's office, we all have lunch together, we all operate as if we're a department of ICANN, so it's more of a legal distinction than a practical day-to-day distinction.

353
00:44:52.050 --> 00:45:07.220
MTS - AV: And then there's PTI itself, as I mentioned, started in 2016, that actually runs the functions. The IANA staff work for PTI, and then ICANN is the sole member organization that PTI is a part of.

354
00:45:09.730 --> 00:45:23.129
MTS - AV: PTR does have its own board of directors. This is the current composition. John is a director, I'm a director. We have three other directors as well. Two of them are community members, Anupam Anggarwal and Lisa Furr.

355
00:45:23.130 --> 00:45:35.760
MTS - AV: Anupama is actually retiring from his role at the end of this week. He'll be replaced by a new board member. His term is up. And rounding out the board, ICANN CFO, Zavia Calvez, is also on the board.

356
00:45:38.130 --> 00:45:52.499
MTS - AV: And then we have a great team that actually does the work. Some of them will be here this week. Most of them are located in Los Angeles, California. And this is the team that does the day-to-day work of

357
00:45:53.770 --> 00:46:02.330
MTS - AV: receiving the requests from the community, implementing them, and also doing all the support work around that. The technical systems and support that make it work.

358
00:46:02.330 --> 00:46:14.370
MTS - AV: All of our strategic work, our planning, our auditing. Auditing is a very important part of what we do. Since we have such a critical and essential function for the internet, it's important we do our job correctly.

359
00:46:14.470 --> 00:46:28.270
MTS - AV: And so we have lots of checks and balances to make sure that we do the job well. And some of the team that we have, their job is just to check our work, bring in third party auditors, so that they can check our work, facilitate that and so forth.

360
00:46:31.880 --> 00:46:47.960
MTS - AV: Our core work is processing requests, of all the kinds I already mentioned. We have subject matter experts on our team, so a lot of, you know, the very technical things that we do require certain subject matter expertise to assess.

361
00:46:47.960 --> 00:46:57.229
MTS - AV: So that's part of the operations work that we do. We have service level agreements so that the community can monitor our performance.

362
00:46:57.230 --> 00:47:08.079
MTS - AV: It's important that when you ask us for a service, we do it in a timely manner. We do it accurately. So the SLAs are all around timely performance of requests and making sure we do them correctly.

363
00:47:08.740 --> 00:47:21.980
MTS - AV: And then also we have emergency capabilities as well, particularly around the root zone. The internet never sleeps. So for the certain things that we do where we have a critical role to play, we have emergency response available as well.

364
00:47:25.290 --> 00:47:33.849
MTS - AV: We have a technical services team. We do things like software development to make sure our systems do what are needed to support the work that we do.

365
00:47:34.110 --> 00:47:47.939
MTS - AV: product management. We have a cryptographic business operations team. Essentially, their primary function is just managing that one key, the KSK that I mentioned. It is so critical, that key, to

366
00:47:47.940 --> 00:48:03.219
MTS - AV: DNS security, because it is essentially one irreplaceable key that protects the whole DNS. For that reason, there's a lot of effort, time, and operational effort spent on just administering that key.

367
00:48:03.430 --> 00:48:07.099
MTS - AV: As well as monitoring and maintaining our systems.

368
00:48:09.340 --> 00:48:24.470
MTS - AV: I mentioned audits are an important part of what we do. We do an annual external audit where we have, our information security, practices audited. We have risk assessments, we have internal compliance functions.

369
00:48:24.560 --> 00:48:32.440
MTS - AV: We do customer satisfaction surveys. All sorts of functions there are supported by our strategic programs team.

370
00:48:32.760 --> 00:48:42.409
MTS - AV: And I'll, you know, this is a bit of a prelude. I'm going to actually have a much longer session later in the week where I talk a bit more about this, so I won't get too much into the details right now.

371
00:48:45.480 --> 00:48:55.740
MTS - AV: Some common misconceptions about what we do and don't do here. What we do do is create those registries, but we do it based on policies from the community.

372
00:48:55.850 --> 00:49:08.839
MTS - AV: We maintain those registries, we allocate, for example, number of resources. And importantly, we're more or less an open book. Our job is to publish our registries so people can use them. So…

373
00:49:08.860 --> 00:49:21.579
MTS - AV: We're in the business of record keeping, but we're also in the business of just publishing those records. So, we don't charge for service. You don't have to pay IANA to get a copy of our records.

374
00:49:21.610 --> 00:49:27.389
MTS - AV: Everything is published in machine-readable format, so people can just download it and use it as they need to use it.

375
00:49:27.730 --> 00:49:44.900
MTS - AV: What we don't do is we don't create nor interpret policy. We are here to administer the policy that the community has made. When the policies don't exist, or the policies are fundamentally unclear or unimplementable, our job is to go back to the community and say, okay.

376
00:49:44.940 --> 00:49:51.240
MTS - AV: We can't implement this policy. You need to go back and work on it, and then ask the community to rework the policy.

377
00:49:52.740 --> 00:50:10.940
MTS - AV: What we don't do is we don't determine what can be a domain name. As cool as it sounds, I don't get to decide, hey, I'm gonna go create that TLD tomorrow. Yes, we do insert TLDs into our records, that is what makes them real, but we do it following policy, and

378
00:50:10.940 --> 00:50:30.829
MTS - AV: There's this whole application round happening now for new gTLDs. If you're a ccTLD, there's all these rules that govern what can be a ccTLD and on what conditions. So we are not the ones that sit there and go yes or no. We're administering policy that should have more or less made that decision well before it comes to us.

379
00:50:33.810 --> 00:50:42.610
MTS - AV: So I mentioned that later this week I have a bigger session. We're going to be talking much more in depth about what we do at IANA on Wednesday.

380
00:50:42.810 --> 00:50:57.870
MTS - AV: If this little brief preview has given you some interest in this, I invite you to come join us there where we'll go into more detail. I'll also be joined by more of my team there during that session as well.

381
00:50:57.910 --> 00:51:15.469
MTS - AV: And we'll be using that as a moment of reflection. As I mentioned, it's a critical 10-year anniversary of a big change that we had, so we'll talk a little bit more about that. And also, we've done a lot of modernisation work in IANA just in the last 6 months, so we're excited to share some of that work that we've done on Wednesday.

382
00:51:15.530 --> 00:51:20.860
MTS - AV: We invite you to come join us at 10.30am on Wednesday for that session, if you're able.

383
00:51:21.240 --> 00:51:39.590
MTS - AV: But in the meantime, I think that brings me to the end of the slides, but as John mentioned, like, really, we're here to answer questions, so we have another half an hour where we're happy to, dive into the questions that you might have, and I'll hand it back to Sirinush to manage that. Thank you very much.

384
00:51:39.760 --> 00:51:54.429
MTS - AV: We have really 30 minutes for Q&A, and this is exactly the time for you to ask questions and unique opportunity. Please raise your hand, I will see. Okay, Sadhichita, we start, and then we'll come to you.

385
00:51:55.610 --> 00:51:56.300
MTS - AV: Yes.

386
00:51:59.550 --> 00:52:12.799
MTS - AV: Hello, everyone. It's me, Sadiktha Silval from Nepal. I am with Fellowship program. I have a question for John. As I am from Nepal, and you mentioned about the SSR research.

387
00:52:12.800 --> 00:52:21.220
MTS - AV: for the, that supports the resiliency of internet and things. So, how does SSR research conduct under

388
00:52:21.220 --> 00:52:28.309
MTS - AV: IROS translate into a practical improvement in the resilience of the zone… root zone.

389
00:52:28.360 --> 00:52:52.690
MTS - AV: For example, does the research inform the operational challenges, like early warning systems, or the recommendation to the root server operator and the wider community? I'm saying specifically to the context that we recently have a disastrous flood in Nepal, and the early warning system and the internet resilience was something we learned from that flood, so yeah.

390
00:52:53.410 --> 00:53:10.449
MTS - AV: So, ICANN itself doesn't have a major resilience study program. There are other organizations that do, and we participate. There's an organization called the Marconi Society that is doing a lot of work bringing together

391
00:53:11.180 --> 00:53:15.939
MTS - AV: providers of… Services for communication.

392
00:53:16.210 --> 00:53:20.379
MTS - AV: So, you know, the internet's not just the identifiers you need,

393
00:53:21.240 --> 00:53:26.730
MTS - AV: physical connectivity, etc, and we do participate in those.

394
00:53:26.990 --> 00:53:31.010
MTS - AV: We do studies… Around…

395
00:53:31.930 --> 00:53:46.899
MTS - AV: things like how easy is it to query a DNS service? Very technical things. We tend not to get into the… all the other important parts of resilience for communications infrastructure.

396
00:53:46.990 --> 00:53:54.920
MTS - AV: What we do is we participate in other programs which are much broader, and we bring our expertise. Now, that said.

397
00:53:55.020 --> 00:54:02.449
MTS - AV: We have a lot of contacts in country, so, you know, if there's ever a disaster, and…

398
00:54:02.730 --> 00:54:20.719
MTS - AV: the CCTLD or others come to us from the identifier side and ask for help, yes, we step in. You know, either with advice or finding help, etc, but it's not a core part of ICANN's role. ICANN's role is that identifier part. Now, of course, we run a root server.

399
00:54:20.940 --> 00:54:31.680
MTS - AV: Right? I think we actually have one in Nepal. I think we have one in Kathmandu. So we operate the root servers, root server operators, of which we are only one.

400
00:54:31.930 --> 00:54:37.550
MTS - AV: We communicate a lot and work together, and you know, our role is to provide this service.

401
00:54:38.250 --> 00:54:45.919
MTS - AV: And we all do work together to try and ensure that we get these around the globe, get them as close to the end user as possible.

402
00:54:46.040 --> 00:54:54.099
MTS - AV: There's actually new emerging discussion about whether or not physical route service is the best way to get that service.

403
00:54:54.420 --> 00:54:58.490
MTS - AV: Because what you're actually interested in is DNS resolution service.

404
00:54:58.640 --> 00:55:02.850
MTS - AV: A root server describes Basically, a box…

405
00:55:03.110 --> 00:55:17.489
MTS - AV: a way of getting that service. You know, there are 13 letters put into the HINS file on the root zone that identify these 13 machines, and the DNS does its thing, and that's one of the first places it goes on a new resolver.

406
00:55:17.950 --> 00:55:23.839
MTS - AV: But there are other mechanisms at play at the moment. And within the Internet Engineering Task Force.

407
00:55:24.100 --> 00:55:31.709
MTS - AV: about, are there ways to make this more resilient? And we are looking at that. Don't have any papers on it at the moment, it's…

408
00:55:31.990 --> 00:55:35.400
MTS - AV: It's been around for a long while, but it's only now getting documented.

409
00:55:35.750 --> 00:55:45.649
MTS - AV: So, you know, we're interested very much on the identifier space. So when it comes down to root servers, absolutely. We are doing some studies at the moment.

410
00:55:45.860 --> 00:55:54.099
MTS - AV: About… deciding… scientifically, As scientific as you can be with data on the internet.

411
00:55:54.500 --> 00:56:00.089
MTS - AV: where the best place is to position all of these instances we have. We have

412
00:56:00.460 --> 00:56:14.140
MTS - AV: 100 and something instances around the globe. Amongst all the root servers, there's a thousand plus of these machines out there, whether it's actually a physical machine or it's in somebody's cloud infrastructure. So…

413
00:56:15.250 --> 00:56:20.419
MTS - AV: We're not doing any specific studies on it at the moment, but we are participating in a lot of other

414
00:56:20.660 --> 00:56:23.919
MTS - AV: bodies that are looking at these things. So, yeah, thank you for the question.

415
00:56:24.040 --> 00:56:25.650
MTS - AV: Thank you, Sanjina.

416
00:56:27.880 --> 00:56:37.360
MTS - AV: Hello, everyone. I'm Sanjina Chhetri, I'm from Nepal. I'm a next-gen participant for ICANN87. I have a question for Kim.

417
00:56:37.580 --> 00:56:42.140
MTS - AV: You just said that IANA doesn't decide who,

418
00:56:42.290 --> 00:56:44.169
MTS - AV: Which

419
00:56:44.950 --> 00:56:59.509
MTS - AV: which CCTRD to give to which country. So, I just wanted… I was just curious who decides that, and also, if not INA, then who decides which CCTRD to give to which country, and also how that

420
00:56:59.510 --> 00:57:12.579
MTS - AV: that thing is managed, like, how it balances the global take, balance, and also the local interests, or the country's interest of, on that manner, so…

421
00:57:14.710 --> 00:57:29.139
MTS - AV: Thanks for the question. So, when it comes to, country code top-level domains, or ccTLDs, there's, I guess, two parts to the answer. One is, how is the two-letter code decided to represent a country, like NP for Nepal?

422
00:57:29.140 --> 00:57:43.919
MTS - AV: So we follow an international standard called ISO 3166. This is a standard that is used globally for not just domain names, but if you look in your passport and the coding on the passport, it uses ISO 3166 codes.

423
00:57:43.920 --> 00:57:57.549
MTS - AV: Currency codes use ISO 3166. All manner of different ways of needing to codify countries use the same international standards. So the two letter codes themselves come from ISO.

424
00:57:57.880 --> 00:58:13.560
MTS - AV: So that's part one to your question, but I think the bulk of your question is who runs the CCTLD. And the way the policy is structured is essentially who runs any individual country code should be a local decision within the country.

425
00:58:13.650 --> 00:58:32.619
MTS - AV: So the global policy doesn't dictate like a certain procedure that happens at the global level. For example, we don't decide directly. What we're obligated to do is to perform due diligence to make sure that an appropriate process happened within the country.

426
00:58:32.680 --> 00:58:35.990
MTS - AV: to identify who should run their CCTLD.

427
00:58:36.440 --> 00:58:41.969
MTS - AV: And that the party that we're being asked to recognise is a product of that process. Now.

428
00:58:42.450 --> 00:58:48.119
MTS - AV: That's at the high level. Obviously, there's some nuance and some detail that go into that.

429
00:58:48.800 --> 00:59:08.699
MTS - AV: A big one is compatibility with local laws. Like we have to have an operator that is in the country that is adhering to local laws. So if, for example, there are local laws that say the CCTLD must be administered in a certain fashion, that's part of the analysis that we need to assess that they are complying with those obligations.

430
00:59:08.790 --> 00:59:18.059
MTS - AV: Competency is a very important one, arguably the most important one. CCTLDs are critical internet infrastructure.

431
00:59:18.550 --> 00:59:33.029
MTS - AV: Whole countries rely on their CCTLD working. So, it's important to us that we do not assign it to an operator that does not know how to run critical infrastructure. So, we obligate applicants that want to run a CCTLD to prove that

432
00:59:33.030 --> 00:59:42.860
MTS - AV: they are capable of running a ccTLD. They have to document their technical infrastructure, their operations. We talked about in the last question, like redundancy and

433
00:59:42.860 --> 01:00:00.650
MTS - AV: The ability to sustain operations in the event of some kind of natural disaster. So we asked them, for example, like, where are your different locations? How have you structured your systems so that if there is a single failure, maybe one particular building is out of commission, how will you keep the CCTLD running?

434
01:00:00.650 --> 01:00:12.550
MTS - AV: Things like that. So, operational competency, compatibility with local laws, you know, there's a multi-stakeholder community in the country, have they participated in developing the approach, and so forth.

435
01:00:12.730 --> 01:00:24.739
MTS - AV: And then lastly, I would say that, you know, practically all CCTLDs exist today. There is already an existing operator. So if there's a proposal to move it to a new operator.

436
01:00:24.790 --> 01:00:39.649
MTS - AV: We need to look at what the transfer looks like. So we're taking an existing ccTLD that people rely on today that is presumably working, or at least somewhat working. And we want to make sure that after we move to the new operator.

437
01:00:39.820 --> 01:00:51.689
MTS - AV: that it will still keep working. So we need to look at how are all the files, how are all the records, the business operations going to move from the previous operator to the new operator? So that's part of the assessment as well.

438
01:00:51.920 --> 01:01:06.080
MTS - AV: But ultimately, like, we're not there to, like, decide, hey, we like that organization. We think they should run it. We're looking at a proposals come to us from the country saying, we've done our research, we've done our preparation inside the country.

439
01:01:06.230 --> 01:01:15.439
MTS - AV: This is the culmination of that process that's happened within the country. We're seeking for you to recognize it, and here we're going to prove that we've done everything correctly, and if…

440
01:01:15.630 --> 01:01:31.190
MTS - AV: you know, they have, we will say yes, we'll move forward, and if they haven't, we'll say, look, we've analysed your proposal, and here are the problem areas, and essentially have them go back and work on it. And, you know, they can go back and do corrective work, or continue to develop their application if they wish.

441
01:01:32.220 --> 01:01:36.659
MTS - AV: Thank you. And if I can… Add, because this is an…

442
01:01:37.000 --> 01:01:42.460
MTS - AV: Not really a nuance, but this is a factor of the internet that you always need to keep in mind.

443
01:01:43.420 --> 01:01:52.330
MTS - AV: the internet and CCTLDs, go way back. So many of these decisions were made in… back in the day.

444
01:01:52.550 --> 01:02:11.510
MTS - AV: way before ICANN exists… I mean, one of the reasons ICANN is formed is because we needed to formalize the internet identifier governance. So a lot of these things happened. That gentleman, John Postel, was making decisions back in the day. And a lot of the existing CCTLDs will be the people that connected your country to the internet.

445
01:02:12.170 --> 01:02:21.199
MTS - AV: Or they may have gone to somebody outside your country for a while who was helping, and then gone back in, and there's so much history there.

446
01:02:21.650 --> 01:02:25.490
MTS - AV: Not all of it as clearly documented as we would wish.

447
01:02:26.130 --> 01:02:38.310
MTS - AV: And that's not just with domain names, right? That is also with IP addresses, and with many of these older identifiers. So sometimes you may sit there and go, but this is obviously not the way it would be designed today.

448
01:02:39.220 --> 01:02:44.229
MTS - AV: But then when you come to us and say, well, this is not the way it's supposed to be, you know, it's meant to be this way, then…

449
01:02:44.530 --> 01:02:47.900
MTS - AV: Kim is going to come into these questions, well, how are you going to move that?

450
01:02:48.090 --> 01:02:52.630
MTS - AV: How's that going to work? And we often will get people come and say, well, we need to move this because…

451
01:02:53.680 --> 01:02:55.590
MTS - AV: We are now the right people.

452
01:02:56.240 --> 01:02:58.650
MTS - AV: And when you ask them how they're going to run it.

453
01:02:58.780 --> 01:03:11.030
MTS - AV: It's actually a really great opportunity to bring in people like our engagement folks, and go and actually educate them about what it takes to run a TLD, what… how the DNS works, how DNSSEC works.

454
01:03:11.710 --> 01:03:19.669
MTS - AV: In the background, the internet's actually quite complicated. So, you know, all of these things tie together, but IANA is that…

455
01:03:20.120 --> 01:03:22.110
MTS - AV: I would never call it a spreadsheet.

456
01:03:22.940 --> 01:03:26.960
MTS - AV: Maybe a CSV file, but never a spreadsheet.

457
01:03:28.110 --> 01:03:29.930
MTS - AV: Thank you, Roshate.

458
01:03:30.140 --> 01:03:39.289
MTS - AV: Yes, so my name is Roshate. I work as an AI manager. My question is related to the IROS and the future of the internet.

459
01:03:39.320 --> 01:03:53.889
MTS - AV: As we all know that AI-driven technologies are becoming part of the internet infrastructure, I would want to know how is Airoz working to identify the emerging technical risks that come with it?

460
01:03:53.890 --> 01:04:01.129
MTS - AV: while ensuring that the internet is globally accessible, open, and interoperable. So, yes.

461
01:04:01.400 --> 01:04:04.030
MTS - AV: That is a fantastic question, and if you could…

462
01:04:04.560 --> 01:04:10.420
MTS - AV: Help us, it would be great. So… AI is…

463
01:04:11.290 --> 01:04:25.609
MTS - AV: the latest keyword, or sales pitch that people use today, right? Everything is AI this, AI that. But it's… for once, it's actually a technology, because we've seen hundreds of these technologies over the years.

464
01:04:25.980 --> 01:04:31.159
MTS - AV: That is realistically a truly disruptive technology.

465
01:04:32.420 --> 01:04:36.620
MTS - AV: Maybe not the individual implementations of machine learning that.

466
01:04:36.780 --> 01:04:44.729
MTS - AV: RAI, but the phenomenon of generative AI, et cetera, is transforming society, just like the internet did.

467
01:04:44.980 --> 01:04:52.049
MTS - AV: So we do look at it, but you have to remember that we are looking at it in the context of ICANN's mission.

468
01:04:52.630 --> 01:05:00.749
MTS - AV: We are not responsible for a stable internet, we are responsible for the stable identifiers that allow that.

469
01:05:00.900 --> 01:05:07.429
MTS - AV: Right? So if somebody's laying stupid cables in all the wrong places in the world, we might tell them, but it's not our responsibility.

470
01:05:07.690 --> 01:05:15.260
MTS - AV: But identify it as our area. So one of the things we're looking at is How does…

471
01:05:15.450 --> 01:05:18.359
MTS - AV: AI affect the identifier system?

472
01:05:18.790 --> 01:05:22.150
MTS - AV: But also, how does AI use identifiers?

473
01:05:22.640 --> 01:05:27.170
MTS - AV: Specifically Agentic AI is really interesting at the moment. There are at least six.

474
01:05:27.490 --> 01:05:32.130
MTS - AV: Different proposals out there about agents using.

475
01:05:32.780 --> 01:05:34.340
MTS - AV: identifiers.

476
01:05:34.700 --> 01:05:38.170
MTS - AV: That either are or look like domain names.

477
01:05:38.950 --> 01:05:42.499
MTS - AV: Just because something looks like a domain name doesn't mean it's a domain name.

478
01:05:43.540 --> 01:05:47.120
MTS - AV: None of them… our standards.

479
01:05:50.330 --> 01:05:58.129
MTS - AV: Certainly none of them are open standards, meaning that everybody can use them, and we're tracking those, and we're trying to figure out

480
01:05:58.330 --> 01:06:01.210
MTS - AV: Where is this technology going? So…

481
01:06:01.940 --> 01:06:16.549
MTS - AV: We actually have, I believe, a session on that here at this meeting. We often have sessions that we talk about the future of the identifier systems and emerging technologies, and I believe the one this week is on Agentic AI.

482
01:06:17.010 --> 01:06:20.079
MTS - AV: But there are other questions that we don't know the answers for. Now…

483
01:06:20.530 --> 01:06:32.860
MTS - AV: I run ENIT. Well, I don't run it, but I watch people run it. I'm an exec… I don't… I'm an executive, I don't really do any real work. I've got people for that, and they're fantastic. But they are…

484
01:06:33.460 --> 01:06:38.169
MTS - AV: with myself, we're looking at how are we going to use AI as an organization?

485
01:06:38.660 --> 01:06:43.799
MTS - AV: We have all the same questions that every other business and organization.

486
01:06:44.530 --> 01:06:47.690
MTS - AV: on this planet has. We're no different, right?

487
01:06:47.930 --> 01:06:52.129
MTS - AV: We have the advantage that we actually have people who understand technology.

488
01:06:52.450 --> 01:06:59.460
MTS - AV: But a lot of this stuff, it's not standardized. There's no open standards. You kind of have to guess what they're doing.

489
01:06:59.610 --> 01:07:01.740
MTS - AV: So that's problematic.

490
01:07:02.600 --> 01:07:09.390
MTS - AV: Right? If you're a believer that the internet grew because of open standards, and the ability of everybody to interconnect.

491
01:07:09.630 --> 01:07:13.140
MTS - AV: Then that's a little worrying, but we can't make them do this.

492
01:07:13.550 --> 01:07:19.760
MTS - AV: ICANN is not the governance body for artificial intelligence, and will not be.

493
01:07:20.490 --> 01:07:22.540
MTS - AV: Right? That is not our role.

494
01:07:23.670 --> 01:07:30.319
MTS - AV: When something goes interesting, I'm not gonna say wrong, something goes interesting in the world, and it needs a global governance.

495
01:07:30.730 --> 01:07:39.500
MTS - AV: People come to us, especially if it's technology, and they look to us for an example of how you can do governance. That doesn't mean they're looking at us to do it.

496
01:07:40.150 --> 01:07:46.489
MTS - AV: There are other areas that we do not know about, and people are starting to study this, but how does the use of

497
01:07:46.670 --> 01:07:52.080
MTS - AV: LLMs, for example, to develops policy standpoints.

498
01:07:52.430 --> 01:07:54.330
MTS - AV: How is that going to affect the policy?

499
01:07:55.980 --> 01:08:00.420
MTS - AV: We actually don't know if everybody's using the same public LLM, or is…

500
01:08:00.720 --> 01:08:05.579
MTS - AV: Are the people actually doing the thinking, or are they all getting sort of groupthink through the LLM?

501
01:08:05.870 --> 01:08:08.660
MTS - AV: We don't… so there are so many questions.

502
01:08:08.770 --> 01:08:10.900
MTS - AV: We are focusing mostly.

503
01:08:11.350 --> 01:08:12.930
MTS - AV: on Agentic AI.

504
01:08:13.260 --> 01:08:28.219
MTS - AV: Because that's where the indicators are at the moment that there's going to be a cross-section with identifiers. There is some work in the Internet Engineering Task Force, but there are at least 5 of the proposals out there outside the IETF.

505
01:08:29.240 --> 01:08:36.190
MTS - AV: and we are following closely. We are going to put out some documentation in the next months.

506
01:08:38.790 --> 01:08:41.209
MTS - AV: I don't know that we're late to the game.

507
01:08:42.279 --> 01:08:46.469
MTS - AV: Or I don't think we're any later to the game than the rest of humanity.

508
01:08:46.590 --> 01:08:49.799
MTS - AV: But yes, it's fascinating.

509
01:08:49.979 --> 01:08:53.080
MTS - AV: And this is something that is going to give us.

510
01:08:53.640 --> 01:08:58.450
MTS - AV: Both threats and problems, and vast opportunities.

511
01:08:58.760 --> 01:09:05.429
MTS - AV: And we're trying to fit, just like everybody else in the world, we're trying to figure it out. We're lucky that we have so many smart people to help us.

512
01:09:06.810 --> 01:09:10.800
MTS - AV: But yeah, I mean, what amazing times to live in.

513
01:09:10.970 --> 01:09:13.630
MTS - AV: to be going through this.

514
01:09:15.090 --> 01:09:21.450
MTS - AV: I think, watch this space. We're definitely going to do something. You will hear people in the community

515
01:09:21.930 --> 01:09:30.819
MTS - AV: talking about Agentic AI, and you will see proposals About… Agentic AI.

516
01:09:32.600 --> 01:09:36.319
MTS - AV: The questions you should ask yourself when you see people doing these are things like.

517
01:09:36.790 --> 01:09:41.259
MTS - AV: Oh, are they suggesting an open standard so they can do this with everybody else?

518
01:09:41.770 --> 01:09:44.490
MTS - AV: Or are they looking at closed environments?

519
01:09:44.670 --> 01:09:45.830
MTS - AV: For themselves.

520
01:09:46.649 --> 01:09:54.580
MTS - AV: Are they doing this for the good of the internet, which is what ICANN's here for? And there's nothing wrong with doing things for commercial reasons, but you need to dis…

521
01:09:54.770 --> 01:09:57.750
MTS - AV: You need to understand the distinction and why they're doing things.

522
01:09:57.870 --> 01:10:03.400
MTS - AV: So it's a very interesting time, and I think the next 12 months or so is only going to get more interesting.

523
01:10:04.150 --> 01:10:07.189
MTS - AV: Happy to chat with you offline, because maybe you have ideas.

524
01:10:08.490 --> 01:10:12.520
MTS - AV: Thank you. We have a question from Frank. Frank, please.

525
01:10:12.530 --> 01:10:29.030
MTS - AV: Okay. Frank Asifwa, for the record, I work with an institution called the Association of African Universities. I was quite interested in the conversation with regards to how there are continental leads who are training across the continent.

526
01:10:29.030 --> 01:10:44.139
MTS - AV: We have a very successful relationship regarding universal acceptance. We've worked with ICANN on universal acceptance on the continent. We've been able to help over 300 universities across the continent to

527
01:10:44.140 --> 01:11:03.170
MTS - AV: get both their websites and their emails compliant, and we continue to support, and then we are even incorporating some in, their, curriculum. But, as you know, curriculum changes are quite, difficult. I was wondering if there was a way we could get in touch with the, continental lead on the African continent.

528
01:11:03.170 --> 01:11:12.379
MTS - AV: So we could work with them and then see ways we could synergize and then extend the reach of the activities they're doing so we could reach out to more universities on the continents.

529
01:11:12.620 --> 01:11:19.110
MTS - AV: I don't know if that was supposed to be a backroom meeting, but since I have you here, I wanted to ask that. Thank you.

530
01:11:19.570 --> 01:11:20.770
MTS - AV: So…

531
01:11:21.370 --> 01:11:34.539
MTS - AV: you could… probably your best bet is to talk to Adiel Ekplugen, who is… will be here. He leads our technical engagement team, and he will be here. I think he arrives tomorrow. He would normally be sitting at this table.

532
01:11:34.540 --> 01:11:42.170
MTS - AV: We've moved these meetings further, earlier and earlier in the meeting, so they happen before most of the staff gets here. Happy to have that conversation.

533
01:11:42.320 --> 01:11:57.729
MTS - AV: We try to be a force multiplier. So we clearly can't get into all the universities. So if we can work with like NREN organizations or education organizations, that just makes our job much easier. So let me make that introduction.

534
01:11:59.570 --> 01:12:01.330
MTS - AV: Mahdiha?

535
01:12:02.720 --> 01:12:20.220
MTS - AV: Hello, everyone. My name is Madjiha Mohammad, and I'm an ICANN Fellow. I guess my question starts from the core, sort of function of IANA, which is to ensure interoperability. Speaking of international domain names, how do you, sort of.

536
01:12:20.860 --> 01:12:44.400
MTS - AV: You know, follow up to that, especially with the reveal day sort of revealing basically more application for IDNs. And when it comes to, let's say, the set of rules that are fixated on managing that, how do you also make sure that sort of the IDNs are not in a way monopolized for lack of better terms? Because if we see, for example, it's mostly specific scripture like Mandarin.

537
01:12:44.400 --> 01:12:49.869
MTS - AV: That is sort of, the greater in number. So for maybe.

538
01:12:49.900 --> 01:13:02.259
MTS - AV: one or two, GTLDs that are, like, in another language that is not as huge as Chinese, for example. How do you make sure it's sort of… I wouldn't say necessarily equal, but everything works as it should.

539
01:13:04.090 --> 01:13:08.920
MTS - AV: That sounds more like a next round question than an IANA question. So…

540
01:13:10.110 --> 01:13:24.839
MTS - AV: we can't force people to apply for GTLDs, right? So, the world, unfortunately, isn't fair, and it's driven by business and interest and enthusiasm. So what we did do is we did an applicant supports program.

541
01:13:25.020 --> 01:13:28.510
MTS - AV: To try and help fund organizations.

542
01:13:28.950 --> 01:13:37.569
MTS - AV: that didn't necessarily have the resources, and we did a lot of outreach around universal acceptance and IDNs to try and encourage people.

543
01:13:37.870 --> 01:13:46.530
MTS - AV: Yeah, I think you could argue it's disappointing that we didn't get as many as we'd hoped.

544
01:13:46.860 --> 01:13:52.509
MTS - AV: I don't actually have the answer to how you do that, how you get more people.

545
01:13:52.770 --> 01:13:58.740
MTS - AV: They are specifically, we released the strings, I think last week, I can't remember exactly when.

546
01:13:59.060 --> 01:14:07.800
MTS - AV: And there are… the majority of the IDNs that are in there are indeed of one specific script.

547
01:14:08.810 --> 01:14:17.049
MTS - AV: Yeah, I don't have a good answer to you. I don't know how you… Persia technology. If the

548
01:14:17.180 --> 01:14:26.330
MTS - AV: business and the industries are not out there chasing it themselves. Even if there's a user need for it, I don't know how you push people to actually go and deploy those things.

549
01:14:27.620 --> 01:14:28.620
MTS - AV: You're welcome.

550
01:14:28.810 --> 01:14:33.689
MTS - AV: Yeah, I can add to that. I mean, I guess firstly from an IANA perspective.

551
01:14:33.920 --> 01:14:45.210
MTS - AV: You know, ANA's job is not to make technologies a roaring success. Our job is to globally coordinate what needs to be globally coordinated to make sure they can work.

552
01:14:45.680 --> 01:15:03.999
MTS - AV: But whether they're a market success or market failure is really beyond our remit, and there's plenty of really interesting technologies that completely fall flat due to lack of interest. It's not really solving a problem people have, or maybe it's a very small problem and it's just not worth the effort.

553
01:15:04.530 --> 01:15:16.389
MTS - AV: I think, frankly, and this is switching to my personal perspective, I think the jury is a bit out for IDNs as a technology as a whole. Like it's a great technology, it works.

554
01:15:16.480 --> 01:15:30.529
MTS - AV: ICANN's invested a lot of effort into making sure they work. IANA's invested a lot of work into it. But ultimately, whether IDNs succeed or fail broadly is whether people use them.

555
01:15:30.820 --> 01:15:32.410
MTS - AV: If people want to use them.

556
01:15:32.540 --> 01:15:41.069
MTS - AV: Setting aside the gTLD application round, we offer IDN ccTLD. So if there's countries out there that want

557
01:15:41.150 --> 01:15:55.659
MTS - AV: a non-Latin script representation of their country name, it's available for free for them if they just want to apply and get it for their country. There are processes, and certainly a lot of Arabic-speaking countries have done this.

558
01:15:55.830 --> 01:15:59.279
MTS - AV: Han script, Chinese, etc, have done this as well.

559
01:15:59.480 --> 01:16:02.829
MTS - AV: But, you know, the adoption is a…

560
01:16:03.100 --> 01:16:10.880
MTS - AV: We're not here necessarily to make sure everyone uses IDNs. It's to make sure that they work, they function. If people want to use them, they're available.

561
01:16:11.010 --> 01:16:17.139
MTS - AV: But the broader market has to run with it, and I think that's where we're at with this particular technology.

562
01:16:18.350 --> 01:16:27.110
MTS - AV: Thank you. Mary, our first ever fellow from Tumur Leslec country, so please go ahead. So, how everyone?

563
01:16:28.110 --> 01:16:44.420
MTS - AV: Hello, everyone. I'm Mary from Timor-Leste. Before I'm going to the question, ask the question, first of all, I want to say thank you again to the ICANN to give the opportunity to the Timor-Leste people to join the ICANN here.

564
01:16:44.580 --> 01:16:46.390
MTS - AV: So this is my guess.

565
01:16:46.820 --> 01:17:02.060
MTS - AV: As someone working in the telecommunication industry, I would like to understand how IROS research can help improve the internet, especially in developing countries. Could you please share some examples of how this research can be applied in practice?

566
01:17:02.560 --> 01:17:03.580
MTS - AV: Thank you.

567
01:17:04.850 --> 01:17:06.219
MTS - AV: So often.

568
01:17:06.330 --> 01:17:12.080
MTS - AV: It depends on the problem you're trying to solve. So… If you're…

569
01:17:12.320 --> 01:17:18.350
MTS - AV: in a country, and your citizens are being affected by DNS abuse.

570
01:17:18.460 --> 01:17:32.300
MTS - AV: then obviously developing science to help track and monitor and then hopefully take action against that will help you, will help that citizenship. Right. It's not directed at a specific country. Most of the issues we deal with.

571
01:17:32.480 --> 01:17:33.660
MTS - AV: are…

572
01:17:34.140 --> 01:17:47.609
MTS - AV: Global. Now, with some of the research we're doing about measuring connectivity for root servers or DNS resolution, if we can identify… I think we may actually have a server in Timor-Leste as well, I have to check that.

573
01:17:47.990 --> 01:17:56.030
MTS - AV: you know, then we can identify places that are harder to get to. I mean, Tim Olesley doesn't have a lot of connectivity options.

574
01:17:56.630 --> 01:17:58.560
MTS - AV: And that may help us.

575
01:18:00.130 --> 01:18:04.479
MTS - AV: You know, look at that place and say, hey, there's a spot that we need to get some better infrastructure in.

576
01:18:04.770 --> 01:18:06.779
MTS - AV: For our infrastructure, not…

577
01:18:06.890 --> 01:18:15.609
MTS - AV: the bandwidth, that's not what we do. And then we can actually identify that and go and actually improve the infrastructure. So it does help

578
01:18:16.960 --> 01:18:19.260
MTS - AV: Nations that are less connected.

579
01:18:19.490 --> 01:18:29.859
MTS - AV: We also have, which is not my group, although we participate heavily in it, we also have a lot of regional outreach that are

580
01:18:30.210 --> 01:18:32.410
MTS - AV: On the side of…

581
01:18:32.710 --> 01:18:42.969
MTS - AV: ICANN's mission. We have a lot of partnerships where we will work with other people, things like education, helping increase the education. There are bandwidth

582
01:18:43.400 --> 01:18:50.689
MTS - AV: programs out there that we are not the leader of, but we may actually give them advice.

583
01:18:51.420 --> 01:18:58.559
MTS - AV: I don't know… If Tim Oleste's looking at… the issues around

584
01:18:58.940 --> 01:19:02.590
MTS - AV: post quantum for their DNSX signing for their TOD.

585
01:19:02.910 --> 01:19:09.590
MTS - AV: So we don't aim at a specific country. Our mission is very global, but they should help you locally.

586
01:19:09.760 --> 01:19:14.390
MTS - AV: The one thing that we don't talk about A lot.

587
01:19:15.700 --> 01:19:21.620
MTS - AV: And it's not really written down, but what we are very good at, especially these technical engagement people.

588
01:19:21.790 --> 01:19:25.390
MTS - AV: is introducing People to each other.

589
01:19:25.720 --> 01:19:29.949
MTS - AV: So, I would suggest that you took to…

590
01:19:30.090 --> 01:19:42.220
MTS - AV: Talk to our folks in the technical engagement, and our global stakeholder engagement, and tell them about what's happening on the island, or what's happening in your country, and how can

591
01:19:42.580 --> 01:19:51.129
MTS - AV: You know, they help, because there's nothing they love more than actually making a real difference on the ground. So, talk to our folks.

592
01:19:51.640 --> 01:19:58.040
MTS - AV: And, like, have a conversation about what you think the issues are. And they may turn around and say, well, that's not something ICANN can really do.

593
01:19:58.580 --> 01:20:05.429
MTS - AV: But… We know these people over here. Why don't we do an introduction? We do a lot of that.

594
01:20:05.660 --> 01:20:12.550
MTS - AV: We're very good at connecting people. It's not… but we don't generally do things based on a specific

595
01:20:12.870 --> 01:20:20.210
MTS - AV: locality. We tend to look more globally, and those global things You know, will affect…

596
01:20:20.670 --> 01:20:22.269
MTS - AV: What's happening in your country?

597
01:20:22.630 --> 01:20:29.509
MTS - AV: You know, those protocols we work on, those internet protocols, they're for everybody. They're not for a specific locality, but without them.

598
01:20:29.690 --> 01:20:32.030
MTS - AV: Obviously, Tim Alessi also can't have

599
01:20:33.030 --> 01:20:49.619
MTS - AV: DNS error signaling, which, you know, I'm sure you woke up this morning and thought, oh, I wish I had DNS error signaling. But, you know, that's something that the internet needed, and we do it for the… more for the global sphere. I know that's not exactly an answer you wanted, but let's have a conversation afterwards and see if we can introduce you to some people.

600
01:20:50.820 --> 01:20:52.970
MTS - AV: Thank you. Andrew, please.

601
01:20:56.720 --> 01:21:14.980
MTS - AV: Hello everyone. Thank you for the wonderful talk. I'm Anuza, a computer engineering student from Nepal. As IPv4 addresses are running out and there is adaptation to IPv6, does moving to IPv6 create new security or stability risk for DNS?

602
01:21:15.200 --> 01:21:19.459
MTS - AV: And how do you measure it or look for it? Thank you.

603
01:21:20.680 --> 01:21:21.739
MTS - AV: Doesn't matter what you take.

604
01:21:23.110 --> 01:21:26.029
MTS - AV: I mean, I think that's a good question.

605
01:21:27.920 --> 01:21:32.320
MTS - AV: Fundamentally, no. IPv6 doesn't change…

606
01:21:32.590 --> 01:21:37.770
MTS - AV: interactions with the DNS in a way that presents new security risks and so forth. I think…

607
01:21:38.200 --> 01:21:44.919
MTS - AV: A lot of the… networking challenges that IPv6 seeks to solve.

608
01:21:45.070 --> 01:21:51.439
MTS - AV: is because IPv6 exhaustion has been a problem for 20 years or more.

609
01:21:52.010 --> 01:22:05.270
MTS - AV: A lot of the mess about how networks are provisioned is trying to solve for that problem before IPv6 came around. So a lot of private networking constructs and things and so forth have been built around.

610
01:22:05.380 --> 01:22:22.459
MTS - AV: IPv6 is so scarce that we need to have, you know, private networks and reuse IP addresses in different contexts because we've run out. And a lot of the complexity around network administration comes from that problem, which IPv6 is trying to solve. I think…

611
01:22:22.590 --> 01:22:27.149
MTS - AV: From where I sit, you know, IPv6… Does solve that problem.

612
01:22:27.230 --> 01:22:40.179
MTS - AV: Obviously, adoption has been a general issue, but very gratified that over the last 5 years or so, that adoption has really taken off, and I think, you know, we started to see this particularly with mobile phone networks.

613
01:22:40.180 --> 01:22:49.530
MTS - AV: I would suggest that almost every mobile phone here is using IPv6, not IPv4, because that's the way modern mobile networks are provisioned.

614
01:22:49.580 --> 01:23:08.370
MTS - AV: And through that, I mean, I don't know what the numbers are now, but IPv6 is at least on par, if not overtaken, IPv4 usage. So I think, you know, IPv6 should make network administration easier. It shouldn't present new problems for the DNS. DNS has had

615
01:23:08.460 --> 01:23:10.300
MTS - AV: IPv6 support.

616
01:23:10.630 --> 01:23:12.550
MTS - AV: You know, for a very long time.

617
01:23:12.680 --> 01:23:28.810
MTS - AV: You know, all the root servers support IPv6, practically every TLD supports IPv6, so all the core infrastructure there to support it is there. It's just relying on that long tail of adoption, which is, you know, smaller networks.

618
01:23:28.940 --> 01:23:35.450
MTS - AV: you know, home networks and things to eventually get on, but, you know, it will happen. I don't know if there's anything you wanted to add.

619
01:23:37.720 --> 01:23:42.869
MTS - AV: Yeah, I mean, in our global deployments with the root server, we manage…

620
01:23:43.940 --> 01:23:49.939
MTS - AV: It used to be an issue, right? Oh, can we get native V6 as well as V4?

621
01:23:50.490 --> 01:24:00.489
MTS - AV: It doesn't really exist much anymore. You can pretty much always get V6. There's the occasional place. We have a few locations that they just haven't deployed V6 because they had no need.

622
01:24:00.820 --> 01:24:04.050
MTS - AV: Right? If you have enough V4 for your network.

623
01:24:05.450 --> 01:24:23.749
MTS - AV: Why would you deploy V6, right? Why would you change technology? This is not the first time we've been through IP technology changes. You know, we changed the way we used IP version 4. We did something called CIDR, which is classless inter-domain routing.

624
01:24:24.040 --> 01:24:29.690
MTS - AV: Back in the, I guess, early 90s, trying to… That was painful.

625
01:24:30.000 --> 01:24:48.540
MTS - AV: I was there, like, trying to help that in Europe, and it was painful to get through it, but we got through it, and the same will happen for V6. It will eventually… we've always known that we would have islands of V6 in a V4 world, and we would eventually go to islands of V4 in a V6 world.

626
01:24:49.170 --> 01:24:57.109
MTS - AV: We never knew how long it would take, and we're still in that transition. But I don't think that fundamentally, V6

627
01:24:57.590 --> 01:25:02.170
MTS - AV: adds DNS specific security risks at all like Kim was saying.

628
01:25:02.660 --> 01:25:05.250
MTS - AV: There are interesting things about…

629
01:25:05.860 --> 01:25:17.600
MTS - AV: you know, being able to do jumbograms, being able to do larger packet sizes, etc, in V6, that may actually help us out in the future. You know, as we go to larger key sizes, depending on how

630
01:25:18.710 --> 01:25:28.739
MTS - AV: negative you are about it. Some people think that every packet's going to be enormous, and we're going to need to be able to send those a single packet, so there are actually advantages to V6.

631
01:25:28.940 --> 01:25:34.290
MTS - AV: But normally it's the commercial that matters, so if you don't have… if you have V4,

632
01:25:34.450 --> 01:25:39.149
MTS - AV: you generally don't move to V6, and as V4 gets more expensive.

633
01:25:39.370 --> 01:25:46.780
MTS - AV: people are going, well, why would I spend that money if I can do everything with V6? It's amazing how economics actually drives everything.

634
01:25:48.710 --> 01:26:04.749
MTS - AV: Very short questions. We're not able to take the more questions. So how it works, I look to the audience and you just give me a sign and there is a line of the people who already want to ask. So Ismael, you are the next.

635
01:26:04.750 --> 01:26:10.690
MTS - AV: And one more for from you. And that will be end of this session. Ismail, go ahead.

636
01:26:10.890 --> 01:26:20.900
MTS - AV: Greetings, everyone. My name is Mahe Ahmed, and I'm CEO, founder of Yalahak, and I'm currently a part of, University of Science and Technology of China.

637
01:26:21.110 --> 01:26:30.829
MTS - AV: First of all, I'd like to thank you so much for this great organization, and the team that's behind this great work for making these meetings happen.

638
01:26:30.940 --> 01:26:38.340
MTS - AV: And second, I'd like also to thanks, for this insightful presentation, which, quitely, I have learned a lot.

639
01:26:38.460 --> 01:26:40.960
MTS - AV: And I have raised, like, about…

640
01:26:41.100 --> 01:26:46.449
MTS - AV: Let's say one question for now, which is about Ayaan.

641
01:26:46.640 --> 01:27:03.710
MTS - AV: My main question is focused on the compliance and the operation. When it comes, previously, IAN is starting to incorporate a new tire for the Security Operations Center, Tire 2 and Tire 3. So, when it comes for the ICANN, where they try to

642
01:27:03.710 --> 01:27:07.269
MTS - AV: do kind of integration between a statistic audit.

643
01:27:07.270 --> 01:27:23.540
MTS - AV: and the continuous compliance monitoring, how it can be both balancing together, as you know, like, every day there is, like, a new, a technology, and with comes new technology, comes new opportunities for the cyber threats. Thank you so much for your explanation.

644
01:27:26.150 --> 01:27:30.730
MTS - AV: Yeah, thanks for the question. I would say that our general

645
01:27:30.890 --> 01:27:35.280
MTS - AV: Posture is to have lots of multiple complementary.

646
01:27:35.290 --> 01:27:48.280
MTS - AV: approaches to making sure our systems are fit for purpose and we do our job well. You mentioned the SOC 2 and SOC 3 audits. I think this is an important part of it. This is where we have a third-party assessor come.

647
01:27:48.280 --> 01:27:56.680
MTS - AV: They sample our systems that, you know, do things like control access to our services.

648
01:27:56.700 --> 01:28:08.969
MTS - AV: And make sure that all of our policies are working effectively. I mean, the SOP framework is a North American-focused framework, so it's much more common in North America, I will admit.

649
01:28:09.010 --> 01:28:22.889
MTS - AV: But ICANN more broadly is rolling out ISO 27001 certification across the whole organisation, including us. So it's a comparable kind of approach. So, if you're familiar with that, that might, you know.

650
01:28:23.200 --> 01:28:35.320
MTS - AV: help you there. But I will say that, you know, within IANA, we don't just rely on these third-party audits. Like, we do regular penetration testing by a third party.

651
01:28:35.680 --> 01:28:38.860
MTS - AV: We do all sorts of different checks and balances.

652
01:28:39.410 --> 01:28:44.990
MTS - AV: We do customer surveys, we do analysis and so forth.

653
01:28:45.140 --> 01:28:47.430
MTS - AV: But I think, also, it's worth noting that

654
01:28:47.500 --> 01:29:05.490
MTS - AV: almost everything we do is public and transparent. So, you know, a lot of when you do audits and security practices, it's about how do you keep things secret? And yes, the cryptographic key we use to secure the DNS is… needs to be kept secret, but that's more the exception to the rule.

655
01:29:05.550 --> 01:29:19.509
MTS - AV: Broadly speaking, the work that we do every day is administering public data sets that you can look at yourself. So we don't need to be too concerned about, making sure we keep our data secret because it's intended to be public.

656
01:29:19.610 --> 01:29:28.509
MTS - AV: What we're more concerned about is did we follow policy? Did we follow procedures? Are we doing requests in a timely manner? And for that.

657
01:29:28.520 --> 01:29:47.779
MTS - AV: We rely on our community. There is committees that will meet later this week that will assess our performance. Do we do our processes quickly enough? Are we following the rules? So there's a lot of oversight within this community to make sure that staff do their job well. We're not relying on sort of like security audits to come to that conclusion.

658
01:29:48.150 --> 01:30:02.660
MTS - AV: I appreciate it. Thank you. We are at the end of our session, but I really want to give the opportunity for IO Foundation team member Ekaladi to ask his question. Chris, go ahead. Thank you very much. Be brief. The last question.

659
01:30:02.990 --> 01:30:08.810
MTS - AV: So I'm Eka. I'm here with the Ayo Foundation as one of the fellows.

660
01:30:08.930 --> 01:30:11.919
MTS - AV: So, I have a question, actually.

661
01:30:12.050 --> 01:30:30.080
MTS - AV: It has been mentioned a few times that ICANN does have a DNS vetting function that helps with DNS abuse. Now, I recognize that ICANN's mandate strictly excludes content regulations, like online gambling and explicit content.

662
01:30:30.180 --> 01:30:35.859
MTS - AV: Unlike, I think, phishing and malware distribution.

663
01:30:36.060 --> 01:30:37.230
MTS - AV: However.

664
01:30:37.540 --> 01:30:48.419
MTS - AV: Operators of those contents heavily rely on technical evasion techniques like fast flux IP hopping and automated domain.

665
01:30:48.450 --> 01:30:59.510
MTS - AV: registrations. Are there telemetry platforms or functions that Okto can use to share these real-time abuse data with local

666
01:30:59.510 --> 01:31:09.719
MTS - AV: regional CCTLD managers like PANDI here in Indonesia, and local registrars to help them detect these fast-rotating infrastructures.

667
01:31:09.750 --> 01:31:10.639
MTS - AV: Thank you.

668
01:31:11.990 --> 01:31:19.819
MTS - AV: Interesting question. So… On a planet far, far away, many years ago.

669
01:31:21.650 --> 01:31:31.890
MTS - AV: Some of us made a recommendation that there might be a need for a… industry… Cert.

670
01:31:32.460 --> 01:31:36.019
MTS - AV: Of some kind, where exactly that kind of thing could happen.

671
01:31:36.640 --> 01:31:44.970
MTS - AV: The scars have mostly healed, from the beatings that we took for suggesting that some 15 or so years ago.

672
01:31:46.000 --> 01:31:57.550
MTS - AV: I don't think the industry was ready for that kind of data processing and telemetry. What we didn't suggest back then was that ICANN did that. We just suggested it probably needed to exist.

673
01:31:58.110 --> 01:32:03.829
MTS - AV: I think The industry itself has actually got a lot better at.

674
01:32:04.040 --> 01:32:06.430
MTS - AV: Intel sharing, etc.

675
01:32:08.260 --> 01:32:09.870
MTS - AV: I don't see as…

676
01:32:10.440 --> 01:32:21.280
MTS - AV: gathering and making decisions about what is and is not abuse, and then sharing intel. I don't think the community wants ICANN to do that.

677
01:32:21.510 --> 01:32:22.559
MTS - AV: But I'm…

678
01:32:23.540 --> 01:32:34.690
MTS - AV: a big advocate of sharing that kind of information and the need for the communities to get together and work on these… I mean, you know, if you're a small…

679
01:32:35.460 --> 01:32:42.770
MTS - AV: CCTLD operator or TLD operator, you're not going to have the skill sets. Now, many of us…

680
01:32:43.110 --> 01:32:56.530
MTS - AV: are members of organizations like FIRST, which is the Forum for Incident Response Units. It's a global body. They do information sharing. So I don't see a role where ICANN steps into there.

681
01:32:56.840 --> 01:33:03.829
MTS - AV: I could be wrong. You know, if next year the community came out and said that we need ICANN to do this, then…

682
01:33:04.360 --> 01:33:07.269
MTS - AV: we'd be in a different world, but I don't see it.

683
01:33:08.020 --> 01:33:12.490
MTS - AV: We we're a member of first. We work in

684
01:33:13.430 --> 01:33:17.279
MTS - AV: Most of the environments where that takes place.

685
01:33:17.740 --> 01:33:20.040
MTS - AV: You know, you may be familiar with

686
01:33:20.280 --> 01:33:31.980
MTS - AV: places like Morgue and APWG and many other of these security forums. We do participate in most of those, but we're typically not a source of data.

687
01:33:32.520 --> 01:33:38.850
MTS - AV: we focused on pushing science rather than becoming a data source. It just turns out that some of the data we use

688
01:33:39.150 --> 01:33:45.670
MTS - AV: is shareable. So the things like we have in Metrica, if you're a TLD and you're CCTLD and you want to participate.

689
01:33:45.780 --> 01:33:47.040
MTS - AV: Absolutely.

690
01:33:47.330 --> 01:34:01.949
MTS - AV: Give us the data we need to do the analysis, we'll share the data with you. Absolutely, we… it's not that we're against it, it's just that's not what the community's asked us to do. But I'm a big fan of, like, data sharing.

691
01:34:02.220 --> 01:34:12.780
MTS - AV: In the modern world, all the privacy issues around data sharing, everything has got much, much more complicated. But…

692
01:34:12.930 --> 01:34:17.670
MTS - AV: The operational security communities have found ways mostly to deal with that.

693
01:34:18.630 --> 01:34:20.430
MTS - AV: Love to sit and have a coffee, and…

694
01:34:20.810 --> 01:34:24.939
MTS - AV: Talk about this at some point, because you just happened to hit on one of my hobbies, so…

695
01:34:25.560 --> 01:34:31.870
MTS - AV: Thank you very much, and our appreciation to John and Kim for being with us.

696
01:34:31.870 --> 01:34:46.570
MTS - AV: And having this very interactive and interesting session. With that, we are closing this session, and I'm looking forward to seeing you back at 1.15 to talk about how policy works in ICANN. See you back!