WEBVTT - Can the Internet Handle the Imminent Streaming Explosion?

0:00:06.680 --> 0:00:10.399
<v Speaker 1>Welcome to another episode of Strictly Business, the podcast in

0:00:10.440 --> 0:00:12.520
<v Speaker 1>which we talk with some of the brightest minds working

0:00:12.520 --> 0:00:15.920
<v Speaker 1>in the media business. Today. I'm Andrew Wallenstein with Variety.

0:00:16.720 --> 0:00:19.320
<v Speaker 1>With all the talk about all the new streaming services

0:00:19.320 --> 0:00:21.800
<v Speaker 1>coming to market in the coming months, here's a question

0:00:21.880 --> 0:00:25.040
<v Speaker 1>you don't hear much. Is the Internet capable of hosting

0:00:25.040 --> 0:00:28.440
<v Speaker 1>this explosion of video and games? My guest today I

0:00:28.440 --> 0:00:31.040
<v Speaker 1>had some thoughts on the matter. He's Tom Layton, CEO

0:00:31.160 --> 0:00:34.320
<v Speaker 1>of acam I, one of the leading company's media businesses

0:00:34.400 --> 0:00:36.760
<v Speaker 1>turned to to make sure their content makes it to

0:00:36.840 --> 0:00:40.239
<v Speaker 1>consumers quickly and safely. Thanks for coming in, Tom, It's

0:00:40.320 --> 0:00:42.400
<v Speaker 1>nice to be here. Thank you, and I'm glad to

0:00:42.440 --> 0:00:44.839
<v Speaker 1>have you here because I think here in Hollywood we

0:00:44.920 --> 0:00:48.360
<v Speaker 1>don't talk enough about streaming distribution, and I think the

0:00:48.360 --> 0:00:51.760
<v Speaker 1>problem stems apart from a lack of education. So I

0:00:51.800 --> 0:00:54.840
<v Speaker 1>want to start really simple. I want you to just explain,

0:00:55.320 --> 0:00:58.320
<v Speaker 1>as they say on Reddit, as if I'm five, what

0:00:58.600 --> 0:01:02.400
<v Speaker 1>exactly does acam I do for its media business clients.

0:01:02.840 --> 0:01:05.800
<v Speaker 1>We actually deliver a lot of that streaming and the

0:01:05.880 --> 0:01:08.720
<v Speaker 1>videos that you watch online. You know, people don't think

0:01:08.720 --> 0:01:11.319
<v Speaker 1>about it. They turn on the TV or or the

0:01:11.360 --> 0:01:13.560
<v Speaker 1>device and click on what they want to watch and

0:01:13.600 --> 0:01:17.319
<v Speaker 1>it shows up. But how it's actually getting there is

0:01:17.360 --> 0:01:21.479
<v Speaker 1>a lot different with online streaming than it would be

0:01:21.520 --> 0:01:25.399
<v Speaker 1>with a cable or satellite, and it does beg the

0:01:25.480 --> 0:01:29.360
<v Speaker 1>question and concern and whether the Internet can handle the

0:01:29.480 --> 0:01:33.480
<v Speaker 1>growth of all the video traffic that's coming online and

0:01:33.520 --> 0:01:37.680
<v Speaker 1>also the cost. You know, one of the big differences

0:01:37.720 --> 0:01:42.080
<v Speaker 1>with the online version of streaming and the satellite version

0:01:43.360 --> 0:01:45.679
<v Speaker 1>is that with satellite, all you had to do was

0:01:45.680 --> 0:01:48.080
<v Speaker 1>send the TV show or the stream up to the

0:01:48.120 --> 0:01:51.720
<v Speaker 1>satellite and then people could tune in, and every extra

0:01:51.800 --> 0:01:56.000
<v Speaker 1>person that tuned in wouldn't cost anything more because you

0:01:56.080 --> 0:01:58.680
<v Speaker 1>paid a lot to get the satellite. But after that

0:01:58.800 --> 0:02:01.280
<v Speaker 1>it was free for people to turn on TVs and

0:02:01.280 --> 0:02:03.559
<v Speaker 1>you didn't have to worry about how many or any

0:02:03.560 --> 0:02:07.160
<v Speaker 1>congestion with the satellite. But the Internet is very different.

0:02:07.200 --> 0:02:10.560
<v Speaker 1>For everybody who's turning on there's a computer somewhere and

0:02:10.639 --> 0:02:15.040
<v Speaker 1>the Internet that is sending you your stream just for you.

0:02:15.800 --> 0:02:18.639
<v Speaker 1>And so if you've got you know, ten million people watching,

0:02:19.160 --> 0:02:23.440
<v Speaker 1>well there's ten million streams being created and being sent

0:02:23.560 --> 0:02:26.760
<v Speaker 1>over the Internet, and that is a lot of traffic,

0:02:27.360 --> 0:02:30.600
<v Speaker 1>and every stream costs money to send on the Internet.

0:02:30.680 --> 0:02:33.000
<v Speaker 1>And that's where Akamy comes in. Uh. You know, we

0:02:33.080 --> 0:02:37.359
<v Speaker 1>have a a much better way of getting all those

0:02:37.440 --> 0:02:42.280
<v Speaker 1>videos and streams and broadcasts to the end user. Uh,

0:02:42.360 --> 0:02:45.480
<v Speaker 1>so that it's more cost effective, it can scale, and

0:02:45.480 --> 0:02:48.520
<v Speaker 1>that it comes in good quality. And the vision that

0:02:48.560 --> 0:02:51.079
<v Speaker 1>I have as you speak, I almost picture of the

0:02:51.120 --> 0:02:54.040
<v Speaker 1>cloud or the pipes of the Internet is a mountain,

0:02:54.080 --> 0:02:56.960
<v Speaker 1>and you guys are like the sherpa taking the media

0:02:57.080 --> 0:03:00.200
<v Speaker 1>client in there. I mean, is it that? I know?

0:03:00.400 --> 0:03:03.080
<v Speaker 1>I'm curious even about the dynamic with you guys and

0:03:03.160 --> 0:03:06.400
<v Speaker 1>media companies. Do they need an ACAM? I could they

0:03:06.400 --> 0:03:09.400
<v Speaker 1>just build their own network out? I mean, how essential

0:03:09.440 --> 0:03:13.360
<v Speaker 1>are you to this? Pretty essential? Very very few companies

0:03:13.400 --> 0:03:16.760
<v Speaker 1>try to build their own because it's really hard to do.

0:03:17.360 --> 0:03:19.839
<v Speaker 1>You know. The concept behind what we do is that

0:03:20.320 --> 0:03:25.959
<v Speaker 1>say there's a hundred people watching a show in your neighborhood. Uh,

0:03:26.040 --> 0:03:30.160
<v Speaker 1>you know, without Akama, you'd be sending that signal that

0:03:30.320 --> 0:03:33.680
<v Speaker 1>stream in a hundred times and it could start to

0:03:34.040 --> 0:03:36.320
<v Speaker 1>fill up the pipes in your neighborhood, so that you

0:03:36.320 --> 0:03:39.560
<v Speaker 1>couldn't get a good experience. With Akama, you know, we've

0:03:39.600 --> 0:03:44.000
<v Speaker 1>placed our computer server already in your neighborhood, and we'll

0:03:44.080 --> 0:03:47.760
<v Speaker 1>just send that signal in once and there's plenty of

0:03:47.880 --> 0:03:50.520
<v Speaker 1>room to send it once, and from there we'll fan

0:03:50.600 --> 0:03:53.440
<v Speaker 1>it out and get each person and reach you know,

0:03:53.640 --> 0:03:58.080
<v Speaker 1>viewer in their homes or offices their copy locally. Uh,

0:03:58.200 --> 0:04:01.160
<v Speaker 1>So that you're not trying to and ultimately at scale,

0:04:01.840 --> 0:04:05.240
<v Speaker 1>trying to send millions and millions or you know, someday

0:04:05.320 --> 0:04:07.880
<v Speaker 1>hundreds of millions of copies of the signal from some

0:04:08.240 --> 0:04:10.640
<v Speaker 1>core spot on the Internet. The Internet just couldn't handle

