sip directions at microsoft gurdeep singh pall general manager live communications group microsoft...
TRANSCRIPT
SIP Directions at Microsoft
Gurdeep Singh PallGeneral ManagerLive Communications Group Microsoft Corporation
SIP ConferenceParis, Jan 21st
2004
2 2
Our Vision
• Bring “voice”, “screen”, “computation” together to improve:
– How calls are initiated and received– How visual information and data are shared during the call– How calls are intelligently routed based on user context and
preferences– How communications are archived, indexed, and browsed on-
demand– …– With seamless interoperation between communication
channels– With seamless interoperation with productivity tools
• The goal and challenge are to make such capability pervasive
• We believe that this convergence will drive productivity
3 3
Data
Em
ail
IMVi
deo
Voice
Store, Identity,Media Servers,
Relays
Info
Age
nt
Speech/Text
End User Value
IT ManagerValue
Developer Value
•Message Management•Unified communications history
•Improved Productivity•Info Agent, PC&Phone, One identity
•Multi Device Access•PC, Phone, Cell, PDA
•Integration of infrastructure
•Provisioning, Credentials, Auditing, Policies, Billing, Routing, Operations
•Lower TCO
•Consolidated extensible Platform
• Multimodal capable•Simple, Orthogonal architecture•Lower development costs
Unified Communications The End State
People&Groups
•Integrated iWorker experiences•Productivity, CRM, Enterprise, work flow application integration
Presence
Presence
4 4
Why SIP?• Unified Communications vision mandates a lingua franca
that is flexible and broadly understood; ecosystem is key
• The first communications protocol that is designed and built around Internet principles; implies unification of at the core around namespace, security
• Single protocol, useful in variety of topologies, applications, scenarios
• The philosophy of SIP resonates with Microsoft’s vision of Unified Communications; distributed model, smart endpoints key
• At this point SIP is a proven technology: both with successes in the industry and our own experiences building products with it
5 5
SIP at Microsoft• SIP ships in Windows XP since 2001
• 130M+ served
• SIP is the cornerstone of Enterprise Communications products• Live Communications Server 2003• “Vienna” and “Istanbul” 2004• Federation and connectivity with MSN Messenger Service
• SIP is becoming the cornerstone of MSN Messenger Service • Today used for pc-phone and video calling• Goal is to move 100M users to SIP for all services (IM, voice,
video) in 2006 timeframe
• SIP is planned to be included in “Longhorn” the next major update to Windows
SIP has gone beyond “boutique” status to become a core, mission critical component used by variety of applications & services across Microsoft
SIP has gone beyond “boutique” status to become a core, mission critical component used by variety of applications & services across Microsoft
6 6
Products and Standards Timeline
*PIDF - <draft-ietf-impp-cpim-pidf-0x.txt> *PIDF - <draft-ietf-impp-cpim-pidf-0x.txt>
1/1/1999 1/1/2007
1/1/2000 1/1/2001 1/1/2002 1/1/2003 1/1/2004 1/1/2005 1/1/2006
2004Vienna and Istanbul
RFC 3261PIDF-08
Sep-02Reuters Edition
RFC 2543PIDF-00
Today
May-03PIDF-08
(Presence)
Aug-01XP Messenger
with SIPRFC 2543
Aug-03LCS 1.0
RFC 2543PIDF-00
Jun-00PIDF-00
(Presence)
Jul-02RFC 3261(new SIP)
May-99RFC 2543(old SIP)
2005Longhorn
7 7
SIP Ecosystem and Microsoft
Bridges ToOther Systems
LoB Applications
Enable Other Systems
PBXs
VoiP Gateways
SMS/Mobile Gateways
Gateways toConsumer IM
End-userCients
Enrich Communications
IT Managment
Mobile DeviceClients
Specialized PC Clients
CommunicationsAppliances
Web Clients
MultipartyAudio/Video
Media Replay
ChatBOT ApplicationServer
Virus Checking
Content Logging
Clustering/Load Ballancing
Complimentary Services
ASP and Hosting
SystemIntegrators
TelecomServices Legend:
Future
Present
PrimaryCategory
8 8
Standards: Focus areas for Microsoft
• Remote Control• Scenario: Integration with IP and TDM PBXs• We are considering the following approaches:
• ECMA-323 XML messages transported over SIP (session and events)• Using REFER with additional semantics and expanding SIP Event
Packages
• Conferencing• Basic conferencing with SIP
• http://www.ietf.org/internet-drafts/draft-ietf-sipping-cc-conferencing-02.txt
• XCON for centralized conferencing• http://www.ietf.org/html.charters/xcon-charter.html
• Security• Hop-by-hop auth and privacy using TLS is the de facto standard• End-to-end security becomes more important with federated
scenarios• S/MIME is an option but PKI has deployment challenges
9 9
Standards: where can we improve
• Presence, many protocols, a world divided• Numerous standardization bodies and consortiums, some
with multiple protocols!• Lack of consistency is going to slow down pervasive
connectivity• Important that SIP becomes the universal connector for
federation between networks
• SIMPLE WG Issues• Slow pace hurting SIMPLE camp• We would like to see SIMPLE address different interfaces
• wireless client-to-server, enterprise client-to-server, common federated server-to-server
• Architectural direction – peer to peer yesterday, client/server driven by wireless scenarios today, tomorrow?
• Instant Messaging directions• MESSAGE Page Mode? Session Mode?• MS(R)P (Message Session Relay Protocol)?
10 10
In Conclusion
• SIP is a Big Bet for Microsoft• A healthy SIP Ecosystem is critical
for the industry and for Microsoft• Many innovations depend upon
the SIP foundations• Industry must rally together to
remove obstacles and improve pace of innovation
BYE sip:[email protected] SIP/2.0From: sip:[email protected]: sip:[email protected]: [email protected]: 2 BYE
:-) Thank You!:-) Thank You!:-) Thank You!:-) Thank You!