To: axial who wrote (25488 ) 2/20/2008 1:18:05 PM From: Frank A. Coluccio Respond to of 46821 Hi Jim. Every entrant is governed by at least some least-common-denominator cut of standards. This holds especially true for the networking layers, lest an entrant not even be able to port its wares. My main point has been: It's how entrants differentiate themselves outside the borders of those LCD standards, usually at the higher layers, that make them stand out and go on to become the next Amazon, Google or Second Life. Ten years ago (your second reference link), steadfastly adhering to "new standards" (actually, emerging Internet RFCs) was deemed sufficient by many entrants _in _the _networking _ space when the primary goal was to escape the gravitational pull of incumbents legacy standards. Back then, ISPs and common carriers (the incumbents) belonged to separate universes, and the evolving Web application space was simpler and less demanding. We're past those once-nascent times today, although new entrants today still need to continue leveraging those same RFCs (and newer ones as they evolve) at the lower layers of the stack while creating newer and proprietary applications, services and products at the higher layers, if they wish to thrive. Of course, in the process everyone else suffers a little bit (Basic Hair-Pulling 101), since they cannot access those applications unless they agree to the terms of subscription or sale. We face this constantly in the enterprise, where, for example, vendors' Ethernet switches and cabling systems, say, adhere to all of the IEEE and TIA/EIA standards at the transport layers, but differentiate themselves when it comes to security, operating systems, administrative tools, and so on, making it extremely awkward, if possible at all, to maintain a multi-vendor environment in an economical manner, despite all vendors adhering to Layer 1 and 2 "network" standards. Of course, the latter also carries along with it the need to protect their IPRs, "because" they are not, in and of themselves, open standards. Skype leveraged peer-to-peer RFCs, for example, but built its capabilities on top of those standards by using proprietary code. Later, FAC ------