0:04:10.640 --> 0:04:13.720
<v Speaker 1>it already. The Internet is congested and the peering points.

0:04:14.720 --> 0:04:17.919
<v Speaker 1>But with Akamai, it does enable it to scale, and

0:04:17.960 --> 0:04:21.240
<v Speaker 1>it makes it less expensive because you're not sending the

0:04:21.279 --> 0:04:24.640
<v Speaker 1>signal from far away using up pipes that are really

0:04:24.680 --> 0:04:28.560
<v Speaker 1>expensive across the country. You're sending it locally and the

0:04:28.600 --> 0:04:32.080
<v Speaker 1>pipes they're much shorter and less expensive. So here we

0:04:32.200 --> 0:04:35.560
<v Speaker 1>are in the early days of the so called streaming wars,

0:04:35.680 --> 0:04:38.920
<v Speaker 1>where the video market that may have been dominated by

0:04:38.920 --> 0:04:42.880
<v Speaker 1>saying Netflix, Amazon, and you know, the established media companies.

0:04:43.200 --> 0:04:48.440
<v Speaker 1>Now we're seeing these Netflix rivals come in, uh, Comcast, Time, Warner,

0:04:48.600 --> 0:04:52.080
<v Speaker 1>I'm sorry, A T and T old Habits die hard, Apple,

0:04:52.640 --> 0:04:56.480
<v Speaker 1>so many players coming in here. Does this even represent

0:04:56.760 --> 0:05:01.080
<v Speaker 1>this kind of step change moment where the volume of

0:05:01.240 --> 0:05:03.440
<v Speaker 1>video that you guys are going to have the sort

0:05:03.440 --> 0:05:07.680
<v Speaker 1>of shepherd becomes much more difficult. Yeah, I think the

0:05:07.760 --> 0:05:11.200
<v Speaker 1>volume levels are growing dramatically, and I think with the

0:05:11.240 --> 0:05:14.240
<v Speaker 1>advent of these new O T T offers, which look

0:05:14.279 --> 0:05:17.440
<v Speaker 1>pretty compelling in terms of the content, more and more

0:05:17.440 --> 0:05:21.240
<v Speaker 1>watching will be done online and they'll be you'll watch

0:05:21.240 --> 0:05:24.680
<v Speaker 1>it higher quality levels. Uh. And people don't think about it,

0:05:24.680 --> 0:05:27.400
<v Speaker 1>but if you get the h D version, that takes

0:05:27.400 --> 0:05:30.440
<v Speaker 1>a lot more traffic to produce that high quality image

0:05:30.520 --> 0:05:33.279
<v Speaker 1>on your screen. Uh. And so that makes the traffic

0:05:33.360 --> 0:05:35.560
<v Speaker 1>levels be even higher. And of course the more you

0:05:35.680 --> 0:05:39.040
<v Speaker 1>watch online, the more traffic it creates. So I do

0:05:39.160 --> 0:05:43.640
<v Speaker 1>think we're seeing a real spike up in traffic due

0:05:43.720 --> 0:05:47.560
<v Speaker 1>to video O T T offers online. But is it

0:05:47.640 --> 0:05:49.760
<v Speaker 1>about to get a lot worse? Is it about to

0:05:49.800 --> 0:05:53.039
<v Speaker 1>get like, let's even say there's a scenario where all

0:05:53.080 --> 0:05:55.480
<v Speaker 1>these streaming services take off like wildfire, and all of

0:05:55.520 --> 0:05:58.719
<v Speaker 1>a sudden, everyone is guzzling these news services and maybe

0:05:58.760 --> 0:06:02.360
<v Speaker 1>not quite at Netflix level, but getting there. Can acam

0:06:02.400 --> 0:06:06.400
<v Speaker 1>I can the Internet handle all this? Yeah? Acam, I

0:06:06.440 --> 0:06:08.360
<v Speaker 1>can handle it? On behalf of the Internet. I think

0:06:08.400 --> 0:06:11.400
<v Speaker 1>the Internet on its own already couldn't do it. It's

0:06:11.440 --> 0:06:14.040
<v Speaker 1>not architected to do it, and the cost would be

0:06:14.120 --> 0:06:17.159
<v Speaker 1>much too great. But we do work with all the

0:06:17.240 --> 0:06:20.920
<v Speaker 1>major OTT providers that are planning launches in a provision

0:06:20.960 --> 0:06:24.279
<v Speaker 1>capacity to handle it. And I think you're right. If

0:06:24.320 --> 0:06:27.440
<v Speaker 1>they're all popular, that's going to be a huge explosion

0:06:27.480 --> 0:06:31.280
<v Speaker 1>in traffic and uh, you know, and we're prepared for that.

0:06:31.279 --> 0:06:35.560
<v Speaker 1>That's what we do. Well, I'm assuming it's horrifically complicated,

0:06:35.880 --> 0:06:37.599
<v Speaker 1>or is it not? Is it? Is it just as

0:06:37.600 --> 0:06:39.640
<v Speaker 1>simple as look, we're's gonna have a lot of servers

0:06:39.680 --> 0:06:41.839
<v Speaker 1>and call it a day. You know, you've got to

0:06:41.839 --> 0:06:44.120
<v Speaker 1>have all the servers out there, for sure, because otherwise

0:06:44.160 --> 0:06:46.800
<v Speaker 1>you're you're dead on arrival. Uh. And you've got to

0:06:46.800 --> 0:06:50.000
<v Speaker 1>have them strategically located. You've got to be in all

0:06:50.040 --> 0:06:52.599
<v Speaker 1>the neighborhoods, you know, And we locate our servers in

0:06:52.640 --> 0:06:56.120
<v Speaker 1>four thousand places in a thousand cities. You can't just

0:06:56.240 --> 0:06:58.440
<v Speaker 1>have one on the East coast or something that just

0:06:58.480 --> 0:07:02.640
<v Speaker 1>doesn't doesn't work. But it's more than just that. It

0:07:02.839 --> 0:07:06.400
<v Speaker 1>is very complicated because well, you in this country, you've

0:07:06.440 --> 0:07:09.000
<v Speaker 1>got hundreds of millions of people. Globally, You've got billions

0:07:09.000 --> 0:07:11.920
<v Speaker 1>of people and a lot of people are watching different

0:07:11.960 --> 0:07:14.800
<v Speaker 1>things at different times, and they've all got to get

0:07:14.840 --> 0:07:19.560
<v Speaker 1>a good experience. And so managing that efficiently UH does

0:07:19.720 --> 0:07:22.800
<v Speaker 1>take a lot of effort, and it has to have

0:07:22.880 --> 0:07:25.680
<v Speaker 1>real time response, so it's all automated. You can't have

0:07:25.760 --> 0:07:29.520
<v Speaker 1>somebody deciding, Okay, somebody just wanted to watch this movie,

0:07:29.560 --> 0:07:31.400
<v Speaker 1>what server are they're going to get assigned to to

0:07:31.760 --> 0:07:36.440
<v Speaker 1>get the stream. That's a very complicated process that you know,

0:07:36.480 --> 0:07:40.080
<v Speaker 1>we've been perfecting now for over twenty years, and UH

0:07:40.280 --> 0:07:42.760
<v Speaker 1>handle pretty much all the world's major events, you know,

0:07:42.800 --> 0:07:45.640
<v Speaker 1>at scale today Already, we should make clear this is

0:07:45.640 --> 0:07:48.640
<v Speaker 1>a global service. We're not just talking about the US.

0:07:48.720 --> 0:07:50.600
<v Speaker 1>You're active, I think, and it's about a hundred and

0:07:50.640 --> 0:07:55.120
<v Speaker 1>thirty nine countries, yes, infrastructures in a hundred thirty nine countries,

0:07:55.120 --> 0:07:58.080
<v Speaker 1>in a thousand cities, and you know, people here think

0:07:58.120 --> 0:08:01.640
<v Speaker 1>about content in the States at you know, China is

0:08:01.680 --> 0:08:05.960
<v Speaker 1>probably the world's largest internet market, India probably the largest.

