Imtc cto-summary day1-draft


Published on

  • Be the first to comment

  • Be the first to like this

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

Imtc cto-summary day1-draft

  1. 1. What Did We Learn Today? - Recap -
  2. 2. Anatoli – IMTC President Intro <ul><li>Welcome - Intro & Objectives of IMTC – History & Accomplishments </li></ul><ul><li>‘ Video is Everywhere’ – What can IMTC do to make it interop and communicate seamlessly </li></ul><ul><li>Challenges </li></ul><ul><ul><li>Clusters, Consumerization, etc. </li></ul></ul><ul><li>Intro by MC Andrew Davies </li></ul>
  3. 3. Keynote – Eric Newton – AT&T Service Provider Perspective <ul><li>‘ The World we Want vs. What we have today!’ </li></ul><ul><ul><li>Headache=Latency, bandwidth, S.P.O.Failure, etc. </li></ul></ul><ul><li>1 st Q&A = What is Standards + (Plus)’ </li></ul><ul><ul><li>Standards, plus Value-Add features & services </li></ul></ul><ul><li>Where we need Standardization </li></ul><ul><ul><li>Common Signal Protocol, Multi-Codec support </li></ul></ul><ul><ul><li>Data sharing, Encryption, Presence </li></ul></ul><ul><li>What Can I do? </li></ul><ul><ul><li>To all…..push, get engaged, support & participate in Standards </li></ul></ul><ul><li>Q – Is SIP really simple vs. 323? </li></ul><ul><li>Yes, but, not ‘everything’ built into SIP standard, so there is need for “Best Practices” engagement, like the IMTC SIP AG which helps define best practices……to make it ‘interoperable’ </li></ul><ul><li>Q – How do you ensure the standard isn’t a minimum subset of requirements </li></ul><ul><li>Agreed, key challenge is common standard with value add on top </li></ul><ul><li>Shouldn’t we strive for ‘good enough’? Users are ‘ready to buy’ but only if it actually works. </li></ul><ul><li>Q If SIP = feature parity with 323, then What? </li></ul>
  4. 4. Ronald Gruia – Frost & Sullivan <ul><li>Challenge – mixed view of enterprise & Consumer </li></ul><ul><li>Challenge – Ensure that user/Value education & habit breaking are handled, to grow adoption (ex. co-pilot UMsg) </li></ul><ul><li>IP & its impact to messaging – user changing rapidly </li></ul><ul><li>Video Telephony – a word of caution…cuz its visible now! </li></ul><ul><li>IMS Making a Comeback </li></ul><ul><li>Can RCS Solve the Client Conundrum? </li></ul><ul><li>Growing Threat from over the top players </li></ul>
  5. 5. Phil Edholm - Avaya <ul><li>Interoperability…what our customers want! </li></ul><ul><li>Think ‘People First’, not #, address, IM ID, etc. </li></ul><ul><li>SVC is critical to deliver comprehensive video </li></ul><ul><li>Conferencing as a paradigm, know your ‘real’ user </li></ul><ul><li>Concept of a Personal Agent </li></ul><ul><ul><li>Human intervention, Contextual, Topical </li></ul></ul><ul><ul><li>Interactive vs. Rule-based, Adpative Intelligence </li></ul></ul><ul><li>Enterprise Federation – Pick a standard, drive adoption, grow the market pervasively </li></ul><ul><li>How do you compete when the value proposition is changing </li></ul>
  6. 6. Mark Coleman - Microsoft <ul><li>Normal experience is 15+ minutes when multi-systems are ‘attempted’ for integration, Not acceptable </li></ul><ul><li>Cross Platform Support for Unified Communications now mandatory </li></ul><ul><li>Key Features of a successful Collaboration Experience </li></ul><ul><ul><li>Mark had list here </li></ul></ul>
  7. 7. Panel Talk – March 8 AM Ron Gruia - Moderator <ul><li>Federation – Personal vs. Business Profile </li></ul><ul><ul><li>Phil – Know the device, know the profile for ‘availability’ </li></ul></ul><ul><ul><li>AT&T – Yes, persona is a good concept, aim to move there…but still a ways off </li></ul></ul><ul><ul><li>MS, understand, but usually don’t have clients ask for multiple profile or persona approach </li></ul></ul><ul><ul><li>Polycom – many EU companies have addressed identity and if ‘industry’ doesn’t address, then public will find a solution. </li></ul></ul><ul><li>Opportunity, Threat of SVC </li></ul><ul><ul><li>Polycom – announcement made, we see opportunity </li></ul></ul><ul><ul><li>ATT, yes, value in SVC, some devices better suited to SVC, and conversely others work with AVC, perhaps better </li></ul></ul><ul><ul><li>Avaya, SVC good because next 3-5 years may have wireless bandwidth issues that SVC can help solve. </li></ul></ul>
  8. 8. Panel notes #2 <ul><li>Legacy – How challenging is that? </li></ul><ul><ul><li>Polycom – yes, challenging, with older legacy when old system have been learned and ‘work’ </li></ul></ul><ul><ul><li>MS-problem with legacy because in the middle of user migration, those with pbx with usable life, and concurrent movement to Unified Messaging </li></ul></ul><ul><ul><li>Avaya….yes, but isn’t it better to use legacy and merge/blend new systems in…rather than cutover. </li></ul></ul><ul><ul><li>Merck – reality is integration & product life cycle and amortization 10 year vs. 5 year factors. </li></ul></ul><ul><li>Will the new codec help, or not </li></ul><ul><ul><li>Avaya…yes it will fragment the industry </li></ul></ul><ul><ul><li>ATT….yes, it just loads cost onto the top, will industry/customers accept that </li></ul></ul>
  9. 9. Casey King - LifeSize <ul><li>Linear Growth </li></ul><ul><ul><li>History slide </li></ul></ul><ul><li>Non-Linear Change </li></ul><ul><ul><li>Are you thinking about, is there a plan, are you ready for a ‘burning platform’ </li></ul></ul><ul><ul><li>Netflix vs. blockbuster </li></ul></ul>
  10. 10. Mirril McMullen - Pfizer <ul><li>Barriers </li></ul><ul><ul><li>Poor user experience, Tough to schedule & Operate </li></ul></ul><ul><ul><li>TP rooms and Video Conf. not interoperable </li></ul></ul><ul><li>Therefore, evaluate, create roadmap </li></ul><ul><ul><li>Upgrade rooms, ‘Self-service Registration/Schedules’ </li></ul></ul><ul><li>Driver for Desktop? </li></ul><ul><ul><li>Low cost, immediate access, remote worker apps </li></ul></ul><ul><li>GET the FACTS, Video Usage overlaid to Travel </li></ul>
  11. 11. Sean Lessman - Cisco <ul><li>Telepresencde (multi-codec) interoperablity </li></ul><ul><li>TIP vs. CLUE </li></ul><ul><li>CLUE is following IETF format requirements </li></ul><ul><li>Business to Business Issues </li></ul><ul><ul><li>Playing well with others </li></ul></ul><ul><ul><li>Firewalls, Directory Services, Dial Plan problem </li></ul></ul><ul><li>Business to Consumer </li></ul><ul><ul><li>Financials, Healthcare, Skype, Facetime, </li></ul></ul><ul><li>B2B & B2C must connect in Scalable way </li></ul><ul><li>Mobility Challenges </li></ul><ul><ul><li>Platforms, Int’l plans, Packet Loss, Networks/Bandwidth </li></ul></ul><ul><ul><li>Mobility requires adaptiveness to non-guaranteed networks </li></ul></ul>
  12. 12. Customer-Vendor Panel March 8 PM