so to to add a concrete example to that, right, within academic papers, not a standard, but you know, quote, unquote, this, these are the best practices again, you know, this is hard engineering discipline, which came up with the concept of just a hardware abstraction layer, right, not a standard hardware abstraction layer that just spoke about, what are the benefits that you can get right? Can we actually have the peripherals, you know, the NIC vendors, the Broadcom, etc. Can we have them right? quote, unquote, drivers, if you will, rather than SDKs, because that involves cadence between, you know, the producer and the consumer, which we can't really manage right to SDK is just the anathema of writing a spec in a standard, can we actually write up our hardware abstraction layer, building standards around that became switch abstraction layer and the switch vendors, unless you had this kind of gravity like Microsoft has with their data centers, you could not go and talk to Broadcom and say, we need whatever your drivers are, we need you to make sure that they acknowledge and stick with this interface. As we do these releases, you have to be compatible because we are buying n number of NICs so they were able to just push that weight around and establishing that standard. Now Now that's a very relevant standard right Broadcom will tell you other than any other thing to any of the switch, render, Broadcom will on the datasheet spec sheet will tell you what their release cycles are. For psi specific decide, yes, Microsoft uses them. But now more and more right and video uses them. Dell has an enterprise release a sonic enterprise release as well. There are tons of companies out there now. But Broadcom actually declares that writes that so that has quote unquote become a standard now that anyone else that wants to come in and be you know, network interface card provider will have to stick with it. Newer vendors that are coming into space, not necessarily a Nic vendor, but you know, purpose basic vendors. They are trying to figure out, hey, we're trying to get into the market. What are the size standards that we should just run too, if we are exposing quote unquote, the SDK, you know, is that P four compatible or not? So even though these are for profit enterprise companies, they're being driven from the start to what the standards are, because they realize that if we want to be a differentiator, we have to abide by some p four spec, or if it's an API, if it's a driver, it has to be, you know, C compatible.