WEBVTT 00:00:15.838 --> 00:00:18.241 We live in a physical world. 00:00:18.241 --> 00:00:20.256 We also live in a physical world 00:00:20.256 --> 00:00:24.394 that's in a process of merging with the digital world. 00:00:24.394 --> 00:00:26.180 As a consequence, 00:00:26.180 --> 00:00:28.961 increasingly, aspect of the physical world 00:00:28.961 --> 00:00:31.008 such as, say, 00:00:31.008 --> 00:00:33.255 the fact that it's geographically distributed, 00:00:33.255 --> 00:00:37.675 are starting to impact our digital experiences. 00:00:37.675 --> 00:00:40.044 This is a worldwide property, 00:00:40.044 --> 00:00:41.399 and it's due to the fact 00:00:41.399 --> 00:00:44.693 that we live all across the surface of a planet 00:00:44.693 --> 00:00:46.680 that has a finite diameter. 00:00:46.680 --> 00:00:49.514 So, for example, in virtual worlds, 00:00:49.514 --> 00:00:52.554 if you have one party on one side of the planet, 00:00:52.554 --> 00:00:54.961 and one party on another side of the planet, 00:00:54.961 --> 00:00:57.402 that are interacting via a virtual world, 00:00:57.402 --> 00:00:58.789 such as Second Life, 00:00:58.789 --> 00:01:01.794 the experience delays due to the fact 00:01:01.794 --> 00:01:04.509 that light takes a finite amount of time 00:01:04.509 --> 00:01:06.695 to travel around the Earth's surface 00:01:06.695 --> 00:01:08.481 in order to connect them. 00:01:08.481 --> 00:01:10.529 And this problem isn't in any way 00:01:10.529 --> 00:01:13.507 specific to virtual worlds or entertainment. 00:01:13.507 --> 00:01:17.080 It's a problem that's keenly felt in industrial sectors, 00:01:17.080 --> 00:01:18.988 in financial sectors. 00:01:18.988 --> 00:01:20.676 Financial sector in particular, 00:01:20.676 --> 00:01:23.172 is very well incentified to make sure 00:01:23.172 --> 00:01:26.445 that the time delays for transmitting information 00:01:26.445 --> 00:01:30.495 between financial exchanges is minimised. 00:01:30.495 --> 00:01:32.590 One more example, 00:01:32.590 --> 00:01:34.934 telerobotics and telesurgery. 00:01:34.934 --> 00:01:37.259 As we move towards an era, 00:01:37.259 --> 00:01:39.759 where a physician in one location on Earth 00:01:39.759 --> 00:01:41.931 can perform surgery on a patient 00:01:41.931 --> 00:01:43.977 on the opposite end of the Earth, 00:01:43.977 --> 00:01:47.096 the delays involved in manipulating remote machines 00:01:47.096 --> 00:01:50.743 become increasingly essential to performance. 00:01:52.243 --> 00:01:55.488 And so how if we try to combat this thus far? 00:01:55.488 --> 00:01:58.709 This is a map of submarine cables 00:01:58.709 --> 00:02:03.095 strewn all around the Earth's oceans and on land. 00:02:03.095 --> 00:02:06.426 We are literally wiring up our planet surface 00:02:06.426 --> 00:02:10.129 in order to efficiently allow information to flow 00:02:10.129 --> 00:02:12.342 from any point on the Earth's surface 00:02:12.342 --> 00:02:15.161 to any other point on the Earth's surface. 00:02:15.161 --> 00:02:16.569 You might imagine 00:02:16.569 --> 00:02:17.747 we are relatively close to 00:02:17.747 --> 00:02:20.705 solving this problem of information delays. 00:02:22.145 --> 00:02:23.532 But of course, 00:02:23.532 --> 00:02:25.659 as with all physical properties, 00:02:25.659 --> 00:02:26.966 there are limits. 00:02:26.966 --> 00:02:28.947 Here's one very important one. 00:02:28.947 --> 00:02:31.387 What you're seeing here are 2 maps 00:02:31.387 --> 00:02:33.421 of some of the state-of-the-art 00:02:33.421 --> 00:02:36.265 Internet connections connecting locations. 00:02:36.265 --> 00:02:37.614 On the left, 00:02:37.614 --> 00:02:39.703 a New York to Chicago connection. 00:02:39.703 --> 00:02:41.109 On the right, 00:02:41.109 --> 00:02:42.835 New York to London. 00:02:42.835 --> 00:02:44.109 Interestingly, 00:02:44.109 --> 00:02:46.113 if you look at the amount of time it takes 00:02:46.113 --> 00:02:48.278 to send information back and forth, 00:02:48.278 --> 00:02:49.888 through these pipes, 00:02:49.888 --> 00:02:51.302 and you compare it 00:02:51.302 --> 00:02:53.576 with the theoretical physical limit 00:02:53.576 --> 00:02:56.530 to how fast you could send information round trip 00:02:56.530 --> 00:03:00.041 using light through optical fiber, 00:03:00.301 --> 00:03:01.553 you'll notice 00:03:01.553 --> 00:03:03.581 that we're literally approaching 00:03:03.581 --> 00:03:06.099 the physical limits allowed to us 00:03:06.099 --> 00:03:08.407 for sending information around the Earth 00:03:08.407 --> 00:03:10.805 between these important cities. 00:03:10.805 --> 00:03:13.673 This is the problem for the reasons I've mentioned 00:03:13.673 --> 00:03:18.176 that's only going to become more exacerbated with time. 00:03:19.006 --> 00:03:20.797 Why is this a problem? 00:03:20.797 --> 00:03:22.351 Well, the way we've architected 00:03:22.351 --> 00:03:25.445 many of our global transactions right now on the Internet, 00:03:25.445 --> 00:03:27.282 and our networks in general, 00:03:27.282 --> 00:03:30.098 requires round trip transactions. 00:03:30.098 --> 00:03:31.854 So, you have location A, 00:03:31.854 --> 00:03:33.390 and location B, 00:03:33.390 --> 00:03:35.601 and you want to coordinate processes 00:03:35.601 --> 00:03:37.562 between these two locations, 00:03:37.562 --> 00:03:40.023 they have to send information to each other 00:03:40.023 --> 00:03:41.753 about their current state, 00:03:41.753 --> 00:03:43.591 and wait for the other party 00:03:43.591 --> 00:03:45.557 to react to that new information, 00:03:45.557 --> 00:03:48.008 and send back an execution signal. 00:03:48.008 --> 00:03:49.431 In other words, 00:03:49.431 --> 00:03:50.951 for most transactions today, 00:03:50.951 --> 00:03:52.995 you're stuck with round trip delays 00:03:52.995 --> 00:03:54.619 on the Internet. 00:03:55.969 --> 00:03:58.009 Now, biology, 00:03:58.009 --> 00:04:00.259 as has historically been the case, 00:04:00.259 --> 00:04:02.680 has come up with a solution to this problem. 00:04:02.680 --> 00:04:04.717 So, if you as a human, 00:04:04.717 --> 00:04:06.348 touch a hot surface, 00:04:06.348 --> 00:04:08.846 you'll note, that your hand pulls itself back 00:04:08.846 --> 00:04:11.514 before you feel the pain in your mind. 00:04:11.514 --> 00:04:13.848 And the reason is that the pain signal 00:04:13.848 --> 00:04:16.182 isn't travelling the entire distance 00:04:16.182 --> 00:04:18.207 from your finger up to your brain, 00:04:18.207 --> 00:04:20.703 and then back to your motor neurons, 00:04:20.703 --> 00:04:22.229 to pull your hand back. 00:04:22.229 --> 00:04:25.106 Instead, it's just travelling to an intermediate location, 00:04:25.106 --> 00:04:26.372 your spinal column, 00:04:26.372 --> 00:04:27.911 where it's immediately recognized 00:04:27.911 --> 00:04:29.900 as actionable information, 00:04:29.900 --> 00:04:32.431 and signals are immediately turned around 00:04:32.431 --> 00:04:34.474 for a more rapid response. 00:04:34.474 --> 00:04:36.316 It's called a reflex arc. 00:04:36.316 --> 00:04:39.342 So, biology is handing us the solution. 00:04:40.022 --> 00:04:43.847 We can do reflex arcs for global networking. 00:04:43.847 --> 00:04:45.679 So rather than doing 00:04:45.679 --> 00:04:48.011 round trip transmission of information, 00:04:48.011 --> 00:04:51.265 let's instead position server infrastructure 00:04:51.265 --> 00:04:54.261 at well selected intermediate locations 00:04:54.261 --> 00:04:57.003 between two different geographic locations 00:04:57.003 --> 00:04:59.016 that need to be coordinated. 00:04:59.016 --> 00:05:00.081 So, this is a problem 00:05:00.081 --> 00:05:01.236 that I've been thinking about 00:05:01.236 --> 00:05:02.612 for a number of years: 00:05:02.612 --> 00:05:05.251 how best to position these intermediate locations 00:05:05.251 --> 00:05:08.475 in order to literally get around the speed of light 00:05:08.475 --> 00:05:11.767 by not being forced to wait for this round trip transmission? 00:05:11.767 --> 00:05:13.237 And recently, 00:05:13.237 --> 00:05:16.577 I identified and published the optimal solution. 00:05:16.577 --> 00:05:18.549 So, what you're seeing here is an equation 00:05:18.549 --> 00:05:21.349 that describes the theoretical optimal solution 00:05:21.349 --> 00:05:23.172 for where to place yourself 00:05:23.172 --> 00:05:25.415 in between two different locations 00:05:25.415 --> 00:05:28.154 in order to optimally coordinate processes 00:05:28.154 --> 00:05:30.483 happening at either end. 00:05:31.613 --> 00:05:33.392 And so, just for fun, 00:05:33.392 --> 00:05:35.406 I've taken this equation, 00:05:35.406 --> 00:05:38.184 and applied it to a financial task. 00:05:38.184 --> 00:05:39.762 So, what you're looking at here, 00:05:39.762 --> 00:05:41.853 is literally a treasure map. 00:05:41.853 --> 00:05:43.578 The large red dots represent 00:05:43.578 --> 00:05:45.683 the world's largest stock exchanges, 00:05:45.683 --> 00:05:48.289 and the small blue dots here 00:05:48.289 --> 00:05:52.260 represent the calculated optimal intermediate locations 00:05:52.260 --> 00:05:54.693 for coordinating, trading, 00:05:54.693 --> 00:05:56.883 on pairs of these exchanges. 00:05:56.883 --> 00:05:58.015 And you'll note, 00:05:58.015 --> 00:06:00.917 that many of these optimal intermediate locations 00:06:00.917 --> 00:06:03.314 are in network sparse areas, 00:06:03.314 --> 00:06:05.141 and on oceans. 00:06:05.141 --> 00:06:08.258 And so, this presents us with what may perhaps be 00:06:08.258 --> 00:06:11.268 the first excuse to literally boil the oceans 00:06:11.268 --> 00:06:13.016 using computation. 00:06:15.056 --> 00:06:19.224 Now, how do we go about to deploying this new infrastructure? 00:06:19.224 --> 00:06:23.578 So, I've shown here 3 different modalities 00:06:23.578 --> 00:06:25.894 for deploying these new servers 00:06:25.894 --> 00:06:29.618 that would be responsible for creating global reflex arcs, 00:06:29.618 --> 00:06:33.348 in order to help us get around speed of light limitations. 00:06:33.348 --> 00:06:34.557 So, on the left, 00:06:34.557 --> 00:06:36.430 you see microwave towers, 00:06:36.430 --> 00:06:38.216 we see balloons in the middle, 00:06:38.216 --> 00:06:42.003 and we see microwave buoys, 00:06:42.003 --> 00:06:44.620 microwave relay buoys, to the right. 00:06:44.620 --> 00:06:49.009 These are just 3 modalities by which one can envisage, 00:06:49.009 --> 00:06:51.546 getting around the speed of light 00:06:51.546 --> 00:06:54.403 due to the Earth's finite size. 00:06:54.403 --> 00:06:57.101 And so, I think, stepping back, 00:06:57.101 --> 00:07:00.994 we're faced with an opportunity at this point in time, 00:07:00.994 --> 00:07:03.495 to not just bump up against 00:07:03.505 --> 00:07:05.716 the finite speed of light, 00:07:05.716 --> 00:07:08.368 as a pretence to telecommunications on Earth, 00:07:08.368 --> 00:07:10.738 but to use this as an opportunity 00:07:10.738 --> 00:07:14.247 to create lots of new infrastructure in locations 00:07:14.247 --> 00:07:17.243 that previously had none, and in particular, 00:07:17.243 --> 00:07:20.819 I'm especially fond of this analogy, 00:07:20.819 --> 00:07:23.081 the Silk Road, or the Silk Route, 00:07:23.081 --> 00:07:26.378 the trade of silk was responsible, 00:07:26.378 --> 00:07:28.716 in the first few centuries CE, 00:07:28.716 --> 00:07:30.610 for creating economic growth 00:07:30.610 --> 00:07:32.484 at intermediate locations 00:07:32.484 --> 00:07:35.268 between opposite ends of a trade route. 00:07:35.268 --> 00:07:37.001 And I think the opportunity here 00:07:37.001 --> 00:07:40.333 is to leverage the finite speed of light 00:07:40.333 --> 00:07:42.043 to deploy infrastructure 00:07:42.043 --> 00:07:44.063 in many locations around the world 00:07:44.063 --> 00:07:45.979 that currently don't have access 00:07:45.979 --> 00:07:47.935 to low latency Internet, 00:07:47.935 --> 00:07:49.110 and as a result, 00:07:49.110 --> 00:07:52.645 treat geography as a new form of natural resource 00:07:52.645 --> 00:07:55.580 that can lead to broader economic development. 00:07:55.580 --> 00:07:57.350 Thank you very much. 00:07:57.350 --> 00:07:59.728 (Applause)