Stolen technology... Also, DVNTF's next contract...hmmmmmm
If stolen technology was the case, why would a "leading" telecom company sign with them? Even more so, why would Certicom sign with them? And even more so, why would MSFT sit on the board of directors in a scandalous company, especially when MSFT has enough problems of their own? And even MORE so why would NSCP sit on the board of a scandalous company? (especially when NSCP is scrambling to save it's self?)
Are MSFT and NSCP really in this together. Ever herd of conflict of interests? But hey, how did MSFT "obtain" NSCP's browser technology in the first place? It sounds like all of these boys have worked together before.
My question is: Why is DVNTF's president meeting with ORCL in two weeks?
Who cares? It's all speculation. The bottom line is this:
Big boys can sniff out flops pretty easy. If this was a flop, MSFT, NSCP, HWP, ORCL, MOT(?), Certicom, etc. would have lost interest after 1 month of solid research in their technology... it's been 3 months and momentum is building, tests are being done, contracts are being signed.
The next contract sign may be with the Canadian bank, NSCP, ORCL or CSCO. HWP is a very conservative company and is always slow to adopt new technology. However, groups within HP are distributing info about DVNTF as we speek and the feedback is very positive. MSFT is not as desperate as NSCP or ORCL. ORCL may want to implement their technology with the "Network Computing" idea of theirs. DVNTF's technology could resolve ORCL's issues with authorization/permission to various groups, domains, resources/applications, etc... in the "Networked Computing" environment. NSCP could implement DVNTF's technology to enhance their e-commerce move. CSCO could use their technology for various network infrastructures. In a nutshell, DVNTF's technology is very "portable". The question remains:
How will their technology be used for:
1. Networking. (VPN's, routers, clients, servers, databases, authorization/permission to various groups, domains, resources/applications, etc...)
2. Applications (API's, unauthorized distribution, source authentication, application access levels)
3. Wireless devices (secure data transmissions, authorized senders and recipients)
4. EBusiness peripherals (Verifone products, smart cards, printers, etc...)
5. Customer and reseller verification/authorization/security/confidentiality
6. Databases.
I've talked extensively with the president and "chief" engineer about their products and technology. Certain components must be adjusted to fit the needs/requirements of larger potential customers (i.e. HWP, NSCP, MSFT). Perhaps this is why big boys sit on the board and DVNTF is meeting with ORCL. Who knows? All I know is that DVNTF is drawing a lot of attention. Something is happening. And it's not small. But hey, "all that glitters is not gold". In the end it all comes down to meeting expectations (the "beef", as it were, that you mentioned earlier). Well, it's bedtime for me. Hopefully tomorrow we'll see another gain.
P.S. As far as Entrust (spin-off of Nortel) is concerned, they don't even come close to VRSN OR DVNTF. Entrusts "solution" could be compared to this: Let's say your low on memory. You have two options. 1. Buy more memory. 2. Buy "special" software that "doubles" your memory. Entrust provides #2 as far as e-commerce security is concerned. |
