1. Evolving Messaging— Instantly or Not Dave Crocker Brandenburg Consulting www.brandenburg.com

2. 2 Evolving Messaging Topics Email IM & Presence IETF IMPP Working Group Paradigm Competition IETF Process Issues Prognostication

3. 3 Evolving Messaging The marketing slide Dave Crocker 1970’s/Research 1970’s/ResearchArpanet/Internet, mostly email 1980’s/Products 1980’s/ProductsEmail & Internet stack at Ungermann- Bass, Digital Equipment, Silicon Graphics 1990’s/Consulting 1990’s/ConsultingDevelop venture funding, product design Brandenburg Concerti grosso, a genre marked by confrontation among a collection of soloists who nevertheless work collaboratively. In the Internet this is called co–optetition Planning & design Products & services

4. 4 Evolving Messaging Setting the context © 1975, Datamation This? Oh, this is the display for my electronic junk mail.

5. 5 Evolving Messaging Internet mail today Highly successful Highly reliable, for many/some uses A base for additional services Lacking essential capabilities for those services Eg, very poor for long-term dialogue and formal exchanges Does it need enhancement or replacement? Limits of extensibility Real benefits of replacement?

6. 6 Evolving Messaging Protocols Data object and transfer RFC822 MIME SMTP (SUBMIT) (Security) PGP S/MIME User pickup POP delivery IMAP access Mailing lists Addressing Subscribe, unsubscribe Usage controls

7. 7 Evolving Messaging Scaling email... Current email is complicated Future email is demanding Scaling is: Increasing the size Overcoming a barrier Size is: Number of messages Size of individual messages and Number of types of messages Barriers Stringent business performance and functions

8. 8 Evolving Messaging Unified Messaging "Message" Bag of bits Bag of addresses Voicemail Server-to-server experience Facsimile Gateway email and telephone fax “Business quality” message delivery Access issues Voice Narrow dial-up Unprotected kiosk “Home” Differential handling of received mail Access procedures, reliability, efficiency

9. 9 Evolving Messaging Electronic mail model Recipient User Agent Originator User Agent SMTP Relaying Mail Transfer Agent Sending Mail Transfer Agent SMTP Submit POP IMAP RFC 822 822MIME SMTP Receiving Mail Transfer Agent Message Store

10. 10 Evolving Messaging Emerging requirements User “scenarios” Fax Instant messaging Legal documents Commercial transactions Permission-based volume mail Recipient tailoring Timeliness Reliability Confirmation Retry Efficiency Binary encoding Application-level routing

11. 11 Evolving Messaging Service requirements IMFaxEmail Content type TextBitsMany Content size Short Short- Medium Short-Long Addressees 11-Some1-Many Confirmation None Final Delivery Failure or Mailbox Delivery Reliability LowHigh Medium- High

12. 12 Evolving Messaging IM&P Architecture SourceTarget Publish domain1 IM Relay domain2 Pres Srv domain1 Subscribe Target Source domain2 IM Relay

13. 13 Evolving Messaging IMPP Working Group Working group URLs <www.ietf.org/html.charters/ impp-charter.html> Also: Goal “Develop an architecture for simple instant mesaging and presence awareness and notification” Dates Apr 98: Apr 98:Started discussions Mar 99: Mar 99:WG chartered Feb 00: Feb 00:RFC 2778/9 – Model/Requirements------------------------------------------- Mar 00: Mar 00:Design teams Jul 00: Jul 00:3 proposals Jul 00: Jul 00:Common Semantics ???: ???:WGs chartered

14. 14 Evolving Messaging CPIM Common Presence and Instant Messaging An experiment… Common semantics, for interoperability among independent protocols… Moving towards common data syntax Addressing: [im:,pres:]user@domain with SRV Security:TLS, OpenPGP—S/MIME Presence:XML Content:MIME, RFC822-in-XML Transport:

15. 15 Evolving Messaging Paradigm Competition PRIM PResence and Instant Messaging SIMPLE SIP for Instant Messaging and Presence Leveraging IMXP/APEX Instant Messaging eXchange and Presence APplication EXchange AOL Aloof IM Unified AT&T, Excite@home, MSN, Odigo, Phone.com, Prodigy, and Yahoo! Aug. 31, 2000 – “IMUnified… today announced the completion of technical specifications…

16. 16 Evolving Messaging PRIM Network Projects, MIT, MITRE, Fujitsu Draft-mazzoldi-print-impp-00.txt Addressing: [im:,pres:]user@domain with SRV Security: TLS, OpenPGP—S/MIME, ACL Presence: XML Content: MIME Transport: Long-lived TCP, shared

17. 17 Evolving Messaging SIMPLE Dynamicsoft, Columbia, Microsoft, Cisco Draft-rosenberg-impp-*-00.txt Real-time telephone control Re-use facilities Addressing: sip:user@domain Security: TLS, OpenPGP—S/MIME, ACL Presence: RFC822-ish Content: MIME, RFC822-ish Transport: SIP

18. 18 Evolving Messaging APEX (IMXP) Invisible Worlds, Brandenburg, Baltimore Draft-mrose-apex-*-00.txt Re-use Internet Mail Architecture Lightweight transport Addressing: [im:,pres:]user@domain with SRV Security: TLS, OpenPGP—S/MIME, Presence:XML Message: MIME, RFC822-in-XML Transport: Beep over…

19. 19 Evolving Messaging APEX architecture +-------+ +--------+ +-------+ +-----+ | APEX | | APEX | | APEX | | | | access| |presence| | report| | … | |service| |service | |service| | | +-------+ +--------+ +-------+ +-----+ | | | | APEX Core +----------------------------+ +----------------------------+ | +------+ | | +------+ | | | appl | | | | appl | | | +......+ +------+ | | +------+ +......+ | | |end- | |relay | | | |relay | |end- | | | | point| | | | | | | | point| | | +------+ +------+ | | +------+ +------+ | | | APEX | | APEX | | | | APEX | | APEX | | | +------+ +------+ | | +------+ +------+ | | | BEEP | | BEEP | | | | BEEP | | BEEP | | | +------+ +------+ | | +------+ +------+ | | || || || | | || || || | | ============= ================ ============= | +----------------------------+ +----------------------------+ administrative domain #1 administrative domain #2

20. 20 Evolving Messaging IETF Process Issues IMPP “plan” (10/13/00) “Other groups will be chartered for progression of individual information transfer protocols. These will have a requirement to check back and coordinate with the IMPP common document” 3 years and no standard “Managing” paradigm conflicts does not work Let the market decide

21. 21 Evolving Messaging Prognostication AOL uber alles, for the near future Eventually multiple IETF standards SIP has massive market/vendor mindshare SIP might be viable APEX, if SIP stumbles Presence Telephony, conferencing, … A separate service

22. 22 Evolving Messaging Start (continue) shooting… Email vs. IM Email QOS Presence uber alles SIP uber alles Email-NG?