0:08:06.000 --> 0:08:08.320
<v Speaker 1>When it comes to watching sporting events, you know, we

0:08:08.360 --> 0:08:10.960
<v Speaker 1>think about the Super Bowl being a big deal here,

0:08:11.640 --> 0:08:15.440
<v Speaker 1>but you know, cricket they're far, far bigger. And you

0:08:15.480 --> 0:08:18.520
<v Speaker 1>look at the crowds online. You know, this past summer

0:08:18.560 --> 0:08:22.600
<v Speaker 1>for a cricket match we had twenty five million concurrent

0:08:22.720 --> 0:08:27.280
<v Speaker 1>viewers on mobile devices. Talk about a challenge for delivering

0:08:27.400 --> 0:08:30.600
<v Speaker 1>content and that just swamps out anything like the Super

0:08:30.640 --> 0:08:34.199
<v Speaker 1>Bowl here in terms of being online. You know, obviously

0:08:34.240 --> 0:08:36.400
<v Speaker 1>I'm talking to you on the eve of the streaming

0:08:36.400 --> 0:08:39.360
<v Speaker 1>war explosion. But as I think you've already alluded to,

0:08:39.720 --> 0:08:42.839
<v Speaker 1>you're already seeing increases. I think you guys just noted

0:08:42.840 --> 0:08:46.240
<v Speaker 1>earlier this month that for the first time Aclamy transmitted

0:08:46.240 --> 0:08:48.480
<v Speaker 1>over and I hope I get this data point right,

0:08:48.520 --> 0:08:52.000
<v Speaker 1>A hundred terror bytes per second. Yeah, hundred trillion bits,

0:08:52.040 --> 0:08:54.960
<v Speaker 1>hundred terror bits per second. We got these numbers so

0:08:55.080 --> 0:08:57.160
<v Speaker 1>large you can't even think about it. Well, but here's

0:08:57.160 --> 0:09:00.120
<v Speaker 1>an interesting comparison. It's supposedly the same as download in

0:09:00.320 --> 0:09:04.400
<v Speaker 1>thirty three hundred two hour HD movies every second. Yeah,

0:09:04.440 --> 0:09:07.200
<v Speaker 1>that kind of puts in perspective. That does. Or you

0:09:07.200 --> 0:09:11.920
<v Speaker 1>can think about a day every day now we're delivering

0:09:12.120 --> 0:09:15.559
<v Speaker 1>traffic that would be the same as two hundred million

0:09:15.640 --> 0:09:22.040
<v Speaker 1>DVDs or eight hundred billion web pages including all the pictures.

0:09:22.720 --> 0:09:26.240
<v Speaker 1>The numbers are staggering, and as you know, I think

0:09:26.240 --> 0:09:28.440
<v Speaker 1>the exciting part is this is the tip of the iceberg,

0:09:28.920 --> 0:09:31.320
<v Speaker 1>as big as it is now. We're in the very

0:09:31.360 --> 0:09:35.960
<v Speaker 1>early days of everything just moving online. And also we're

0:09:36.120 --> 0:09:39.800
<v Speaker 1>largely talking about on demand content, but more and more,

0:09:39.840 --> 0:09:42.080
<v Speaker 1>and I'm sure you're seeing this with your clients both

0:09:42.200 --> 0:09:48.480
<v Speaker 1>here and internationally. Live content, particularly sports. I assume there's

0:09:48.480 --> 0:09:51.840
<v Speaker 1>an added demand there. And yet we're on the verge

0:09:51.960 --> 0:09:54.480
<v Speaker 1>of probably an era not too far in the future

0:09:54.480 --> 0:09:57.160
<v Speaker 1>where we could see some of the streaming companies take

0:09:57.240 --> 0:10:02.160
<v Speaker 1>over the rights to major sports, be at NFL, nb A, whatnot.

0:10:02.679 --> 0:10:06.160
<v Speaker 1>Uh Are we at a place where the demand or

0:10:06.200 --> 0:10:08.960
<v Speaker 1>sorry not the demand, just the capacity for that is

0:10:09.000 --> 0:10:13.120
<v Speaker 1>even possible, Yeah, you know, and doing it live is

0:10:13.160 --> 0:10:16.880
<v Speaker 1>even harder. If it's v O D, you can get

0:10:16.880 --> 0:10:19.320
<v Speaker 1>a copy of the show ahead of time and store

0:10:19.360 --> 0:10:22.240
<v Speaker 1>it in the neighborhood and then it's ready when somebody

0:10:22.320 --> 0:10:24.160
<v Speaker 1>wants to see it there. When it's live, you don't

0:10:24.200 --> 0:10:27.280
<v Speaker 1>have it ahead of time, and increasingly you want to

0:10:27.320 --> 0:10:31.040
<v Speaker 1>see it in real time, which means it just has

0:10:31.080 --> 0:10:33.640
<v Speaker 1>to becoming streamed and you got to fan it out

0:10:33.679 --> 0:10:37.160
<v Speaker 1>everywhere around the world. That's that's a lot harder to do,

0:10:37.920 --> 0:10:41.040
<v Speaker 1>and also it drives a lot of traffic because people

0:10:41.120 --> 0:10:43.800
<v Speaker 1>want to see it all at the same time, as

0:10:43.800 --> 0:10:47.120
<v Speaker 1>opposed to spreading it out of course the across an evening.

0:10:47.400 --> 0:10:51.559
<v Speaker 1>Say so, that puts a lot of pressure on the internet. Now,

0:10:52.040 --> 0:10:55.960
<v Speaker 1>live traditionally has been done on TV through satellite, More

0:10:56.040 --> 0:10:58.520
<v Speaker 1>and more it's it's online. And some of the world's

0:10:58.559 --> 0:11:02.240
<v Speaker 1>major broadcasters now are envisioning the day when it's probably

0:11:02.280 --> 0:11:05.520
<v Speaker 1>still ten years out, but they won't be using satellites anymore.

0:11:06.080 --> 0:11:09.840
<v Speaker 1>It'll all be online. And that's a pretty interesting concept,

0:11:09.880 --> 0:11:12.400
<v Speaker 1>you know. I think five years ago nobody thought that

0:11:12.440 --> 0:11:14.600
<v Speaker 1>would ever happen. You go back ten years ago and

0:11:14.640 --> 0:11:17.240
<v Speaker 1>nobody thought you'd ever watch a sporting event online. Why

0:11:17.280 --> 0:11:20.800
<v Speaker 1>would you have TV? Well, we all do now, and

0:11:20.840 --> 0:11:23.120
<v Speaker 1>we're to the point now where people are thinking it'll

0:11:23.200 --> 0:11:26.560
<v Speaker 1>all be online at some point. I mean, we're having

0:11:26.559 --> 0:11:29.720
<v Speaker 1>a very video centric conversation. But let's not forget there's

0:11:29.760 --> 0:11:34.360
<v Speaker 1>more than just video on the internet. Healthcare, banking, all

0:11:34.400 --> 0:11:38.640
<v Speaker 1>sorts of different kind of industries that create congestion of

0:11:38.760 --> 0:11:42.319
<v Speaker 1>various kinds. So I guess I want to understand videos

0:11:42.400 --> 0:11:46.480
<v Speaker 1>place in the overall sort of band with picture. Is

0:11:46.520 --> 0:11:49.480
<v Speaker 1>it like, you know, the main band with hog or

0:11:49.520 --> 0:11:51.200
<v Speaker 1>are we actually kind of missing the forest for the

0:11:51.240 --> 0:11:53.680
<v Speaker 1>trees here and there's other things going on that videos

0:11:53.720 --> 0:11:56.840
<v Speaker 1>is a little piker. Well, if you're talking about bandwidth

0:11:56.840 --> 0:12:00.520
<v Speaker 1>our total traffic, there's two big hawks and they have

0:12:00.559 --> 0:12:05.760
<v Speaker 1>almost all the traffic, and that would be video and software. Now,

0:12:05.880 --> 0:12:09.400
<v Speaker 1>people don't think about software, but if you're playing Fortnite,

0:12:09.960 --> 0:12:13.080
<v Speaker 1>you know, on a regular basis, you're downloading a gigantic

