IPv5 never existed, oh! fuck off you smug self congratulatory prick. if theres a v4 and a v6 stands to reason there's a v5. I'll go on to explain my personal experience of it. But before I go further, listen fuckwit - don't do driveby on posts I've put up on other groups just cos you want to prove that you cock is bigger. So what I don't give a shit, I'm here to look at naked and semi naked chicks and get turned on by them. Fucking hell this is a members only soft core art sleaze site.
Anyway cockchops doesn't belive there is an IPv5 even though it was a typo on my part as there have been moves afoot to move from IPv4 to IPv6.
So to start with some historical context in the early to late 1990's I worked for a US outfit called Dynatec Communications. They were the dogs bollocks in their day, just to summarise they developed and built milcom spec emp data comms kit for US Military US Militrary allies (S.Korea Japan Australia) NATO and Israel. Plus we did Frame Relay, Matrix Systems (mainly for Japanese Banks and Wall St.) and TelCo Exchanges. Interestingly, Cern was one of our big customers back then where Sir TBL developed HTTP. Not surprisingly really the kit could shift shitloads of data reliably but it wasn't one of the fastest known to man.
To side track for a moment our R&D dept (of which I was a member) developed digital data over Electricity cabling (it took 15 years for that to end up as Homeplug), we intended it to be used over the power companies cable and pylon infrastructure to shift huge amounts of data around countries. Unfortunatly, the ELF generated tended to kill small birds and wildlife, and could induce suicidal depression in humans living nearby. We then switched to an urban environment using it over streetlamp cabling unfortunatly, there all the streetlamps acted as gigantic arials so all you needed was a radio to pick up the data and decode it.
We were also one of the first companies to put out a comercial Telco VOIP system way before Skype, but as this was the mid 90's and audio compression wasn't really a viable option except in University R&D labs and being developed by competitor companies we were a bit shafted (this is where IPv5 starts to rear its ugly head). Patent infringments and all manaer of shit like that was flying back and forth. Now, the realtime streaming audio data system we had worked on closed source principles (this was way before the cathedral and the Bazar) and fuck it the amount of hard cash a Telco, Bank, Government was paying for this we could do it over closed protocols, and no one really gave a shit about interoperability. If someone said Company X can't connect to our data network, we'd go "Fuck em - they have to buy our kit".
Problem was with that as a business model and business attitude we missed the ball with Cisco, they took us totally by surprise and by 1996, they were having it away with large chunks of our customer base. Trouble was we relied too much on the big fuck off Frame Relay and Matrix Systems and the MilCom (the day I was made redundant (1997) we finished two installations for the Israeli Air Force and the Royal Jordainian Airforce turned out they were the final big orders - nothing else of that size came in from that point).
So where does IPv5 fit into all of this - well it was (and still is but no one really bothers with it) an experimental stream protocol it provided real time end to end garantees and QoS which is very important when transmitting real time Audio Data. Espcially when you consider in the 90's you had to down step to baud rate modem from the Telco infrastructure. You don't really want large chunks of your conversation being dropped out while you are chatting. All of this layed the ground work for VOIP apps that came to being in the early 00's.
I think what this actual shows is that it takes a lot of time for really useful technology to filter down to the end users. It would be more interesting to know what is going on in University R&D labs at the moment as it will take about 15 years for it to become common place. So if anyone is doing a Bsc CS and wants to let me know I'll get my three and a half year old daughter prepared now.
Anyway cockchops doesn't belive there is an IPv5 even though it was a typo on my part as there have been moves afoot to move from IPv4 to IPv6.
So to start with some historical context in the early to late 1990's I worked for a US outfit called Dynatec Communications. They were the dogs bollocks in their day, just to summarise they developed and built milcom spec emp data comms kit for US Military US Militrary allies (S.Korea Japan Australia) NATO and Israel. Plus we did Frame Relay, Matrix Systems (mainly for Japanese Banks and Wall St.) and TelCo Exchanges. Interestingly, Cern was one of our big customers back then where Sir TBL developed HTTP. Not surprisingly really the kit could shift shitloads of data reliably but it wasn't one of the fastest known to man.
To side track for a moment our R&D dept (of which I was a member) developed digital data over Electricity cabling (it took 15 years for that to end up as Homeplug), we intended it to be used over the power companies cable and pylon infrastructure to shift huge amounts of data around countries. Unfortunatly, the ELF generated tended to kill small birds and wildlife, and could induce suicidal depression in humans living nearby. We then switched to an urban environment using it over streetlamp cabling unfortunatly, there all the streetlamps acted as gigantic arials so all you needed was a radio to pick up the data and decode it.
We were also one of the first companies to put out a comercial Telco VOIP system way before Skype, but as this was the mid 90's and audio compression wasn't really a viable option except in University R&D labs and being developed by competitor companies we were a bit shafted (this is where IPv5 starts to rear its ugly head). Patent infringments and all manaer of shit like that was flying back and forth. Now, the realtime streaming audio data system we had worked on closed source principles (this was way before the cathedral and the Bazar) and fuck it the amount of hard cash a Telco, Bank, Government was paying for this we could do it over closed protocols, and no one really gave a shit about interoperability. If someone said Company X can't connect to our data network, we'd go "Fuck em - they have to buy our kit".
Problem was with that as a business model and business attitude we missed the ball with Cisco, they took us totally by surprise and by 1996, they were having it away with large chunks of our customer base. Trouble was we relied too much on the big fuck off Frame Relay and Matrix Systems and the MilCom (the day I was made redundant (1997) we finished two installations for the Israeli Air Force and the Royal Jordainian Airforce turned out they were the final big orders - nothing else of that size came in from that point).
So where does IPv5 fit into all of this - well it was (and still is but no one really bothers with it) an experimental stream protocol it provided real time end to end garantees and QoS which is very important when transmitting real time Audio Data. Espcially when you consider in the 90's you had to down step to baud rate modem from the Telco infrastructure. You don't really want large chunks of your conversation being dropped out while you are chatting. All of this layed the ground work for VOIP apps that came to being in the early 00's.
I think what this actual shows is that it takes a lot of time for really useful technology to filter down to the end users. It would be more interesting to know what is going on in University R&D labs at the moment as it will take about 15 years for it to become common place. So if anyone is doing a Bsc CS and wants to let me know I'll get my three and a half year old daughter prepared now.