Right.

And Zoom's, um...

it behooves Zoom's architects to design their application in a way that the video streams or the data plane stuff does not require constant authentication or authorization, which is probably bottlenecked to a US server or bottlenecked to a England server, uh, or bottlenecked to a Singapore server, right? They may have identity and authorization at only two or three points in the world, but they will have these video stream, uh, platforms, uh, media servers at multiple locations.

So the more their media servers are stateless or weakly coupled to their identity and authorization servers, the more they will be able to scale out geographically, uh, and hence, uh, give a delightful user experience to no matter where that satellite user is coming from, right? So architecture d- uh, network architecture and application architecture requires you to split out stateful things from stateless things, and the more stateless you make your app or your service, the better you are able to site it closer to the user.

That has always been true.

This is not new.

This is not new information.

Mm.

Right.

And Zoom's, um...

it behooves Zoom's architects to design their application in a way that the video streams or the data plane stuff does not require constant authentication or authorization, which is probably bottlenecked to a US server or bottlenecked to a England server, uh, or bottlenecked to a Singapore server, right? They may have identity and authorization at only two or three points in the world, but they will have these video stream, uh, platforms, uh, media servers at multiple locations.

So the more their media servers are stateless or weakly coupled to their identity and authorization servers, the more they will be able to scale out geographically, uh, and hence, uh, give a delightful user experience to no matter where that satellite user is coming from, right? So architecture d- uh, network architecture and application architecture requires you to split out stateful things from stateless things, and the more stateless you make your app or your service, the better you are able to site it closer to the user.

That has always been true.

This is not new.

This is not new information.

Mm.

So tell us a little bit about maybe your talk and what are some of the fundamental breakage that could happen when the user is satellite users?

Yeah, so I'll wear the application developer's hat because that hat is something that I'm intimately familiar with.

So if I was, say, for example, a Google application developer, I tried the search engine web page, right? So on the search engine results web page, my code is supposed to use an IP geolocation lookup.

where the request for search is coming and i'm supposed to um you know language localize look the you know the search results to what i believe is the best guess of the user location so now if i am in a you know moving aircraft which is transiting across many international borders every 30 seconds and i have a long nine hour flight from say carter airways hub to washington dc I'm traversing over all of these IP geolocations.

So if I actually change the IP of my terminal, of my aircraft, effectively, should I, as a Google app developer, continue changing the language localization based on the location of the IP.

This was actually my user experience six months ago.

And then they have been changing this implementation, the Starlink guys.

So maybe you could talk a little bit about that and the multiple ways to solve this besides the one that you just covered.