0:12:13.200 --> 0:12:17.000
<v Speaker 1>chunk of software to play it. Or all those apps

0:12:17.320 --> 0:12:20.000
<v Speaker 1>you have on your mobile device, they all have a

0:12:20.040 --> 0:12:23.240
<v Speaker 1>pretty decent sized chunk of software and they're trying to

0:12:23.320 --> 0:12:25.720
<v Speaker 1>update it all the time. And so I would say

0:12:25.760 --> 0:12:30.240
<v Speaker 1>today the big consumers would be updating software on your

0:12:30.280 --> 0:12:34.040
<v Speaker 1>devices and video. Now, in the long run, probably video

0:12:34.160 --> 0:12:38.240
<v Speaker 1>takes over, but today they're they're equal in terms of

0:12:38.840 --> 0:12:43.239
<v Speaker 1>you know, total traffic. You're banking transaction, buying something online?

0:12:43.920 --> 0:12:47.760
<v Speaker 1>Tiny tiny tiny, Uh, Now there's a lot of back

0:12:47.760 --> 0:12:51.440
<v Speaker 1>and forth. It's a very important transaction. Uh. Security is

0:12:51.520 --> 0:12:54.840
<v Speaker 1>really important if you're buying something or you're doing banking online.

0:12:54.880 --> 0:12:58.480
<v Speaker 1>But in terms of traffic volume tiny, And we'll get

0:12:58.520 --> 0:13:02.280
<v Speaker 1>to security in a second. You know, you mentioned Fortnite,

0:13:02.280 --> 0:13:05.560
<v Speaker 1>and I'm curious, does one I think we can call

0:13:05.600 --> 0:13:09.959
<v Speaker 1>it a phenomenon like that have a discernible impact on

0:13:10.000 --> 0:13:12.960
<v Speaker 1>the networks that you're handling. You can, can you see

0:13:13.040 --> 0:13:16.520
<v Speaker 1>one thing that becomes so popular that you have to

0:13:16.520 --> 0:13:20.000
<v Speaker 1>sort of focus on the impact of just this one property.

0:13:20.280 --> 0:13:23.960
<v Speaker 1>Oh yeah, we worry a lot about having the scale

0:13:24.080 --> 0:13:28.040
<v Speaker 1>ready for a gaming, big gaming release. Uh. You know,

0:13:28.160 --> 0:13:31.760
<v Speaker 1>something like that can drive tens and tens of teara

0:13:31.840 --> 0:13:35.000
<v Speaker 1>bits per second, you know, which is a lot. You know,

0:13:35.160 --> 0:13:40.319
<v Speaker 1>it's thirty forty fifty trillion bits a second on the internet. Uh,

0:13:40.600 --> 0:13:44.079
<v Speaker 1>so that's a that's a whopper, and that today those

0:13:44.400 --> 0:13:48.280
<v Speaker 1>peak flash crowds for big gaming releases are bigger than

0:13:49.280 --> 0:13:54.800
<v Speaker 1>the big sporting events or big video releases today, you know,

0:13:54.840 --> 0:13:58.200
<v Speaker 1>maybe by about a factor of two. Now, overall traffic

0:13:58.240 --> 0:14:00.840
<v Speaker 1>probably get more from video, and I think long run

0:14:01.559 --> 0:14:05.400
<v Speaker 1>video takes over. But we worry a lot about a

0:14:05.440 --> 0:14:08.839
<v Speaker 1>particular gaming release from the big guys. I'm actually surprised,

0:14:09.000 --> 0:14:12.800
<v Speaker 1>given you know, the bulk that software represents, that in

0:14:12.800 --> 0:14:16.080
<v Speaker 1>the longer term, that's not a bigger threat than video,

0:14:16.400 --> 0:14:19.640
<v Speaker 1>particularly because you know we're here talking about the streaming wars,

0:14:19.680 --> 0:14:21.680
<v Speaker 1>but we've got another war coming soon in terms of

0:14:21.760 --> 0:14:25.360
<v Speaker 1>cloud gaming, lots of news services from big companies like

0:14:25.440 --> 0:14:29.680
<v Speaker 1>Google Stadia. Is all that going to be okay? Because that,

0:14:29.800 --> 0:14:32.760
<v Speaker 1>to me, what do I know, seems to be uh,

0:14:32.800 --> 0:14:36.200
<v Speaker 1>maybe a bigger kettle of fish. That's a great question.

0:14:36.400 --> 0:14:38.800
<v Speaker 1>You know, today with gaming, the traffic is just getting

0:14:38.800 --> 0:14:41.880
<v Speaker 1>the software there, and you only do it once a month, say,

0:14:42.040 --> 0:14:46.160
<v Speaker 1>or maybe there's updated releases on a weekly basis. But

0:14:46.240 --> 0:14:49.520
<v Speaker 1>as you think about the future, if the video that

0:14:49.600 --> 0:14:53.160
<v Speaker 1>produces the experience on your screen is coming from the

0:14:53.200 --> 0:14:56.320
<v Speaker 1>cloud as opposed to being created on your device, which

0:14:56.360 --> 0:14:59.560
<v Speaker 1>is how it's done you know today, that could create

0:14:59.600 --> 0:15:02.680
<v Speaker 1>a lot of traffic. Now, the question is will that

0:15:02.760 --> 0:15:07.040
<v Speaker 1>ever really be viable commercially? Uh? And people have been

0:15:07.080 --> 0:15:10.440
<v Speaker 1>thinking about streaming the game to your device that you're

0:15:10.440 --> 0:15:12.560
<v Speaker 1>actually playing it in what you see on your device

0:15:12.640 --> 0:15:15.960
<v Speaker 1>comes from the cloud for over a decade. It's never

0:15:16.080 --> 0:15:19.720
<v Speaker 1>really proved financially viable because now you've got to do

0:15:19.760 --> 0:15:22.120
<v Speaker 1>the heavy duty compute in the cloud and you're streaming

0:15:22.120 --> 0:15:25.960
<v Speaker 1>an experience just for that user. It's got to have

0:15:26.080 --> 0:15:29.440
<v Speaker 1>really low latency, especially if it's a multiplayer game and

0:15:29.560 --> 0:15:33.480
<v Speaker 1>has to be a rich experience, and that's that's expensive. Uh,

0:15:33.640 --> 0:15:37.440
<v Speaker 1>So we'll see, you know how viable that is. Doesn't

0:15:37.440 --> 0:15:40.880
<v Speaker 1>really take off, but the right commercial models there that

0:15:40.960 --> 0:15:43.160
<v Speaker 1>hasn't been successful yet, so we'll see if if that

0:15:43.240 --> 0:15:47.040
<v Speaker 1>will change. I just wonder listening to all this, the

0:15:47.120 --> 0:15:50.760
<v Speaker 1>incredible demand that all these news services of various kinds

0:15:50.760 --> 0:15:55.160
<v Speaker 1>you're gonna have on the cloud and so forth, is

0:15:55.200 --> 0:15:58.160
<v Speaker 1>there like a worst case scenario that consumers need to

0:15:58.200 --> 0:16:01.000
<v Speaker 1>keep in mind here? Could are you kept up nights

0:16:01.040 --> 0:16:03.520
<v Speaker 1>by the notion that we could see something like a

0:16:03.680 --> 0:16:06.360
<v Speaker 1>giant outage? Or at the end of the day, is

0:16:06.400 --> 0:16:11.520
<v Speaker 1>the Internet maybe more nimble, more capable than we're giving

0:16:11.520 --> 0:16:13.880
<v Speaker 1>it credit? Well, our job at ocam I is to

0:16:13.960 --> 0:16:16.880
<v Speaker 1>make the Internet be okay here, to make it scale,

0:16:16.960 --> 0:16:20.400
<v Speaker 1>to make it be fast, intelligent and secure, and that's

0:16:20.400 --> 0:16:23.480
<v Speaker 1>what we do as a business. The Internet by itself

0:16:23.560 --> 0:16:27.040
<v Speaker 1>is not nimble. Uh. It would already be in big

