1 Internet Email Internet Commercialization SMTP is Internet Email - PDF document

Background of Chapter Software Infrastructure of the Commercializing Internet � Not finished… � Mostly journalistic � Recounting of basic events from secondary sources � Focus on interplay between technology and business models Thomas Haigh � Search engines/portals to be separated The Haigh Group � Software infrastructure chapter University of Wisconsin--Milwaukee � Search and portals chapter Munich, July 24 2006 Construction of Internet Reconstruction of Technology Technologies � What happens when an already “shaped” � Closed, homogenous, small academic technology gets population � New uses � Results: Rely on social mechanisms for � New “relevant social groups” security, elimination of troublemakers � New cultural meanings � Models � Non-commercial � VHS vs Beta? – � No mechanisms to bill for use of resources � which is the net? � Support for many machine types � Ecological? � Extinction of the megafauna � Compatibility through standards, not code � Native Americans and Smallpox Construction of Internet Layering of Protocols Technologies II FTP Client Mail client Web Many browser others…. � Practical, working network FTP SMTP HTTP Video, chat, � Rather have it next week than perfect news, P2P, (File (Mail (Web) � Decentralized and international instant transfer) transfer) � Easy to connect new machines, sub-domains messaging � Many different communication mechanisms Socket API � TCP/IP works over many media TCP/IP � Created for experimentation and research (also DNS shared by applications) � Separation of application protocols from network Ethernet SLIP/ Satellite Fiber Optic, mechanisms PPP Etc. 1

Internet Email Internet Commercialization � SMTP is Internet Email protocol � Rapid and unexpected � “Pushes” messages to destination � Classic example of internet approach � Though idea of “information superhighway” � Builds on TCP/IP and DNS and universal networking was not � Initial version very simple, so easy to implement from RFC � Tech support for “hacker” culture? � Driven by virtues � No frills � Web and email as killer apps � Plain text only � No verification of sender identity � High quality, free(ish) multiplatform software � No way to charge sender � Real, useful, pragmatic � Very simple addressing mechanism � Reading, composition, sorting of email left to other tools � Adopted by existing online services � Later standards build on this, eg MIME, add features � AOL, Compuserver, etc. Simple Charms Power of Technological Momentum � Biggest opportunities are in fixing design flaws � Frame is email as application � Perfect environment for spam � Continuities and differences of Internet with earlier � Internet has no natural defenses against spammers services � Plenty of proposed standards available to make email � In early commercial period, Internet email � Secure and authenticated � Give proof of receipt � Is a lingua-franca between closed systems � Support email directories, etc � Is cheap and easy to implement � But require simultaneous shift of client, server, user � Does the job behavior. � Has easy to remember addresses � Will probably never happen… � Especially as Microsoft has a proprietary system � Unlike “official” X.400 standards Commercial Internet Email Web: Business History � Traditional packaged application model � Covers the basics struggles � Berners-Lee and CERN � People expect downloads � Gopher, WAIS, etc � Free software is available and expected � Mosaic � Microsoft kills the market with bundling � Netscape � New models emerge � Browser wars � Java � Webmail – Hotmail as big success � Follows Internet tradition of integrating existing � Firefox technologies and code 2

Focus and Arguments I Focus and Arguments II � Coevolution of browser and server � Initial appeal of web as integrator of existing � Importance of Apache to keep things open content � Importance of AOL and ISPs � Obvious development of existing ideas � As distributors, packages of software � New elements: HTML, HTTP, URL � Work needed to reconstruct browser as � Simplicity of web commerce platform � Fundamental problems ignored � SSL and credit card protection � Follows spirit of internet � Creation of logins and sessions – CLUNKY � General confusion of web and Internet � Creation of web development platforms � Unlike email, web needs direct TCP/IP connection � Packaging of internet storefronts, etc. Influence on Business Models Help Me Frame This � No support for payment for content � Does the argument seem reasonable? � Micropayment hyped but flops � What did I miss out? � Web publishing model shifts fundamentally from AOL � Can more of the user experience be era squeezed in? � Microsoft push to integrate browser creates insecurities � Layering of protocols allows many new apps � VOIP, P2P, streaming video, etc. 3