Latest / Cables2Clouds / Identity Crisis: What is Cloud Networking?
Transcript
- 0:14Tim McConnaughy: Hello and welcome to another episode of the Cables to Clouds podcast.
- 0:17Tim McConnaughy: I'm your host this week, tim, and with me, as always, is my co-host, chris.
- 0:23Tim McConnaughy: I'm at Carpe DMVPN on Blue Sky and Chris is at BGP Main on Blue Sky, if I could speak correctly.
- 0:32Tim McConnaughy: And with us is a returning guest, a good friend of the podcast.
- 0:37Tim McConnaughy: We're lucky to have him.
- 0:38Tim McConnaughy: Nico Weber, would you like to?
- 0:40Tim McConnaughy: Actually, I don't remember, nico, are you on?
- 0:41Tim McConnaughy: I don't remember.
- 0:42Tim McConnaughy: Are you on Blue Sky yet, nico?
- 0:43Tim McConnaughy: Are you?
- 0:43Tim McConnaughy: You to actually?
- 0:44Nicolas Vibert: I don't remember.
- 0:44Nicolas Vibert: Nico, are you on Blue Sky yet?
- 0:45Nicolas Vibert: Nico are you?
- 0:46Nicolas Vibert: You don't do the social media.
- 0:47Nicolas Vibert: No Well, I used to be on Twitter and pretty active, but I left that, yeah.
- 0:52Tim McConnaughy: That was a good move.
- 0:55Nicolas Vibert: Pretty active on LinkedIn with videos and silly blog posts, but that's where you'll find me.
- 1:01Tim McConnaughy: Yep, yep, yep, excellent.
- 1:02Tim McConnaughy: And just in case, so we've had you on the podcast before.
- 1:07Tim McConnaughy: It was an excellent episode talking about Kubernetes and Cilium, but for the people who may not have heard or seen that episode, go ahead and quickly reintroduce yourself.
- 1:17Nicolas Vibert: Sure.
- 1:17Nicolas Vibert: So I'm a senior staff technical marketing engineer at iSurveillance slash Cisco and my background is network engineering.
- 1:27Nicolas Vibert: I've been in network for about 20 years now.
- 1:29Nicolas Vibert: I did my CCNA, ccnp, ccie back in the days.
- 1:33Nicolas Vibert: I was CCIE for about 10 years until I let it go and worked for Cisco for a while and then I was a boomerang back in through the acquisition of iSurveillance by Cisco last year.
- 1:47Nicolas Vibert: So yeah, just happy to be back on this podcast.
- 1:52Tim McConnaughy: Yeah, we're definitely happy to have you back and actually you came up with a really cool topic and that's why we brought you back.
- 1:58Tim McConnaughy: And let me see if I can read this correctly, just make sure I'm getting it right.
- 2:02Tim McConnaughy: So we were talking on LinkedIn a little bit and you were like you know, what I really love to tackle was this idea of the identity crisis of cloud networking, specifically, what's cloud networking and what it is, what it isn't.
- 2:14Tim McConnaughy: And I just realized that, like you know, there's so many opinions on this that, like it's a great topic and I'm sure if you talk to 10, five engineers, you'll get 10 different opinions, right, so I love it.
- 2:26Tim McConnaughy: So let's just kick it off there, like what made you think of this topic?
- 2:30Tim McConnaughy: And like because I mean, so this comes from somewhere.
- 2:32Tim McConnaughy: You've got opinions on this, yeah.
- 2:41Nicolas Vibert: Well, I guess, as a marketing, technical, marketing engineer, one of my responsibilities is to work with analysts, you know, like the likes of Gardner and Forrester, that kind of people, and answer questionnaires about our product and where we fit, and obviously let them, you know, rank stackers against other companies, you know, in the quadrant right.
- 2:56Nicolas Vibert: And I was recently answering one such query about cloud networking.
- 3:04Nicolas Vibert: I looked at all the different vendors and I was like, hang on, are these guys cloud networking?
- 3:08Nicolas Vibert: And you just look at the list of people we were being compared with, it was like apples and oranges, lemons, I don't know.
- 3:16Nicolas Vibert: It was just a bunch of different companies and I just kept thinking what is even cloud networking?
- 3:23Nicolas Vibert: And you guys, you've had like cloud networking and you guys, like you know, you've had a cloud networking podcast for a couple of years now a couple years, yep yeah, um, you probably, even between yourself, have a different definition of what cloud networking might be, so no, it's.
- 3:38Tim McConnaughy: It's funny to hear you say this because since I became a TME, one of the things I probably hate most are those 40-page report questionnaires about hey, here's, fill out 40 pages of why you fit into this quadrant and how you're better, and you know, usually they're like, oh, don't talk about your competitors in here.
- 3:57Tim McConnaughy: But then you get to see, like you said, like you go look at the magic, the quote, unquote magic quadrant or whatever.
- 4:02Tim McConnaughy: They've all got their own version of stack ranking vendors and you're looking at them like huh, Like why am I?
- 4:09Tim McConnaughy: These guys are like SSE or something.
- 4:12Tim McConnaughy: They got nothing to do with what I do.
- 4:13Tim McConnaughy: Right, so absolutely All right.
- 4:16Nicolas Vibert: So I'll ask a question then who do you think was on this cloud networking, you know?
- 4:24Nicolas Vibert: Who else we have ISOVANON, which, as I said, is now part of Cisco.
- 4:28Nicolas Vibert: There might be some that you think, oh yeah, of course that's a cloud networking company, and there might be some that was like, hang on, so give me your, give me your, give me your guesses.
- 4:37Chris Miles: Like versus like versus, who is versus who isn't.
- 4:39Nicolas Vibert: Well, who do you think is on it?
- 4:41Tim McConnaughy: There's a list.
- 4:45Nicolas Vibert: Who would be on the list?
- 4:46Nicolas Vibert: Yeah, I've got the list.
- 4:46Nicolas Vibert: I'll tell you if you're.
- 4:47Chris Miles: If you're correct, or not nice uh yeah, well, I mean, I would hope.
- 4:50Chris Miles: I would hope our current employer is on there as well.
- 4:53Tim McConnaughy: Uh, I'm sure a matrix has got to be on there somewhere.
- 4:55Tim McConnaughy: Yes, uh, I mean so obviously, alkira would I.
- 5:00Tim McConnaughy: I mean I say obviously, but I I believe that alkira would would qualify and I feel like we're like passing judgment on that.
- 5:05Tim McConnaughy: I feel like an asshole, we're just passing judgment on these companies.
- 5:08Tim McConnaughy: But no, I mean I think from a focused cloud networking perspective.
- 5:12Tim McConnaughy: Yeah, I mean I think Alkira would fit the bill for that.
- 5:14Tim McConnaughy: Prosimo probably did before it went under right.
- 5:19Tim McConnaughy: I mean obviously Isovalent.
- 5:21Tim McConnaughy: Did Calico's own?
- 5:23Tim McConnaughy: Is it Tigera's the company that actually does Calico?
- 5:26Tim McConnaughy: Is that right?
- 5:30Nicolas Vibert: Yeah, they're actually not on it, but I suppose they could be, because they offer a similar product to what we do.
- 5:35Tim McConnaughy: Yeah, well, okay.
- 5:36Tim McConnaughy: Now, this is, of course, because I only just started getting into the Kubernetes stuff within the last few weeks and I went straight to Cilium because I already knew you and I was very familiar with the labs and everything that you pointed me towards.
- 5:48Tim McConnaughy: But then I was reading something else and I was like, oh, I should take a look at Calico and it's not the same, and I don't want to compare the two products.
- 5:55Tim McConnaughy: But I was like, just from a, you know, it's a CNI plugin, right, like it fits at least the Kubernetes CN, kubernetes, cni, I that's.
- 6:02Tim McConnaughy: And again, this gets into the whole cloud networking thing.
- 6:04Tim McConnaughy: Well, which you know, it's kubernetes, kubernetes networking, which could be running in the cloud.
- 6:08Tim McConnaughy: So, yeah, you can see how it automatically.
- 6:10Nicolas Vibert: Already we're starting to draw lines, right, right yeah, and you know, like I think if I, if I had to guess, I would have said aviatrix and prosimo, now kira, because they're kind of for me like obvious networking companies, um, but then and then I saw, okay, I saw cisco and arista, juniper.
- 6:31Nicolas Vibert: Fair enough makes sense.
- 6:33Tim McConnaughy: So f5 yeah, that's yeah, are we?
- 6:36Tim McConnaughy: That's like a fair point, right?
- 6:38Tim McConnaughy: They route packets but their, their actual value, prop and application is in the load balancing, right.
- 6:44Tim McConnaughy: So that's a fair point.
- 6:46Tim McConnaughy: Uh, oh no, didn't f5 bought somebody though?
- 6:48Tim McConnaughy: Uh, a few years ago, um, what was the name of that company?
- 6:51Tim McConnaughy: They bought a they bought a cloud.
- 6:53Chris Miles: Yeah, was it engine x.
- 6:54Nicolas Vibert: Sorry, it's a bit of gen x yeah yeah, I'll have to look it up.
- 6:58Tim McConnaughy: They bought an actual company that they were like, but then they kind of buried it.
- 7:01Tim McConnaughy: They never came out with the product, the the.
- 7:03Tim McConnaughy: They actually had a quote-unquote multi-cloud product and they never came out with it.
- 7:07Nicolas Vibert: Now.
- 7:07Nicolas Vibert: I have to go find it Well.
- 7:08Tim McConnaughy: Cloudflare actually just today had a press release about a new MCNS product.
- 7:13Tim McConnaughy: Did you see it?
- 7:14Tim McConnaughy: Oh, did I?
- 7:15Tim McConnaughy: Okay.
- 7:16Chris Miles: Yeah, they acquired a company called Nefeli I think it was about a year ago, right and now it's being called ago, right, um, and now it's being called like of course they've dubbed their, their branded magic, uh, moniker onto the front of it now, but it just like that seems like an orchestration thing.
- 7:32Chris Miles: So but like I think, as we open this up, that kind of speaks to your point, nico, like what is cloud networking?
- 7:38Chris Miles: Like?
- 7:38Chris Miles: We have like companies just doing maybe like kubernetes networking and then maybe multi-cloud networking, and then you know something as simple as just orchestrating the native constructs, like is that a cloud networking company?
- 7:50Chris Miles: Like it's uh, yeah, the, the money.
- 7:53Nicolas Vibert: the waters are very muddy at this point yeah, you know, I see, like the likes of you know broadcom vmware is that.
- 8:00Nicolas Vibert: You know, do they include vmware and I make vmware and yeah, you know, like an sx or something.
- 8:07Nicolas Vibert: Yeah, I'm assuming that's an sx right I would think so yeah, but like would you?
- 8:13Nicolas Vibert: would you describe an sx as cloud networking?
- 8:16Nicolas Vibert: And you know, and again, I worked on an sx and which is I?
- 8:19Nicolas Vibert: I mean an sx couldn't be more different than you know, like what, what, what I don't know, f5 or prosimo, or if hvc says right.
- 8:27Nicolas Vibert: So this is what I mean about, like this, cloud networking products and companies that actually do very different things.
- 8:35Chris Miles: Yeah, yeah, I feel like.
- 8:36Chris Miles: I feel like this is almost somewhat adjacent to like the kind of the evolution of where sd went.
- 8:44Chris Miles: Oh yeah, we had a few companies start out that were obviously pure SD-WAN companies, like you know, kind of in that kind of founding sector, so to say.
- 8:52Tim McConnaughy: Like Viptala Of the product.
- 8:54Chris Miles: Versa, versa, yeah, and there's one other one Avello Cloud.
- 9:00Tim McConnaughy: Yeah, Avello.
- 9:01Chris Miles: And then, but you know, then we started to see the likes of the major networking vendors.
- 9:05Chris Miles: Uh, just start like maybe or maybe, like I saw, mainly networking vendors, and like way in optimization they were just yeah the way in ops too, yeah, firewall vendors, firewall vendors, they would add like one feature and now it's like okay, well, now this is sd-wan it's like I don't know I don't know if you can really you, you know put your merit on that Like that's just like.
- 9:26Nicolas Vibert: Yeah, and it was like it went from like being SD1 to being SASE to being ZTNA.
- 9:33Tim McConnaughy: you know it's so quickly.
- 9:36Nicolas Vibert: But we were like yeah, like sorry, it was like even SD1, like, is that cloud networking?
- 9:40Nicolas Vibert: Because you know, you used to think about SD-WAN and you had, like, you are your branch device and you would say, oh, let's go and take all that traffic to Office 365.
- 9:49Nicolas Vibert: And instead of backhauling back to my data center and then through my internet pipe, I send it straight to my, you know, over my local internet link.
- 9:57Nicolas Vibert: That's some form of kind of cloud networking as well.
- 10:01Tim McConnaughy: Not, you know, not the yeah, well, this is interesting too, because the uh this is where we get into some other things where there's kind of a long-standing curiosity about like is saz cloud the same like?
- 10:12Tim McConnaughy: You know, like when, uh, we talk about this all the time, where, like customers are like, or microsoft is like, we have, uh, you know, so many million cloud customers and it's like, well, I mean they're, they're office 365 customers.
- 10:23Tim McConnaughy: I don't know if I would call them cloud customers.
- 10:24Nicolas Vibert: And it's like well, I mean they're Office 365 customers.
- 10:26Nicolas Vibert: I don't know if I would call them cloud customers.
- 10:27Tim McConnaughy: Sure, it runs on Azure, but I don't know if that makes them Azure customers.
- 10:32Tim McConnaughy: You know what I mean.
- 10:32Nicolas Vibert: Like it's not quite the same, Let me ask you guys, like where do you think cloud networking was invented?
- 10:41Tim McConnaughy: I mean like the CSPs.
- 10:43Chris Miles: Yeah, I mean mean ultimately, I think the.
- 10:46Chris Miles: If we look at the evolution of cloud, you know kind of start in the early days with, you know, launch of S3, and then you know, eventually more things started or like using cloud and needed the natural progression and eventually things needed to be, you know, able to talk to each other, right, I don't remember what was it.
- 11:02Chris Miles: When did VPC launch?
- 11:03Chris Miles: Was like 2010.
- 11:03Chris Miles: Wow, literally.
- 11:03Chris Miles: So that's to be you know, able to talk to each other, right and um, I don't remember what was it.
- 11:05Chris Miles: When did vpc launch?
- 11:05Chris Miles: Was like 2010, 2000.
- 11:07Chris Miles: Well, literally.
- 11:08Nicolas Vibert: So that's to 25th of august 2009.
- 11:11Nicolas Vibert: I found jeff biles uh, announced some blog posts.
- 11:14Nicolas Vibert: Oh, nice, nice, um, and it's just, you know, you.
- 11:18Nicolas Vibert: You read it and it's like, wow, you know.
- 11:20Nicolas Vibert: That's like close to 16 years ago and all still relevant, well-written, clear.
- 11:26Nicolas Vibert: The blog post was about, you know, being able to create a virtual isolated network connecting back to on-prem with a VPN, so that for me that feels like the origins and I'm sure some people will disagree, but it feels like the origins of, like, cloud networking.
- 11:45Tim McConnaughy: Well, here's the question, though Hold on real quick, because we got to.
- 11:47Tim McConnaughy: Some people will disagree, but it feels like the origins of like cloud networking.
- 11:49Tim McConnaughy: Well, here's the question, though Hold on real quick, cause we gotta.
- 11:53Nicolas Vibert: I'm waiting for the data center people to start screaming that like private cloud.
- 11:56Nicolas Vibert: What about private cloud?
- 11:57Nicolas Vibert: Yeah, and you think okay.
- 12:03Tim McConnaughy: I think the response to this wasn't, you know, things like OpenStack.
- 12:04Tim McConnaughy: Yeah, that's a very good point.
- 12:05Tim McConnaughy: Actually, I like OpenStack right.
- 12:06Tim McConnaughy: Yeah, that's a very good point.
- 12:06Tim McConnaughy: Actually, I think OpenStack would probably be, because, I mean, we're really talking about a model, we're not just talking about private cloud as a data center.
- 12:13Tim McConnaughy: That's not you know its own kind of abstracted workflow.
- 12:17Tim McConnaughy: Because to get to that on private, yeah, I think the first thing you would have been able to work with to do that would have been, yeah, openstack, to try to abstract away the compute and stuff.
- 12:27Nicolas Vibert: And they had the Neutron or Quantum plugin which was their way of creating virtual network and again I think that's my recollection where it was in response to the cloud providers and taking off and they wanted to cloudify the way networking was being consumed, on-prem right To offer a similar kind of experience.
- 12:48Nicolas Vibert: Yeah, it's again.
- 12:51Nicolas Vibert: We still haven't really got to the definition of cloud networking, right?
- 12:54Tim McConnaughy: No, no, no, no, we'll get there.
- 12:57Tim McConnaughy: We'll get there around 55 minutes or 60.
- 13:01Chris Miles: Well, it's funny because I think cloud has always been used pretty much as an abstraction.
- 13:07Chris Miles: Right At the end of the day, there's still kind of, you know, hardware and components running under the hood that we all are familiar with.
- 13:15Chris Miles: But I feel like, yeah, the cloud initially was supposed to be this term.
- 13:18Chris Miles: That was like somewhat agnostic and you know, we had private cloud, we have public cloud, but, like, private cloud is a very, very different experience than than public cloud and I feel, like the terminology has kind of just shifted cloud I mean.
- 13:32Chris Miles: In my mind cloud means public cloud, um, and what that ultimately translates to is, you know, basically using, uh, vendor or service provider specific APIs to interact with their environment to get it to do what you want to do.
- 13:46Chris Miles: So it's like I mean, that's what it sounds like to me.
- 13:51Chris Miles: I mean, ultimately, you're always going to be able to do what they give you access to right.
- 13:55Chris Miles: Yeah, just like MSP, right, there's no super level of customization that you could do with a private cloud Right.
- 14:02Chris Miles: So I mean, that's the way it translates to me.
- 14:05Nicolas Vibert: And I think that for me, cloud networking, it does involve some form of public cloud, because otherwise the definition just becomes too broad.
- 14:16Nicolas Vibert: Yeah, it's too generic.
- 14:18Chris Miles: Yeah, Otherwise it's just networking.
- 14:20Chris Miles: Really, yeah, networking.
- 14:25Nicolas Vibert: But I think what you said around consuming the MSPs APIs, I feel like the first kind of real form of kind of cloud networking companies, like the likes of Aviatrix, was really about like building a gap that the cloud networking, the MSPs where the networking constructs had some limitations.
- 14:48Nicolas Vibert: So the startup was like, oh, let's go and create a product that fits this gap.
- 14:52Nicolas Vibert: That's fair.
- 14:54Tim McConnaughy: Yeah, no, I couldn't agree more, 100%, 100% yeah, it's.
- 14:57Tim McConnaughy: In fact, if you look at the history of our company, if you look at the features we rolled out, first stopgap, fill in the blank.
- 15:03Tim McConnaughy: Like these don't exist in the hyperscaler and I think there will always be a limitation to what the hyperscalers can offer to customers.
- 15:11Tim McConnaughy: Just by the fact that they're hyperscalers, right, they can't give you the same granular level of control that you can give to if you're going to, if they give it to you, they got to get to everybody, right.
- 15:20Chris Miles: So that's yeah, because it's a service, right, like, like hardware, like hardware vendor can give you something off the shelf that does everything under the hood, because you control all of that and you know it's probably in your isolated environment, right.
- 15:31Chris Miles: But if you're providing a service, there's only so much you can do, um, for, uh, you know, like with r&d development, things like that, it just takes so much more work to get to that, get to that level I think every uh, even every msb, has a different stance and culture towards networking.
- 15:49Nicolas Vibert: I mean, I feel like AWS was, like you know, so developer-centric and I don't know, google is, like, so proud of its networking, so proud of its backbone and, you know, happy to share.
- 16:00Nicolas Vibert: Oh look, we've got cables, you know, under the Pacific Ocean, the pacific oceans.
- 16:05Nicolas Vibert: Look at that, it's amazing.
- 16:06Nicolas Vibert: And like they're just very, very proud of someone's networking and their pipes and their innovation around this.
- 16:12Nicolas Vibert: Uh, they take now, that's interesting yeah, they have a different perspective, I think.
- 16:16Nicolas Vibert: I think that's a cultural aspect to uh, to to the importance of networking yeah the like.
- 16:23Chris Miles: it's always cool when they show those things, but in my mind, whenever I see you know, um, you know a service provider, specifically a cloud service provider, kind of toting about like what kind of connectivity they've built with you know undersea cables, all this kind of stuff, all that says to me at the end of the day is like, there's capacity, like the like.
- 16:42Chris Miles: Capacity will probably never be my problem, which is good.
- 16:45Chris Miles: It doesn't change how I build networks and I'll be honest with you in the long run, the least interesting thing well, not the least, but one of the most least interesting things to me in networking has been QoS, and if I don't need that anymore, then I'm very happy with that.
- 17:01Nicolas Vibert: So I think this is progression for sure.
- 17:05Chris Miles: But I don't know.
- 17:06Chris Miles: Like yeah, networking to me like the undersea cables that's all cool, the CDNs that's cool as well, but like I'll be honest like that doesn't move the needle for me, like in terms of cool technology.
- 17:18Tim McConnaughy: So it's interesting, nico, you have the observation that Google cares a lot about its networking, because I think that's true.
- 17:25Tim McConnaughy: What you said about is building the undersea cables.
- 17:27Tim McConnaughy: I think all that is true, but, like, when I look at google's, the way that you as a customer have to consume google's networking, to me it seems like extremely developer centric.
- 17:37Tim McConnaughy: Like like don't even the concept of global vpc and specifically the idea that like we can just do it all for you.
- 17:44Tim McConnaughy: It seems like they really just want you to not care about networking, or just for me working with it.
- 17:49Tim McConnaughy: It seems, you know, like the auto building uh vpcs where they'll auto do all your subnets for you.
- 17:53Tim McConnaughy: It seemed to me like they they were focused on more.
- 17:56Tim McConnaughy: So it's interesting that the opinion that you have that is different yeah, it's.
- 18:02Nicolas Vibert: I mean to be fair, like I um, I was at cisco last week and I was showing a demo with a couple of colleagues that uh, which was like um meshing a couple of capabilities cluster one was on-prem, one was um in, uh, the cloud and we picked, we picked uh, gk, uh, because we thought actually from a networking perspective, that was the easiest.
- 18:25Tim McConnaughy: Oh, for sure, I think so.
- 18:26Tim McConnaughy: With the global VPC and everything and the way they do it.
- 18:29Tim McConnaughy: I think GKE is the easiest.
- 18:32Nicolas Vibert: And you know, doing some cool connecting machine clusters together, doing some low balancing across sites.
- 18:37Nicolas Vibert: That's a nice form of cloud networking.
- 18:41Tim McConnaughy: Yeah.
- 18:42Nicolas Vibert: It's interesting.
- 18:42Tim McConnaughy: I'm actually just getting into this myself because we're kind of doing some stuff with Kubernetes as well, so I've been so late, Like I know we had you on what like almost a year ago now or something like that.
- 18:52Tim McConnaughy: It's been a while and I was one of those things where I was like I'll get around to it.
- 18:56Tim McConnaughy: I didn't really get a chance until a few weeks ago, but the more I learned about it, the more interesting it is, especially the networking aspect of it about it, the more interesting it is, especially the networking aspect of it, even though it's like 90% of it is abstracted away, at least within the cluster, certainly within the cluster it is.
- 19:11Nicolas Vibert: Which is interesting from my perspective.
- 19:14Nicolas Vibert: It was my first time presenting at Cisco Live.
- 19:17Nicolas Vibert: I've been to Cisco Live many times but I've been presenting at KubeCon, for example yeah, and presenting our networking platform for Kubernetes.
- 19:28Nicolas Vibert: It's very different when you go to somewhere like Cisco Live.
- 19:32Nicolas Vibert: Compared to KubeCon, audience is very different.
- 19:34Nicolas Vibert: Yeah, exactly, very, exactly, very different audience and, like some of the KubeCon, they're more interested in like, what can you do with all this networking?
- 19:43Nicolas Vibert: Like you know more about the application stuff, can you do things like canary testing and load balancing and introducing new version of my app, do some redirection?
- 19:54Nicolas Vibert: Lots of different, more, more again application-centric, whereas I go to Cisco Live and what the first question I get is like, show me your packet work, show me the headers, and you know, show me BGP, you know, and it's just like oh boy, but so, yeah, it's kind of again a different culture.
- 20:14Nicolas Vibert: But what was?
- 20:14Nicolas Vibert: I guess?
- 20:16Nicolas Vibert: What I found fascinating is the platform and Kubernetes.
- 20:21Nicolas Vibert: Networking is about cloud-native applications, which is mainly containers and mainly managed and orchestrated by Kubernetes, and I think that's one of the reasons we were invited in this vendor's analyst report is because we do networking for cloud-n native applications.
- 20:37Nicolas Vibert: So does it qualify?
- 20:39Nicolas Vibert: As you know, is that a requirement to be cloud networking?
- 20:43Nicolas Vibert: Do you need to be able to support modern containerized applications, or is that just a kind of a side aspect of it?
- 20:52Nicolas Vibert: That's a great question.
- 20:53Chris Miles: Yeah, I mean, I think like we're at this point where we probably like I feel like we don't want to fall like in the same direction, like maybe security has where there's, you know, there's so many different categories for things, like there's, you know like so many acronyms, cnap, all this kind of stuff.
- 21:11Chris Miles: There's probably been two announced today as yeah, there's a lot um but like I don't know if we wanted like venture into that territory where we have like ultimate levels of classifications to every one of these things, like um, I mean, we're already there, we can generally talk about it, but there's just no, you know, like official, you know, once gartner does it, then then then it's real right um, but yeah, I don't know if I wanted to go that, that route, but I mean, ultimately there there is confusion.
- 21:36Chris Miles: So you know, the consumer at the end of the day, is going to be the one that's confused when they hear this term.
- 21:41Chris Miles: Right, so, um, it might be necessary, I don't know.
- 21:44Tim McConnaughy: So, so this, uh, you know you get me thinking, though, because, like Kubernetes, the whole thing with Kubernetes is that we, you know you can have this cloud native, Cloud native and Kubernetes like go together.
- 21:54Tim McConnaughy: Right, the CNCF owns the whole thing.
- 21:56Tim McConnaughy: Like there's so much it's joined at the hip.
- 21:59Tim McConnaughy: Right, we say cloud native, cloud native, cloud native.
- 22:02Tim McConnaughy: You kind of wondered, you know.
- 22:03Tim McConnaughy: Now we have to like, okay, what the hell does cloud native mean?
- 22:06Tim McConnaughy: In order to get to cloud native, what the hell is cloud native?
- 22:09Tim McConnaughy: We had a discussion on this as well we did, we did a while back.
- 22:13Chris Miles: Yeah, it's like I think it's strayed from what it what it used to mean or what it was intended to mean as you can force.
- 22:19Tim McConnaughy: You can run a kubernetes cluster on prem right or, you know, in a middle mile provider or something.
- 22:25Tim McConnaughy: I don't think I'm not, I don't know how many people do that.
- 22:26Tim McConnaughy: To be honest with you, I think a lot of people consume the, the managed kubernetes.
- 22:29Tim McConnaughy: Kubernetes is pretty complicated, but well, actually I mean the.
- 22:33Nicolas Vibert: I mean just again talking to customers at Cisco Live and KubeCon.
- 22:37Nicolas Vibert: So many are doing self-manage and you know, very often on the like, you know like OpenShift or Rancher, and that's why I had so many conversations around this last week at Cisco Live.
- 22:51Nicolas Vibert: Again, it's about like okay, I'm building my own Kubernetes cluster, managing my own on-prem, how do I connect to my Cisco ACI, for example?
- 23:01Nicolas Vibert: Yeah, of course, any other fabric.
- 23:06Tim McConnaughy: Just outside the cluster.
- 23:07Tim McConnaughy: How are we making connectivity right?
- 23:09Tim McConnaughy: Yeah, how do we expose our?
- 23:10Nicolas Vibert: applications applications.
- 23:20Nicolas Vibert: What's the best practices?
- 23:21Nicolas Vibert: Again around BGP and Ingress and make our cloud native applications accessible from the outside.
- 23:25Tim McConnaughy: Yeah, it's funny because with Kubernetes, specifically for Ingress specifically, you have to build, you need a load balancer service, something for the ingress to the service you've done.
- 23:35Tim McConnaughy: So now a load balancer now becomes part of cloud networking, Like all these services.
- 23:42Tim McConnaughy: These extra services end up being part of cloud networking.
- 23:46Tim McConnaughy: Right, it's not just networking anymore, there's all these services included.
- 23:51Nicolas Vibert: Yeah, so is service mesh a service mesh or an ingress controller?
- 23:56Nicolas Vibert: Is that cloud networking?
- 23:59Tim McConnaughy: I think it has to be with Kubernetes specifically?
- 24:01Tim McConnaughy: I think it has to be right, the service mesh especially.
- 24:05Tim McConnaughy: You've got your sidecar.
- 24:05Tim McConnaughy: You're building tunnels.
- 24:06Tim McConnaughy: You're just making a tunnel mesh between clusters with your sidecars.
- 24:12Chris Miles: That one almost ventures just into application networking.
- 24:15Nicolas Vibert: to me, yeah, maybe At the end of the day, I guess like what is that that's?
- 24:20Chris Miles: fair.
- 24:20Chris Miles: I mean it's turtles all the way down right.
- 24:22Chris Miles: Eventually it's the same thing, but like I don't know, we're probably splitting hairs.
- 24:28Tim McConnaughy: No, I mean, that's a fair point though Application, because it's the application.
- 24:32Tim McConnaughy: So yeah, I mean now that you're asking yourself, god, this is getting so crazy.
- 24:36Nicolas Vibert: So, philosophical.
- 24:38Tim McConnaughy: Yeah it's almost Socratic in the method, right?
- 24:42Tim McConnaughy: Because then you have to say well, is the Envoy like for Istio, is the Envoy an application or is it a networking?
- 24:51Nicolas Vibert: device or is it both?
- 24:51Nicolas Vibert: Yeah, yeah, yeah, I mean it's proxy-wise.
- 24:54Nicolas Vibert: So yeah, it's kind of.
- 24:55Nicolas Vibert: You know, defining a category is just really hard when it just keeps things keep evolving.
- 25:01Nicolas Vibert: But I think for me, I guess, the characteristics of cloud networking.
- 25:06Nicolas Vibert: There are things that I think we can say, okay, the one thing that all have in common for me is that they're API-centric.
- 25:13Nicolas Vibert: That would be, I guess, my own personal take, and maybe you know I'm sure there are also cloud networking products that are maybe more consumed through a UI, but I think the aspiration should be that you consume your cloud networking.
- 25:30Nicolas Vibert: Your networks are API, built through an API.
- 25:34Tim McConnaughy: Okay, okay, yeah, I think that's Well.
- 25:37Tim McConnaughy: What about Terraform?
- 25:38Tim McConnaughy: Did you consider that the same thing?
- 25:40Tim McConnaughy: It's IOC, right?
- 25:41Nicolas Vibert: Yeah, with an API, some form of automation, a playbook, a Terraform module, okay, yeah, yeah, that should be part of the goal when you start leveraging a cloud networking.
- 25:54Nicolas Vibert: Part of the goal when you start leveraging a cloud networking is that you template, create a template or automate it.
- 26:00Nicolas Vibert: If you claim you have a cloud networking product and you don't have an API, then you're lying.
- 26:12Tim McConnaughy: Or, at the very least, if your product is not interacting with the cloud provider APIs to do the building, like that kind of stuff.
- 26:21Tim McConnaughy: Yeah, I think that's definitely true.
- 26:23Tim McConnaughy: Yeah, I think after I asked about the Terraform question, I realized that what you originally had meant when you said that so yeah, it is APIs all the way down, right, that's how you generally interact with, whether you're doing it on a CLI, whether you're doing it on a CLI, whether you're doing it with their SDK, whatever.
- 26:38Tim McConnaughy: That is right.
- 26:39Tim McConnaughy: Terraform, it's an API call at the end of the day.
- 26:41Tim McConnaughy: So you asked a question on the notes here that I really wanted to get to and I don't want to pick out a specific company, but, like you had said, essentially is Middle Mile a cloud networking company, somebody that provides connectivity to the cloud?
- 27:01Tim McConnaughy: Would we consider them a cloud networking company.
- 27:03Nicolas Vibert: You have an opinion, yeah, you could argue, and again you could say things like Equinix, megapod.
- 27:10Nicolas Vibert: They provide some direct links to the cloud from on-prem to the cloud.
- 27:17Nicolas Vibert: I think they also enable you to connect your clouds together, so some form of inter-cloud connectivity.
- 27:27Nicolas Vibert: Now, I think because it's more of a physical layer to and from the cloud.
- 27:36Nicolas Vibert: I don't think it necessarily qualifies as such.
- 27:38Nicolas Vibert: I guess in my head it's more.
- 27:41Nicolas Vibert: I guess cloud network, in my head, is more about creating networks within a cloud environment that isn't consumed by applications that live in the cloud and that can be virtual machines, that can be bandwidth or that can be containers.
- 27:59Chris Miles: Okay, so real quick then I was going to say an important thing in that classification is they also provide the connectivity like direct connectivity options for like SaaS providers as well.
- 28:10Chris Miles: Right, so that's like services running on cloud, but maybe you're not getting into a private environment that you manage on top of cloud.
- 28:16Chris Miles: So it's like running on cloud, but maybe you're not, you know, getting into a private environment that you manage on top of cloud.
- 28:19Chris Miles: So it's like, yeah, like what does that translate to?
- 28:23Tim McConnaughy: Well, I also have to challenge a little bit the idea that if Megaport connects two clouds together but it's physical, that makes them not cloud.
- 28:32Tim McConnaughy: Because that then question is so if I connect AWS to Azure and I do it over the internet instead of using, because I mean, you know, there's no direct connect between AWS and Azure.
- 28:41Tim McConnaughy: That's obviously right.
- 28:43Tim McConnaughy: So is that cloud networking or it's going over the internet?
- 28:46Tim McConnaughy: Are we counting the internet as a medium?
- 28:49Tim McConnaughy: You know what I mean.
- 28:51Chris Miles: But if we're thinking about like this concept of at least the CSPs provided networking options, you're basically building networking across their backbones.
- 29:04Chris Miles: Whatever services they've exposed, they allow you to build networking on their platform.
- 29:08Chris Miles: What is different about that to Megaport or to Equinix?
- 29:11Chris Miles: That's the exact same thing.
- 29:12Chris Miles: They have an underlying set of hardware services, a backbone of something.
- 29:17Chris Miles: But the way you interact with it is essentially the same.
- 29:20Chris Miles: You make an API call and you say build this connectivity.
- 29:22Chris Miles: So how is it not cloud networking at that point?
- 29:26Tim McConnaughy: We're not saying you're wrong.
- 29:27Tim McConnaughy: I'd like to justify a little bit.
- 29:31Nicolas Vibert: I suppose it's.
- 29:32Nicolas Vibert: You don't necessarily use their networks to run applications.
- 29:39Tim McConnaughy: Okay, so it's that you're not building apps on their network?
- 29:42Nicolas Vibert: Yeah, and maybe I don't know enough about what they do.
- 29:47Nicolas Vibert: I guess it almost feels like a subcategory of cloud networking.
- 29:54Nicolas Vibert: Maybe this is how we kind of break it down right yeah clam cloud networking as a kind of overall category, and then you've got the intercloud, and then you have the I mean it's just not easy, right like there's a reason why everybody struggles with it.
- 30:08Tim McConnaughy: This definition, these definitions, is not easy.
- 30:11Tim McConnaughy: I think it's very hard to to draw these lines and to figure out what lines to draw.
- 30:15Nicolas Vibert: And you know we talked.
- 30:16Nicolas Vibert: You were saying like Cloudflare or maybe like CDN I don't necessarily Akamai.
- 30:22Tim McConnaughy: Yeah, that's a really good question, man.
- 30:24Tim McConnaughy: That's a super good.
- 30:25Tim McConnaughy: That's even harder than the Megaport one, by far, I think, or Megaport Equinix Middle Mile generally by far, because, you know, the CDNs are technically usually attached to the cloud backbone, but like they're not, so they're, they're delivering content right.
- 30:41Tim McConnaughy: That is, over a network that is usually cloud based in some way, whether it be Cloudflare or directly connected like with the AWS offers.
- 30:50Tim McConnaughy: Man, I don't know what do you think?
- 30:52Tim McConnaughy: Chris?
- 30:52Tim McConnaughy: That's a tough one.
- 30:54Chris Miles: Yeah, it is tough, but I mean that one one, that's one that I feel like has been around in some shape or form for a long time as well, like even before cloud oh yeah, cdns, yeah yeah well, like I mean, yeah, like I remember, like back in the day we used to, I used to work at a big mpls provider and like we got a lot of circuits from level three and at level three, had a lot of these kind of front front door scrubbing services and things that are just very adjacent to what those providers do today and obviously they have a much bigger footprint and things like that.
- 31:24Chris Miles: So it's like I don't know Then so does it?
- 31:27Chris Miles: If that's the case, then the cloud networking start back then, like yeah yeah it is, it is, it is, it is, it is, it is.
- 31:35Nicolas Vibert: Yeah, yeah, it is, it is.
- 31:36Nicolas Vibert: It is very hard to say like, yeah, what, what was?
- 31:37Nicolas Vibert: What started it all?
- 31:39Nicolas Vibert: Um, yeah, okay, so what about security?
- 31:43Nicolas Vibert: Then?
- 31:43Nicolas Vibert: Like, do we is, let's say, consistent security across cloud?
- 31:49Nicolas Vibert: Is that a must?
- 31:50Nicolas Vibert: Is that like um, because we can't do talk, we can't talk about cloud networking without talking about cloud networking.
- 31:57Nicolas Vibert: Security Is encryption, is consistent networking across the multiple clouds?
- 32:06Nicolas Vibert: Yeah, some form of requirement to say, okay, we do cloud networking.
- 32:12Tim McConnaughy: So, yeah, obviously, we work for Aviatrix and we literally this is kind of the mission statement of the company.
- 32:22Tim McConnaughy: So, to put the company aside, I think, even putting the company aside, I think you know if you're gonna this whole shared responsibility model that all providers have, you know, customers are still in charge of their own data, right, the data that's runs across their cloud networks.
- 32:37Tim McConnaughy: Now it's encrypted in the rack, essentially, or across the backbone, or however you want to say it on the cloud provider side, but ultimately a customer, but that you know.
- 32:45Tim McConnaughy: Then you look at things like salt typhoon uh, the sulfide typhoon attacks, uh, you know owning telecom networks and being able to just do man in the middle, you know captures of open, of unencrypted traffic.
- 32:58Tim McConnaughy: So, yeah, I mean, I do think I think it's a requirement, in that a customer would be very foolish not to run some of their, you know, do it themselves.
- 33:09Tim McConnaughy: I wouldn't trust the provider to secure all of my traffic, but does it?
- 33:14Tim McConnaughy: Is it quote unquote required?
- 33:15Tim McConnaughy: Like from a technical RFC perspective, if you will?
- 33:18Tim McConnaughy: I mean, obviously not right.
- 33:20Tim McConnaughy: Like AWS supports GRE across you build a GRE tunnel from a TGW Connect, for example, and of course you can't do GRE in Azure, but that's because that's what they're using.
- 33:31Tim McConnaughy: On the underlay right.
- 33:32Chris Miles: It's funny how many directions this can go in, because that's the first thought you had, tim, about this.
- 33:39Chris Miles: I call back to just when we're talking about the different architectures that we see within cloud and how it's a very strong fundamental shift with what we've been doing for 20, 30 years at this point.
- 33:52Tim McConnaughy: Oh yeah, the Volus coupling model.
- 33:53Chris Miles: Yeah, well, not even that.
- 33:54Chris Miles: I'm just talking.
- 33:59Chris Miles: If we think of the concept of a global VPC, like that's one big network that exists everywhere.
- 34:01Chris Miles: Like the difficulty to implement something in there, like zero trust, which is a prominent thing you know from from a networking perspective.
- 34:08Chris Miles: Like doing that in a global construct that is just all meshed together at one point, like that becomes a conversation.
- 34:15Chris Miles: That's very difficult to get that in there, right?
- 34:19Tim McConnaughy: What's your opinion, Nico?
- 34:22Nicolas Vibert: I can't imagine doing like a global VPC back when I used to be like a network operator.
- 34:29Nicolas Vibert: I just imagine there's a difficulty of doing something that is so well crafted that you know like you you get, you know you deploy VPC in GK and you don't really care Like you, just you know your application receiver, it just works and you know.
- 34:51Nicolas Vibert: And that's just thinking again, thinking back to the days where I had to connect multiple, multiple sites together and having to worry about addressing.
- 35:00Nicolas Vibert: And I think that's the beauty of like a really well designed cloud networking like GKE, but again also, providers also do it very well, but it's all the intelligence and the automation under the hood to, you know, make it happen and being able to replicate it on-prem is just about impossible.
- 35:20Tim McConnaughy: We've said that for even when Alex was here, that we used to talk about all the time that the people that are going to win the game are going to be yeah, I know who is that?
- 35:28Tim McConnaughy: I don't know who that is either the people who can, whatever company or companies finally are able to build the product that can reproduce that level of the consumption model of cloud.
- 35:40Tim McConnaughy: But in an on-prem data center, man, they're just going to win the game.
- 35:46Tim McConnaughy: Like it's going to win the game because it's impossible, it's like so impossible but everybody would benefit from it.
- 35:51Tim McConnaughy: Like everybody would love that, because nobody's going to be able to fully evacuate.
- 35:54Tim McConnaughy: Unless you started in the cloud, you're probably never going to truly leave all of your data centers behind, right?
- 36:01Tim McConnaughy: You're going to need something on prem.
- 36:03Tim McConnaughy: So, yeah, man, I yeah.
- 36:04Chris Miles: Yeah, I think, I think it was very easy not easy, but it was easier, at least in um the pre-cloud days to kind of classify what type of networking, like products and things were out in the market, because there was always this kind of delineation of like physical location like like branch routing, data center routing or data center switching was.
- 36:26Chris Miles: It was a very different thing, right, that's like, even if I just say that that implies certain things about the hardware campus and about it.
- 36:33Nicolas Vibert: What if its capabilities are?
- 36:35Chris Miles: know, right off the bat, right, whereas cloud has just become this extension of IT, right, it's not?
- 36:41Chris Miles: It's like everything runs there, right.
- 36:43Chris Miles: So it's like it's incorporating the branch the way in, the like.
- 36:46Chris Miles: Everything is there, right.
- 36:48Chris Miles: So it's just like so convoluted, yeah, yeah.
- 36:52Nicolas Vibert: So I think maybe we just need some new vocabulary, more acronyms, yeah, yeah, but I think maybe we just need some new vocabulary to describe it More.
- 36:58Nicolas Vibert: Acronyms yeah, probably.
- 37:00Nicolas Vibert: But yeah, we need to separate it because I think it just becomes very complicated and then I end up having to answer a questionnaire from vendors and the questions that maybe apply to me, to my products, don't apply at all to you know.
- 37:20Nicolas Vibert: I don't know like a restart Wi-Fi or whoever.
- 37:24Chris Miles: So it's Gartner's problem, basically.
- 37:28Tim McConnaughy: I think that's true, though I mean speaking of someone who's also had to fill out one of those 40-page reports like there are.
- 37:33Tim McConnaughy: Definitely sometimes they'll ask a question or be like explain your capability, and you're just sitting there like scratching your head, like tapping the pen on the desk, like huh, I got to put something here, but like our product really doesn't play in this particular space.
- 37:48Nicolas Vibert: Yeah, well, one we.
- 37:49Nicolas Vibert: We had a question recently which was all your your product doesn't support like drag and drop and your product?
- 37:55Tim McConnaughy: doesn't support drag and drop.
- 37:56Tim McConnaughy: You're like no, not exactly.
- 37:59Nicolas Vibert: What?
- 37:59Nicolas Vibert: Because maybe there will be some products where you can do some kind of Right like a policy creation in a UI or something.
- 38:09Chris Miles: Yeah, a map type thing, yeah.
- 38:13Nicolas Vibert: I'm not sure that, as a decision maker, we think, oh, I won't buy this product.
- 38:20Chris Miles: Gotta have that drag and drop man.
- 38:23Tim McConnaughy: Yeah, I can't build rules if I can't drag and drop things in my UI.
- 38:27Tim McConnaughy: That doesn't exist.
- 38:29Nicolas Vibert: Yeah.
- 38:29Tim McConnaughy: Now that's really interesting, I don't know.
- 38:32Tim McConnaughy: So I know we're running out of time, but I don't know if we got to an answer and I don't think the three of us are authoritative enough to make an answer for everyone, anyway, but even for ourselves.
- 38:46Tim McConnaughy: It's very convoluted, it's very ephemeral, it's changing all the fucking time.
- 38:50Tim McConnaughy: Yeah, it's almost like and this is the problem with a lot of things, right, not just networking, but also security, as we pointed out, it's very reductive, right?
- 38:59Tim McConnaughy: So, in order to get to the bare minimum the MVP definition, it becomes so reductive that you can almost sweep everything underneath it, which is what you're trying not to do, right, by defining it.
- 39:13Nicolas Vibert: Yeah, I won't even even try.
- 39:14Nicolas Vibert: I enjoy the, the, actually the diversity, uh of of cloud networking and the whole.
- 39:22Nicolas Vibert: Um, even a few years ago, the way I thought of the cloud networking is different from what I think of it now, and maybe you know, in the same five years time, like, I guess what, what do you think like cloud networking will look like?
- 39:34Nicolas Vibert: You know, and can you answer this without mentioning ai?
- 39:38Chris Miles: no, no, that's as far.
- 39:41Chris Miles: We got this far without saying ai, that's great yeah well.
- 39:45Tim McConnaughy: So I mean, but yeah, we're not gonna.
- 39:48Tim McConnaughy: I don't think, I I don't even know right, like it's almost like a uh, what's the word?
- 39:51Tim McConnaughy: What I'm looking for like the uh singularity, like the technical singularity, like lies five years in the future, now that AI is everybody's fricking, finding new and new, newer and newer things to do with AI and we're getting closer and closer to to Skynet or whatever.
- 40:06Nicolas Vibert: Like who can even say and that's something we have now seen in the past couple of years is in in vendor analysis asking does your product support some form of AI?
- 40:18Nicolas Vibert: And I always like to kind of distinguish between is it about AI for networking, do we leverage some form of AI to optimize network traffic, predict patterns, or is it about making the network more robust, quicker for AI workloads?
- 40:38Nicolas Vibert: And I think both of them apply.
- 40:41Nicolas Vibert: I think both are requirements we're going to see more and more from not just kind of cloud networking but broader networking products is can your network cater for AI workloads and does your network leverage AI to provide better performance?
- 40:58Tim McConnaughy: Right, yeah, so this is interesting because the CSPs are like whole hog on basically developing their own silicon, which they've been doing for a while, but specifically for AI.
- 41:11Tim McConnaughy: They don't want to be beholden to NVIDIA or anybody for GPUs a while, but specifically for AI, like they don't want to be beholden to NVIDIA or any of the you know any anybody for GPUs and GPU.
- 41:22Tim McConnaughy: So doesn't that also come with a requirement then to and maybe this is why all these we reported on the news a few weeks ago that you know Microsoft is planning to spend what?
- 41:28Tim McConnaughy: A hundred billion dollars on their, on their upgrading their infrastructure, and like AWS said 75 and Google said like 80 or something like that, do you think a lot of that is going to build the networking for AI, meaning networking to support AI workloads?
- 41:44Tim McConnaughy: Do you, you know cause people may not be building their own, or do you think we'll see a reduction, like with deep?
- 41:49Tim McConnaughy: You know this, the deep seek thing was like 50, 50, which is what I kind of expected, which like, yeah, there are things that are good, but also a lot of it was kind of snowed over.
- 41:58Tim McConnaughy: It was a snow job of burying the lead on a lot of the costs and stuff, but it still represents a movement forward towards making it more.
- 42:08Tim McConnaughy: What's the word I'm looking for?
- 42:09Tim McConnaughy: Affordable, essentially to do AI, so do you think they'll just kind of meet in the middle somewhere?
- 42:15Tim McConnaughy: What do you think we're going to see first?
- 42:18Nicolas Vibert: I am equally as excited and dubious about AI for networking.
- 42:24Nicolas Vibert: I guess for a couple of reasons.
- 42:27Nicolas Vibert: One is I wrote a blog post about machine learning for networks 15 years ago.
- 42:30Nicolas Vibert: I wrote a blog post about machine learning for networks 15 years ago.
- 42:34Nicolas Vibert: I remember being I got the chance to sit in a room with like a Cisco fellow which is like the highest engineering level at Cisco and he was presenting some machine learning capabilities that he was working on at the time.
- 42:49Nicolas Vibert: That was 2000.
- 42:50Nicolas Vibert: It was more like maybe 2015, but it was like it was maybe 10 years ago.
- 42:58Nicolas Vibert: But it was, like you know, way, way, way before we you know, we yeah.
- 43:04Nicolas Vibert: And I got very excited about the possibilities, but nothing from what I know kind of came out of it.
- 43:11Nicolas Vibert: Right, it was, maybe it was maybe it was too early, but clearly, you know, we've seen like some amazing advancements and I'm a more than daily user of ChatGPT, but I still have some I really want to see like really applicable use cases.
- 43:30Nicolas Vibert: Like show me okay, networking has been able to help us make a better decision for this packet, right?
- 43:36Nicolas Vibert: Yeah, it was supposed to go and follow the you know the rising table and I could not hang on.
- 43:41Nicolas Vibert: we'll just go and send it to elsewhere because of you know conditions, whatever that is, yeah, yeah, um, yeah yeah, just just I want to see some more evidence, but I'm, I'm, I'm excited and I think just it's going to really help us make, create better products, help us develop our software faster, for sure.
- 44:07Nicolas Vibert: But we still want to see a bit more before.
- 44:11Nicolas Vibert: Let's say, I trust AI to enforce some security policies for me, for example.
- 44:20Tim McConnaughy: That's the one.
- 44:20Tim McConnaughy: Who was it?
- 44:21Tim McConnaughy: It was John.
- 44:22Tim McConnaughy: We had John Capobianco on there.
- 44:23Tim McConnaughy: We were asking him the same thing about.
- 44:26Tim McConnaughy: You know, when is it going to be the point where somebody is going to trust this agent like an AI agent enough to to actually go do network-level changes that could just blow up the whole network?
- 44:36Tim McConnaughy: Like, where's that?
- 44:37Tim McConnaughy: Where do we get to that part where somebody's okay with pressing that button and walking away?
- 44:41Tim McConnaughy: You know, essentially so I think I'm with you.
- 44:44Tim McConnaughy: I think it's going to still be a long time before we get to that, no matter what, right.
- 44:51Chris Miles: We're too big of control freaks for that at this point.
- 44:56Tim McConnaughy: Well, network engineers have to be, because those five nines of uptime are on us.
- 44:58Tim McConnaughy: Alright.
- 45:01Tim McConnaughy: Well, we'll go ahead and wrap it there.
- 45:03Tim McConnaughy: Nico, as always, it's awesome having you on and I'm really glad we could do it.
- 45:07Tim McConnaughy: We'll have to do it again in the future, any time any final thoughts there, chris, before we roll up.
- 45:15Chris Miles: No, I was just going to say Nico.
- 45:17Chris Miles: Where can people find you online?
- 45:19Nicolas Vibert: Yeah, so you can find me on LinkedIn Again.
- 45:24Nicolas Vibert: That's probably where I'm most active.
- 45:28Nicolas Vibert: So LinkedIncom slash Nicolas Viver.
- 45:34Tim McConnaughy: We'll get it in the show notes too.
- 45:35Tim McConnaughy: Yeah, yeah, yeah, all right.
- 45:37Nicolas Vibert: Good night people.
- 45:39Tim McConnaughy: All right, everybody.
- 45:40Tim McConnaughy: Well, I don't know if we got to the exact answer, but hopefully somebody found some useful information in all of this.
- 45:47Tim McConnaughy: As always, I'm Tim, this is Chris, our guest, nico, and thanks for listening or watching, and we'll see you next time.