Replies to post #65060 on Rim Semiconductor Company (fka RSMI)

[beechbreak1]

Dr. Chan,

I see people posting a "linked in" link. I was curious if you made this or was it someone making it for you to discredit you?

Well duh. Of course it was done to discredit him. But the real shame is that it wasn't necessary. He discredits himself with every post. RIM is going NOWHERE. Ray & Dumbo are liars. Period. End of story.

[beechbreak1]

On the Rim Semiconductor site.....when you go to the Residential IPTV Under Cupria applications it gives you multiple links.

Oh my. The RIM SEMICONDUCTOR SITE gives multiple links to reputable companies? You're kidding right?

[ken_chan]

The telecommunication companies that are referenced on that website are unquestionably potential target customers for Rim Semiconductor. It’s a bit ironic that you mention that, as I will be providing more information on something related to that early next month, as I will be in attendance for a major telco meeting (specifics will be disclosed at that time). That list would be best thought of as a sub-set of potential Rim clients, as there are some key names that are missing there, especially in the China and Europe regions.

The effort to produce a million chips is nothing to be concerned about, and is a routine procedure for a foundry. There is some initial time needed to program the machine specifications to precise wafer etching settings and chip details and then from there it’s essentially an automated mass production effort. The only delay that can occur sometimes is if another client has a massive order for the foundry, their machinery can be tied up. But with Rim selecting TSMC as their manufacturer, that shouldn’t be a problem. They are a top notch organization, one of the best in the world! Trust me on that, as I am very familiar with China based companies in this sector. If you want some additional information on the fabrication process, please read the following Wiki article: http://en.wikipedia.org/wiki/Semiconductor_fabrication_plant

In terms of the timing of the chip production, there is a slim chance that the ratification vote could be rejected or even accepted on a conditional basis. Therefore, it would be unwise to produce the chip on a mass scale until after the ratification process has been completed. This may seem a bit odd to some people because normally when someone (such as Rim) has such a great product they wield the power, so to speak. The situation is somewhat difficult to understand with Rim and Cupria. It can best be put this way: The clients that will be using the technology are potentially very high profile customers, and they are in a sense ‘pulling the strings’ to a certain degree. This causes delays and is understandably frustrating to investors, but the long-term rewards as a result of this will be much greater. In fact, the ISPL ratification and the subsequent Cupria deployment will make others in the industry a technology epigone or even entirely obviated. A little more time and patience will reveal this more clearly.

Another related question that I would like to address, as many people have inquired about it, is as follows:

How long does it take a potential client company to test a chip like Cupria?

Well I cannot speak on behalf of Rim specifically, but since it’s a legitimate inquiry, I will do my best to clarify it based on my own experience in similar situations.

First of all, the chip has to be implemented on a test environment on the customers site and an end-to-end precision and compatibility test must be done. If the system ‘works’ after this initial test, that doesn’t automatically give them the green light to declare that everything is good. Its imperative that additional testing be done for a period of usually a few months to obtain statistics on key elements. For example, the company would want to test the frequency of lost data packets. If you simply tested the system for 2 days, it would not provide accurate information on items like that. However, if you did it for a couple of months, it would provide much more accurate information on the reliability and performance of the system. Generally speaking, the objective of the testing phase would be to obtain statistics on the following items:

-Service continuity and percentage of downtime
-Average time to recover from service outage downtime
-Lost data packets
-Bit errors
-Secure file transfer ability
-Pairwise equality for alternative binary predicates
-Lexical encryption ability
-Overall encryption strength
-Tampering (ie: hacking) defense ability
-Maximization of available resources
-Deployable modes (ie: Carrier VoIP-based networks)
-Total network element processing
-Multiple switch access using pure IP network
-Utilization of industry-standard protocols like TCP/IP, Ethernet, etc
-Capabilities to wireline and wireless switching networks on a standard platform
-Digital communications systems frequency mode testing
-Ciphering algorithm reliability

For example, on another technology project that I worked on recently, we were testing bit encryption for a point of sale system in the following manner:

an x-bit STRING is subdivided into y-bit substrings AB0,AB1…ABi so if we have a string:
0x0123456789ABCDEFFEDCBA987654321086545381AB594FC28786404C50A37…
we have:
AB0 = 0x0123456789ABCDEF
AB1 = 0xFEDCBA9876543210
AB2 = 0x86545381AB594FC2
AB3 = 0x8786404C50A37…
In binary this would be:
000000010010001101000101011001111000100110101011110011011110111111111110…
with AB0 = 0000000100100011010001010110011110001001101010111100110111101111
AB1 = 1111111011011100101110101001100001110110010101000011001000010000
AB2 = 1000011001010100010100111000000110101011010110010100111111000010
AB3 = 1000011110000110010000000100110001010000101000110111…

Each test starts by showing the various inputs to the procedure block. Thereafter both of the keystream blocks are shown. The normative part of the specification of the block cipher is also considered. The initial test set lists all values in their binary version and so forth (I wont go into all the details, but this is just so you guys get the idea).

After the data from the testing results are obtained, they can then take the next step to correct the deficiencies or implement the system into the production environment. Investors may not like to hear such things as long time frames, but I think its important for them to get a realistic picture of how the industry works. The good news is that the testing process has already begun for many of the target clients, so we could very well be in the late stages of testing and close to deployment. In fact, we would easily see several deployments in rapid succession (after the ratification vote) resulting in a mass influx of revenue for Rim. Keep in mind that there is a reason why Rim selected TSMC to manufacture their chip – TSMC does NOT accept small orders. Rim Semiconductor is ready to shake up the world in ways that are even bigger than what some of their long time supporters expect.

Kindly,
Ken

PS: the linked in URL that you provided is not me – I am in no way connected to the Telewise organization.