0:16:27.080 --> 0:16:30.560
<v Speaker 1>trouble in terms of just the traffic that's there today,

0:16:30.600 --> 0:16:33.160
<v Speaker 1>and it doesn't have any security. I'm bet it at all.

0:16:33.600 --> 0:16:36.840
<v Speaker 1>You know. That's the kind of capabilities that ocamy adds

0:16:36.880 --> 0:16:40.960
<v Speaker 1>in on behalf of our customers who are the major enterprises,

0:16:41.000 --> 0:16:44.080
<v Speaker 1>the major banks, the major commerce companies, the major media

0:16:44.120 --> 0:16:47.480
<v Speaker 1>and gaming companies. UH. And so it's up to companies

0:16:47.520 --> 0:16:51.240
<v Speaker 1>to provide that capability to help make it work in

0:16:51.280 --> 0:16:54.080
<v Speaker 1>the future. But why is it? It sounds like the

0:16:54.080 --> 0:16:57.800
<v Speaker 1>Internet is almost like this, you know, infrastructure that is

0:16:57.840 --> 0:17:00.800
<v Speaker 1>just slowly rotting, and it's good that acomy is there

0:17:00.800 --> 0:17:03.920
<v Speaker 1>to to help sort of pave over the rough spots.

0:17:04.400 --> 0:17:07.439
<v Speaker 1>And so I'm curious, why is that, I mean, is

0:17:07.520 --> 0:17:10.439
<v Speaker 1>there Why aren't we seeing an Internet that, as it

0:17:10.480 --> 0:17:14.880
<v Speaker 1>gets older, is better paved roads. The Internet is not rotting,

0:17:15.800 --> 0:17:19.840
<v Speaker 1>but it's a it's a fixed infrastructure. It's growing. Companies,

0:17:19.880 --> 0:17:22.840
<v Speaker 1>the telcos have to put a lot of money to

0:17:22.920 --> 0:17:25.919
<v Speaker 1>add more pipe and they the last mile is getting

0:17:25.920 --> 0:17:30.000
<v Speaker 1>better and better. UH. And consumers at home offices pay

0:17:30.119 --> 0:17:32.000
<v Speaker 1>to have a better last mile link. A lot of

0:17:32.000 --> 0:17:34.399
<v Speaker 1>homes now in many cities have gig a bit per

0:17:34.400 --> 0:17:37.040
<v Speaker 1>second coming into the home. UH. You look at five

0:17:37.119 --> 0:17:40.879
<v Speaker 1>g and that will give a much better experience across

0:17:40.920 --> 0:17:44.080
<v Speaker 1>the last mile. So improvements are being made to it,

0:17:44.440 --> 0:17:48.320
<v Speaker 1>but the fundamental protocols don't really change very much, and

0:17:48.359 --> 0:17:52.440
<v Speaker 1>that's a very slow process. Security is not inherently embedded.

0:17:52.640 --> 0:17:55.920
<v Speaker 1>Was never designed into the Internet. Uh, it was not

0:17:56.560 --> 0:18:01.560
<v Speaker 1>built to scale to you know, deliver you know, hundreds

0:18:01.560 --> 0:18:05.600
<v Speaker 1>of millions of concurrent viewers video high quality video from

0:18:05.600 --> 0:18:09.240
<v Speaker 1>a central location. That whole it wasn't it's it can't

0:18:09.240 --> 0:18:12.080
<v Speaker 1>do that, and so you do need companies to come

0:18:12.119 --> 0:18:15.440
<v Speaker 1>in and take what's there, which is very valuable. It's

0:18:15.240 --> 0:18:19.160
<v Speaker 1>it's good, but to make it work for these applications

0:18:19.160 --> 0:18:21.679
<v Speaker 1>we're thinking about now, and to make it be secure,

0:18:21.720 --> 0:18:25.160
<v Speaker 1>because it's it's not set up to be secure. And

0:18:25.440 --> 0:18:27.800
<v Speaker 1>digging a little deeper into security, what does that mean

0:18:27.840 --> 0:18:31.560
<v Speaker 1>from a media perspective, This is a business that gets

0:18:31.600 --> 0:18:34.919
<v Speaker 1>impacted in all sorts of ways by security issues, whether

0:18:35.000 --> 0:18:38.240
<v Speaker 1>it's piracy that seems to be a scourge that just

0:18:38.280 --> 0:18:42.520
<v Speaker 1>doesn't go away to you know, notorious incidents like the

0:18:42.560 --> 0:18:47.199
<v Speaker 1>Sony hack where uh, you know, massive amounts of data

0:18:47.760 --> 0:18:51.679
<v Speaker 1>privacies are compromised. Um. Does ACA might get involved in

0:18:51.720 --> 0:18:54.159
<v Speaker 1>all ends of of security when it comes to the

0:18:54.240 --> 0:18:57.879
<v Speaker 1>media businesses, Yeah, pretty much. Um. You know, and you

0:18:57.960 --> 0:19:01.159
<v Speaker 1>have denial of service attacks, you know, a website or

0:19:01.200 --> 0:19:04.119
<v Speaker 1>a news site is brought down, you have data corruption.

0:19:04.359 --> 0:19:07.000
<v Speaker 1>This is where you go into a news site, for example,

0:19:07.320 --> 0:19:11.600
<v Speaker 1>and you change the content. Some pretty famous examples of that.

0:19:12.359 --> 0:19:15.840
<v Speaker 1>Very dangerous when you start changing what the news is

0:19:16.440 --> 0:19:19.320
<v Speaker 1>on a site that people would would trust in. You

0:19:19.440 --> 0:19:23.800
<v Speaker 1>have account takeover. Uh. That's really bad for banks, you know,

0:19:23.920 --> 0:19:25.760
<v Speaker 1>when you have your bank account taken over and a

0:19:25.880 --> 0:19:31.359
<v Speaker 1>criminal organization drains the funds. Uh. You know, that was

0:19:31.440 --> 0:19:33.800
<v Speaker 1>not thought to be something that media companies had to

0:19:33.840 --> 0:19:36.520
<v Speaker 1>worry about in the past, but now in the last

0:19:36.640 --> 0:19:39.440
<v Speaker 1>year they've been targeted so that your O T T

0:19:39.560 --> 0:19:43.320
<v Speaker 1>account gets stolen, your gaming account where you've built up

0:19:43.359 --> 0:19:47.680
<v Speaker 1>all these tools or weapons or prizes or whatever. Those

0:19:47.720 --> 0:19:51.920
<v Speaker 1>have monetary value with real dollars now and there's a

0:19:51.960 --> 0:19:55.440
<v Speaker 1>black market for that, and you know, somebody hacks your account,

0:19:55.520 --> 0:19:59.960
<v Speaker 1>steals all your stuff and then sells it online. We're seeing,

0:20:00.160 --> 0:20:03.359
<v Speaker 1>you know, massive attacks on people's accounts to take them over.

0:20:03.400 --> 0:20:06.760
<v Speaker 1>With media companies. Now, you mentioned the Sony hack as

0:20:06.800 --> 0:20:10.200
<v Speaker 1>an enterprise. Media companies have a lot of sensitive information

0:20:10.920 --> 0:20:13.399
<v Speaker 1>and there's third parties that go in there and steal

0:20:13.440 --> 0:20:15.920
<v Speaker 1>that and then can publish it or do other things

0:20:16.040 --> 0:20:19.120
<v Speaker 1>with it. Those are all things that acam I you know,

0:20:19.600 --> 0:20:22.760
<v Speaker 1>is working to stop and building you know, services to

0:20:22.880 --> 0:20:26.760
<v Speaker 1>keep from happening. Uh, it's a it's an interesting challenge

0:20:26.760 --> 0:20:29.080
<v Speaker 1>on a daily basis. And it's interesting to hear you

0:20:29.119 --> 0:20:31.040
<v Speaker 1>say that this has become a bigger problem in the

0:20:31.040 --> 0:20:34.320
<v Speaker 1>past here, because frankly, at least in my circles, nobody's

0:20:34.320 --> 0:20:37.080
<v Speaker 1>talking about it here in Hollywood. And I'm curious, is

