To: Frank A. Coluccio who wrote (19045 ) 1/19/2000 11:26:00 PM From: E. Davies Read Replies (1) | Respond to of 29970
Or, do you want to KISS it nice and quick, delivering a high bandwidth platform with stupid network attributes Your preference here is clear, however I'd be curious to hear you take the other side for a moment. Does it really work to simply hang the users on the internet? No network management? No caching? What things are lost with "nice & quick"? I'm truly uncertain.You've just described the Internet, which has upwards of 6,000 networks connecting together using open internetworking standards. That wasn't the question I posed. What I'm talking about is duplicate networks where each ISP is required to run its own link between each headend and "the internet" (in whatever form). Instead of one heavy duty link for all the users of that headend there would be 10 smaller ones each attempting to size itself for the capacity based on the number of subscribers they have at the moment. Seems illogical to me. Increasingly, subscribers want speed and the option to go wherever they want go without binding terms, whether that's AOL, Home, or elsewhere. @home already provides that. What can other ISP's (excluding AOL) provide that would make consumers choose them over @home? Where will the battleground be when MSPG tries to steal away @home customers? I personally don't see any way that they can (except for SOHO type apps unless @work gets it's act together). Finally in regards to the question "How hard is it to duplicate @home?" I ask about the management of the network down to the user. My understanding (though I'm still fuzzy) is that though the MSO provides the link, @home controls and manages the network all the way down to the users modem. In essense you might say that @home is leasing the wires similar to how they lease backbone capacity from AT&T. If true- how can you have multiple managers of a single network? I'm honestly not even sure what "network managment" is- but I know that your average company spends a great deal of money hiring significant numbers of employees to manage internal networks. It ain't easy even if only one group is in charge. Bottom line: I've never answered the eternal question "What is @home anyway?". But I'm still trying... Eric