SIP Directions at Microsoft

1
SIP Directions at Microsoft

• Gurdeep Singh Pall
• General Manager
• Live Communications Group
• Microsoft Corporation

SIP Conference Paris, Jan 21st 2004
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
Unified Communications The End State
End User Value

• Message Management
• Unified communications history
• Improved Productivity
• Info Agent, PCPhone, One identity
• Multi Device Access
• PC, Phone, Cell, PDA

• Integrated iWorker experiences
• Productivity, CRM, Enterprise, work flow
  application integration

Data
PeopleGroups
Info Agent
Voice
Presence
Store, Identity, Media Servers, Relays
Email
Video
IT Manager Value
Developer Value
Presence
IM

• Integration of infrastructure
• Provisioning, Credentials, Auditing, Policies,
  Billing, Routing, Operations
• Lower TCO

• Consolidated extensible Platform
• Multimodal capable
• Simple, Orthogonal architecture
• Lower development costs

Speech/Text
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 Microsofts
  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
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
6
Products and Standards Timeline
PIDF - ltdraft-ietf-impp-cpim-pidf-0x.txtgt
7
SIP Ecosystem and Microsoft
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-sip
  ping-cc-conferencing-02.txt
• XCON for centralized conferencing
• http//www.ietf.org/html.charters/xcon-charter.htm
  l
• 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
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
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

11
BYE sipsipconf_at_upperside.fr SIP/2.0From
sipgurdeep_at_microsoft.comTo sipsipconf_at_uppersid
e.frCall-ID 1_at_microsoft.comCSeq 2 BYE
-) Thank You!