0:20:37.080 --> 0:20:39.960
<v Speaker 1>it because these media businesses don't understand these issues, don't

0:20:39.960 --> 0:20:43.440
<v Speaker 1>appreciate the gravity of these threats, because it sounds pretty

0:20:43.480 --> 0:20:46.240
<v Speaker 1>damn serious. Oh, I can assure you that big company

0:20:46.359 --> 0:20:48.639
<v Speaker 1>media c s, O S, c I O s and

0:20:48.680 --> 0:20:52.920
<v Speaker 1>increasingly CEOs are worried about it. Uh, And certainly when

0:20:52.920 --> 0:20:55.600
<v Speaker 1>you get into data breaches things like happen with Sony there,

0:20:55.840 --> 0:21:00.119
<v Speaker 1>every media CEO is worried about that our media, your

0:21:00.200 --> 0:21:04.440
<v Speaker 1>company's targeted more or less than any other industry or

0:21:04.560 --> 0:21:07.439
<v Speaker 1>is just every industry under attack these I think it

0:21:07.520 --> 0:21:11.560
<v Speaker 1>depends on the nature of the attack. For banks, Uh,

0:21:11.600 --> 0:21:16.560
<v Speaker 1>they're most worried about the accounts being taken over, you know,

0:21:16.600 --> 0:21:20.439
<v Speaker 1>And what happens there is that human beings today have

0:21:20.680 --> 0:21:24.040
<v Speaker 1>dozens of accounts online and they'll tend to use the

0:21:24.080 --> 0:21:26.680
<v Speaker 1>same log in and the same password because who can

0:21:26.720 --> 0:21:30.560
<v Speaker 1>remember dozens of different passwords and which account there on

0:21:30.680 --> 0:21:33.159
<v Speaker 1>that's you know, really hard. And then one of the

0:21:33.200 --> 0:21:37.800
<v Speaker 1>companies gets hacked, take Yahoo, and your credentials are stolen.

0:21:38.320 --> 0:21:42.120
<v Speaker 1>And then what happens is the criminal organization takes your

0:21:42.119 --> 0:21:45.560
<v Speaker 1>credential and gives it to a bot army and they

0:21:45.600 --> 0:21:48.879
<v Speaker 1>will try out your credential on every bank in the world,

0:21:48.960 --> 0:21:52.480
<v Speaker 1>every commerce site, now every media site, and they look

0:21:52.560 --> 0:21:54.360
<v Speaker 1>to see did you have an account there and did

0:21:54.400 --> 0:21:57.639
<v Speaker 1>you use the same password, And invariably they gets what

0:21:57.720 --> 0:22:00.359
<v Speaker 1>it's called a hit, which means they found a a

0:22:00.400 --> 0:22:03.879
<v Speaker 1>website where your credentials work. Then they sell that to

0:22:04.000 --> 0:22:06.760
<v Speaker 1>organize crime. A different entity comes in and drains your

0:22:06.800 --> 0:22:09.360
<v Speaker 1>bank account or buy if it's a commerce account by

0:22:09.440 --> 0:22:12.440
<v Speaker 1>something online you know, and charges it to you. And

0:22:12.600 --> 0:22:15.280
<v Speaker 1>if it's a media account you know, uses that now

0:22:15.320 --> 0:22:19.880
<v Speaker 1>to uh steal your tools, you've amassed, anything of monetary

0:22:20.160 --> 0:22:23.040
<v Speaker 1>value or other people will now be watching the video

0:22:23.200 --> 0:22:27.480
<v Speaker 1>or buying videos under your account. Uh. And this is

0:22:27.520 --> 0:22:30.800
<v Speaker 1>a So it's a big problem that started with banks

0:22:30.800 --> 0:22:33.320
<v Speaker 1>and has now moved everywhere. If you're a news site,

0:22:33.800 --> 0:22:36.800
<v Speaker 1>your most vulnerable to a doss attack which brings you

0:22:36.880 --> 0:22:40.800
<v Speaker 1>down or to data corruption, which means they change the headline,

0:22:41.119 --> 0:22:45.160
<v Speaker 1>the terrorist organization puts their message as the news headline

0:22:45.200 --> 0:22:48.240
<v Speaker 1>on your site, or they do something to embarrass somebody

0:22:48.280 --> 0:22:50.080
<v Speaker 1>because they know lots of people are coming to the

0:22:50.119 --> 0:22:52.320
<v Speaker 1>news site to see what the news is in the

0:22:52.359 --> 0:22:55.159
<v Speaker 1>front page. Story will change. I'm wondering whether we're on

0:22:55.200 --> 0:22:57.560
<v Speaker 1>the verge of seeing that kind of attack. But with

0:22:57.760 --> 0:23:01.120
<v Speaker 1>deep fake video, which could be I mean, I can't

0:23:01.160 --> 0:23:04.320
<v Speaker 1>even contemplate how awful damage like that could be done.

0:23:04.359 --> 0:23:07.240
<v Speaker 1>Is that something that does ACAM I look at things

0:23:07.240 --> 0:23:09.280
<v Speaker 1>like deep fakes and how you can stop that kind

0:23:09.280 --> 0:23:11.600
<v Speaker 1>of thing. What we do is we stop the data

0:23:11.640 --> 0:23:15.200
<v Speaker 1>corruption from happening, whatever it is. Uh. And so most

0:23:15.200 --> 0:23:18.000
<v Speaker 1>of the major media news sites around the world use

0:23:18.119 --> 0:23:21.280
<v Speaker 1>us for security. And if you you don't see these

0:23:21.320 --> 0:23:23.520
<v Speaker 1>things happening so much anymore. And that's because we can

0:23:23.600 --> 0:23:27.639
<v Speaker 1>block those attacks from corrupting the content on a website.

0:23:28.080 --> 0:23:31.359
<v Speaker 1>So we're not looking to say is this video deep

0:23:31.359 --> 0:23:34.240
<v Speaker 1>fake or was it the legitimate We're just making sure

0:23:34.240 --> 0:23:36.760
<v Speaker 1>whatever video on that website came from the people who

0:23:36.840 --> 0:23:39.679
<v Speaker 1>owned the website, not from some third party putting their

0:23:39.720 --> 0:23:43.560
<v Speaker 1>own video on the website. Switching gears let's talk a

0:23:43.560 --> 0:23:46.840
<v Speaker 1>bit about five G, which you know, tremendous amount of

0:23:46.880 --> 0:23:51.240
<v Speaker 1>hype about how amazing it is going to be. And

0:23:51.320 --> 0:23:54.800
<v Speaker 1>I'm curious the impact it has on your business or

0:23:54.920 --> 0:23:59.240
<v Speaker 1>or maybe your impact on five G. Uh Is this

0:23:59.440 --> 0:24:02.280
<v Speaker 1>going to be everything that it is being made out

0:24:02.320 --> 0:24:05.040
<v Speaker 1>to be. Well, five G does a lot of good things.

0:24:05.160 --> 0:24:08.720
<v Speaker 1>It gives you much better connectivity in the last mile

0:24:08.840 --> 0:24:11.200
<v Speaker 1>or the end user connecting to the Internet or to

0:24:11.280 --> 0:24:15.840
<v Speaker 1>the cell tower, much lower latency than traditional cellular, higher

0:24:15.880 --> 0:24:19.360
<v Speaker 1>throughput uh, and more devices will be able to connect.

0:24:19.880 --> 0:24:24.240
<v Speaker 1>And I think this will have the biggest impact on IoT,

0:24:24.680 --> 0:24:27.199
<v Speaker 1>you know, the Internet of things now. IoT has been

0:24:27.240 --> 0:24:30.320
<v Speaker 1>a pretty good buzzword, you know for the last five years,

0:24:30.359 --> 0:24:32.200
<v Speaker 1>but you haven't seen much in the way of killer

0:24:32.240 --> 0:24:36.240
<v Speaker 1>apps yet. I think that could change with five G.

0:24:36.680 --> 0:24:40.000
<v Speaker 1>And we do see in our customer base now more

0:24:40.000 --> 0:24:43.919
<v Speaker 1>and more interesting projects you know around five G. You know,

