I'm not overlooking it in the least. The discussion revolves around devices which will require a dongle, not around those which do not. Oh, and by the way, the lack of an external STB is not a feature of OCAP. It is the primary reason for separable security and CableCard in the first place. The problem is, there is no standard for bidirectional hosts. Only if the CATV vendor in question supports OCAP. Scientific Atlanta doesn't. Of course, it will still function perfectly as a unidirectional host, but no interactive services, inlcuding SDV, unless the vendor has OCAP hardware. You missed the point entirely. The question is why should a receiver manufacturer go to the trouble of designing a dongle-ready set when they can simply produce a non-separable security set and let the CATV provider handle it when the perceived value to the customer is the same? That makes no sense at all. 1. The Comcast Tivo is a DVR, not a TV. Almost nothing of its functionality is of any use to a TV. 2. The subscriber is not allowed to download anything as far as OCAP is concerned. Downloading under OCAP is entirely the prerogative of the CATV vendor. The subscriber has no choice either way and cannot exert control either for the software to be loaded or prevent it from being loaded. 3. OCAP is not a UI nor an OS. It's middleware. The TiVo software consists of an OS (Linux 2.4) and a UI, plus some supplied or available middleware. 4. Although all OCAP software by design must be compatible with any OCAP device, the OS and all operational software including the UI are specific to a device. TiVo software won't run on a TV unless the software is modified to run on the platform or the hardware is modified to emulate the TiVo hardware. Downloading OCAP software won't modify the UI only allow it (or force it, if you will) to provide additional specific capabilities. The general capabilities must already exist in the UI - but of course they must in the first place for the device to be OCAP compliant.