0:24:44.080 --> 0:24:48.679
<v Speaker 1>sensors and your sneakers, sensors and your sporting equipment or

0:24:48.720 --> 0:24:53.200
<v Speaker 1>closed sensors on price tags, sensor sureley in cars, there's

0:24:53.200 --> 0:24:57.159
<v Speaker 1>a lot of them in cars today. Your gaming devices,

0:24:57.200 --> 0:25:00.840
<v Speaker 1>you know, become things in the Internet of things. UH.

0:25:01.000 --> 0:25:04.560
<v Speaker 1>And interestingly, the communication protocols. It's different. It's not Web,

0:25:05.320 --> 0:25:07.680
<v Speaker 1>it's other protocols are being used that are a lot

0:25:07.760 --> 0:25:09.960
<v Speaker 1>lighter weight. There's a lot more compute that will be

0:25:10.040 --> 0:25:12.600
<v Speaker 1>done on the edge near the end user, and I

0:25:12.640 --> 0:25:17.240
<v Speaker 1>think there'll be some pretty interesting applications. Already. Airlines are

0:25:17.320 --> 0:25:19.719
<v Speaker 1>using it to sense when you're in the airport, pushed

0:25:19.760 --> 0:25:23.840
<v Speaker 1>you notifications about your flight, get you updated with whatever METEA,

0:25:23.880 --> 0:25:26.000
<v Speaker 1>or movies you might want to watch before you get

0:25:26.000 --> 0:25:27.960
<v Speaker 1>on board, because once you're on board is a little harder.

0:25:29.080 --> 0:25:30.960
<v Speaker 1>I think there'll be a lot of cool stuff with

0:25:31.040 --> 0:25:34.600
<v Speaker 1>around IoT enabled by five G. In terms of the

0:25:34.640 --> 0:25:37.280
<v Speaker 1>impact on akam I, it's it's great, you know for

0:25:37.359 --> 0:25:41.560
<v Speaker 1>our business. Uh you know, because as you get more

0:25:41.680 --> 0:25:44.119
<v Speaker 1>activity out at the last mile or the edge of

0:25:44.160 --> 0:25:48.840
<v Speaker 1>the Internet, um, that's what we accommodate, you know, and

0:25:48.880 --> 0:25:51.120
<v Speaker 1>it will put more stress on the core of the Internet.

0:25:51.320 --> 0:25:55.159
<v Speaker 1>And our whole thesis is you want to serve the

0:25:55.280 --> 0:25:58.840
<v Speaker 1>end user close to the end user, and as the

0:25:58.920 --> 0:26:01.439
<v Speaker 1>last mile gets better, are that increases the need for

0:26:01.480 --> 0:26:04.080
<v Speaker 1>the kind of things that we do, and we'll be

0:26:04.119 --> 0:26:07.120
<v Speaker 1>helping the Internet to accommodate the load that will get

0:26:07.119 --> 0:26:10.399
<v Speaker 1>put on it from five G. Listening to all this,

0:26:10.520 --> 0:26:12.639
<v Speaker 1>I I think about I guess let's call it the

0:26:12.720 --> 0:26:15.600
<v Speaker 1>last foot of the last mile, which is in my

0:26:15.680 --> 0:26:18.719
<v Speaker 1>own home. You know. Look, I deal with issues like

0:26:18.800 --> 0:26:22.520
<v Speaker 1>buffering maybe a little more often than i'd like. Um,

0:26:22.840 --> 0:26:25.080
<v Speaker 1>and I assume all these things have more to do

0:26:25.160 --> 0:26:30.040
<v Speaker 1>with my in home WiFi and whatever uh drawbacks that

0:26:30.080 --> 0:26:32.880
<v Speaker 1>has At the end of the day, is there only

0:26:32.960 --> 0:26:36.800
<v Speaker 1>so much you could do to deliver video as quick

0:26:36.840 --> 0:26:39.199
<v Speaker 1>as possible when at the end of the day, I

0:26:39.200 --> 0:26:42.120
<v Speaker 1>don't know what kind of control you have over, say,

0:26:42.160 --> 0:26:45.639
<v Speaker 1>my faulty WiFi. Well, yeah, we don't have control of

0:26:45.680 --> 0:26:47.919
<v Speaker 1>your faulty WiFi. But in a lot of the world

0:26:48.080 --> 0:26:52.400
<v Speaker 1>today that's not the problem. Uh. It really is bottlenecks

0:26:52.400 --> 0:26:55.120
<v Speaker 1>in the core of the Internet, and that's where it's

0:26:55.119 --> 0:26:58.800
<v Speaker 1>breaking down, and that's what we get around. Uh. So

0:26:58.880 --> 0:27:01.600
<v Speaker 1>what docummy, we can make that problem go away. Increasingly,

0:27:01.640 --> 0:27:03.920
<v Speaker 1>we'll have software on your device and in your home

0:27:04.480 --> 0:27:07.879
<v Speaker 1>that will make things better there. But I don't I

0:27:07.960 --> 0:27:10.920
<v Speaker 1>don't think the home is the really the problem. You've

0:27:11.080 --> 0:27:13.280
<v Speaker 1>been in my home, then well, okay, maybe in your

0:27:13.400 --> 0:27:16.800
<v Speaker 1>home it's the problem. Interesting data point that acam I

0:27:16.920 --> 0:27:19.919
<v Speaker 1>interacts with a hundred and thirty terror bytes of data

0:27:20.000 --> 0:27:24.639
<v Speaker 1>on over one billion devices. That is a scale I

0:27:24.920 --> 0:27:27.560
<v Speaker 1>can't even wrap my head around. Yeah, we're serving well, actually,

0:27:27.600 --> 0:27:32.000
<v Speaker 1>billions of people every day. A lot of what billions

0:27:32.040 --> 0:27:34.880
<v Speaker 1>of people do around the world every day runs through us,

0:27:35.440 --> 0:27:38.200
<v Speaker 1>and our goal is to make it be really fast, efficient,

0:27:38.280 --> 0:27:42.120
<v Speaker 1>and importantly to be secure. I feel like we've kind

0:27:42.119 --> 0:27:45.959
<v Speaker 1>of been talking, perhaps interchangeably about what I think are

0:27:46.440 --> 0:27:51.479
<v Speaker 1>sort of two different transmission modes wire line and wire lists.

0:27:51.680 --> 0:27:54.760
<v Speaker 1>You know, I have different issues on my phone related

0:27:54.800 --> 0:27:59.119
<v Speaker 1>than to my TV or my MacBook. Um, are there

0:27:59.119 --> 0:28:01.320
<v Speaker 1>a different set of channel just from an Acomi perspective

0:28:01.359 --> 0:28:04.280
<v Speaker 1>in terms of how you manage the Internet across those

0:28:04.280 --> 0:28:07.560
<v Speaker 1>two different pipes, so to speak at a high level, No,

0:28:07.800 --> 0:28:10.439
<v Speaker 1>at a high level, it's it's similar. Uh. You know,

0:28:10.960 --> 0:28:14.040
<v Speaker 1>cellular short of five G, but three G four G

0:28:14.640 --> 0:28:17.720
<v Speaker 1>has higher latency. Uh. Then again, a lot of cable

0:28:17.720 --> 0:28:22.000
<v Speaker 1>networks have high latency into your home with land lines. Um,

0:28:22.080 --> 0:28:25.080
<v Speaker 1>So the and the capacities can be different. You know,

0:28:25.119 --> 0:28:28.159
<v Speaker 1>three G and four G capacity through put is not

0:28:28.240 --> 0:28:30.560
<v Speaker 1>so great if you're the only person at the tower, fine,

0:28:30.720 --> 0:28:32.280
<v Speaker 1>but if you've got a lot of people using the tower,

0:28:32.320 --> 0:28:35.600
<v Speaker 1>you can have capacity problems. You know, the connection into

0:28:35.640 --> 0:28:38.040
<v Speaker 1>the homes now is actually pretty good in a lot

0:28:38.120 --> 0:28:42.280
<v Speaker 1>of places, although you can get aggregation and congestion at

0:28:42.320 --> 0:28:47.000
<v Speaker 1>the neighborhood or the community, you know, city level that

0:28:47.080 --> 0:28:51.160
<v Speaker 1>will reduce your throughput. So the challenges at a high

0:28:51.200 --> 0:28:53.640
<v Speaker 1>level of the saying the technology is a little bit different.

0:28:53.840 --> 0:28:55.800
<v Speaker 1>Our goal in both cases is to make it a

0:28:55.840 --> 0:28:58.880
<v Speaker 1>good experience. There was a time not too long ago

0:28:59.200 --> 0:29:02.800
<v Speaker 1>where there was a lot of conversation really is net

0:29:02.800 --> 0:29:05.880
<v Speaker 1>neutrality started to become a bigger issue about things like

0:29:06.040 --> 0:29:10.640
<v Speaker 1>peering agreements and you know, all sorts of negotiations between say,

0:29:10.640 --> 0:29:15.280
<v Speaker 1>pay TV distributors and content delivery networks that seem to

0:29:15.280 --> 0:29:17.920
<v Speaker 1>be all about holding the Internet together. I don't hear

0:29:17.960 --> 0:29:21.720
<v Speaker 1>about that stuff as much anymore, and I'm curious, wise,

0:29:22.120 --> 0:29:24.479
<v Speaker 1>is everything kind of settled and everyone's just sort of

0:29:24.520 --> 0:29:28.280
<v Speaker 1>playing on the same page or or those conversations still

0:29:28.280 --> 0:29:31.240
<v Speaker 1>as fractious as they've always been. We're just not hearing

0:29:31.240 --> 0:29:36.520
<v Speaker 1>about it. I think the the the things that motivated

0:29:36.560 --> 0:29:41.280
<v Speaker 1>that are the same things. On the one hand, you

0:29:41.440 --> 0:29:48.520
<v Speaker 1>have the economic uh issues between some big content providers

0:29:48.560 --> 0:29:52.200
<v Speaker 1>people who want to distribute movies, say, and big carriers

0:29:52.480 --> 0:29:56.239
<v Speaker 1>who also have movies and uh and uh, you know,

0:29:56.320 --> 0:30:00.400
<v Speaker 1>content channels that they want to distribute, and the question

0:30:00.440 --> 0:30:05.720
<v Speaker 1>about who should pay to distribute that content, you know,

0:30:05.800 --> 0:30:09.440
<v Speaker 1>should the carrier build out a lot of infrastructure and

0:30:09.680 --> 0:30:13.080
<v Speaker 1>bear a lot of costs to distribute their competitors videos.

0:30:14.360 --> 0:30:17.600
<v Speaker 1>You know, well, the some the competitor who has those

0:30:17.680 --> 0:30:20.560
<v Speaker 1>videos think so and and did a very good job

0:30:20.600 --> 0:30:24.400
<v Speaker 1>at getting the administration to agree, and that forced net

0:30:24.440 --> 0:30:28.160
<v Speaker 1>neutrality laws. Then there is a new administration and so

0:30:28.320 --> 0:30:31.880
<v Speaker 1>the control changed of who makes the decisions, and all

0:30:31.920 --> 0:30:35.120
<v Speaker 1>those decisions got reversed, and so now it's not the

0:30:35.160 --> 0:30:39.040
<v Speaker 1>case that the big carrier needs to pay. Now there's

0:30:39.080 --> 0:30:43.360
<v Speaker 1>also a technical issue here that is really important that

0:30:43.480 --> 0:30:47.760
<v Speaker 1>didn't that people didn't think about, and that is it

0:30:47.800 --> 0:30:51.440
<v Speaker 1>doesn't matter so much who's paying. You just can't pay

0:30:51.600 --> 0:30:56.120
<v Speaker 1>enough to distribute videos at scale from these core data

0:30:56.120 --> 0:30:59.400
<v Speaker 1>centers from outside. There's just even if the carrier wanted to,

0:30:59.480 --> 0:31:02.800
<v Speaker 1>which they did, and they couldn't afford to build all

0:31:02.880 --> 0:31:06.040
<v Speaker 1>these gigantic pipes, you know, from the data centers into

0:31:06.040 --> 0:31:09.680
<v Speaker 1>the neighborhoods, it's just not the right model. You need

0:31:09.720 --> 0:31:13.520
<v Speaker 1>to be distributing locally. Uh. And the reason we had

0:31:13.560 --> 0:31:17.680
<v Speaker 1>congestion and do and people were complaining they couldn't watch

0:31:17.720 --> 0:31:21.400
<v Speaker 1>the movie without rebuffers, they couldn't watch a high quality

0:31:22.320 --> 0:31:25.880
<v Speaker 1>wasn't so much the dispute between the media company and

0:31:25.920 --> 0:31:30.040
<v Speaker 1>the carriers, because you need a different technical model. You

0:31:30.120 --> 0:31:33.120
<v Speaker 1>need to be distributing that movie from from the edge

0:31:33.200 --> 0:31:36.920
<v Speaker 1>or you know, inside way deep in the carrier. Uh.

0:31:36.920 --> 0:31:41.680
<v Speaker 1>And that was what was really causing the equality problems. Uh.

0:31:41.880 --> 0:31:44.760
<v Speaker 1>So all those issues are the same. It's just there's

0:31:44.760 --> 0:31:47.800
<v Speaker 1>a different uh party in control today and they have

0:31:47.840 --> 0:31:51.560
<v Speaker 1>a different view on how net neutrality should go. And

0:31:51.640 --> 0:31:53.720
<v Speaker 1>on that front, one last question, I mean, do you

0:31:53.760 --> 0:31:57.320
<v Speaker 1>guys have a dog in that hunt of net neutrality?

0:31:57.480 --> 0:32:00.440
<v Speaker 1>Is there a company position about what you I think

0:32:00.480 --> 0:32:03.600
<v Speaker 1>should be as it continues to be kind of a

0:32:03.600 --> 0:32:07.520
<v Speaker 1>hot potato in d C. Yeah, so it sounds funny,

0:32:07.520 --> 0:32:11.280
<v Speaker 1>but it's true. We're neutral on net neutrality. Uh. You know,

0:32:11.400 --> 0:32:14.280
<v Speaker 1>we we help advise the government to educate them what's

0:32:14.440 --> 0:32:17.720
<v Speaker 1>going on. We work with the big media companies because

0:32:17.760 --> 0:32:20.200
<v Speaker 1>for a lot of them, we distribute their video, almost

0:32:20.200 --> 0:32:23.080
<v Speaker 1>all of them, and obviously we work with the big carriers.

0:32:23.120 --> 0:32:25.640
<v Speaker 1>They're big partners for us were embedded deep in their

0:32:25.680 --> 0:32:29.200
<v Speaker 1>infrastructure and we help them be efficient and help their

0:32:29.320 --> 0:32:32.160
<v Speaker 1>users get a good experience. So we work closely with

0:32:32.160 --> 0:32:35.640
<v Speaker 1>with both sides, and uh so we don't have a

0:32:36.440 --> 0:32:39.480
<v Speaker 1>you know, a stake really in net neutrality. Well, rest

0:32:39.520 --> 0:32:41.800
<v Speaker 1>assured that will be a topic that I'm sure I

0:32:41.880 --> 0:32:44.280
<v Speaker 1>will both continue to hear about for quite some time.

0:32:44.880 --> 0:32:48.520
<v Speaker 1>But Tom, thanks for coming in. Really appreciate your education

0:32:48.560 --> 0:32:54.000
<v Speaker 1>on an important subject. Thank you very much. This has

0:32:54.040 --> 0:32:57.360
<v Speaker 1>been another episode of Strictly Business. Tune in next week

0:32:57.400 --> 0:33:01.640
<v Speaker 1>for another helping of scintillating conversation media movers and shakers,

0:33:01.800 --> 0:33:04.640
<v Speaker 1>and please make sure you subscribe to the podcast to

0:33:04.720 --> 0:33:08.600
<v Speaker 1>hear future episodes. Also leave a review in Apple Podcast

0:33:08.720 --> 0:33:13.280
<v Speaker 1>let us know how we're doing. Yeah,