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
  • Internet2 is a unique non-profit corporation of more than 200 universities, 60 corporations, and 40 affiliates working to develop a faster, more reliable, more private and secure Internet that enables applications such as really useful videoconferencing, medical training and care, secure access to music and movies, and high schoolers using electron microscopes to investigate unseeable worlds.
  • Stas: Why aren’t application “key” too? Without code, nothing will happen. Aren’t developers an important constituency?.
  • Ben – obviously feel free to add a phone number, or not as you like. Or, if you prefer, it's okay with me just to lis t email addresses for us both. I like the multi-mode plug for integration of email:, im:, sip:, but it's not required.
  • The emphasis in the first paragraph is on global-scoped communcations and private & open-source collaborations. The listing of demonstrations, tutorials andinitiatives is just for example. I don't think we mean to limit our methods to just these three. The second paragraph is a statement of our core value that a common, bearer signaling protocol (analogous to IP at a lower level) is important, especially in the context of integrated communications. It doesn't, however, mean that we wouldn't ever move outside SIP i.e., location.
  • PIC is a relatively new working group, still in its first year – July 1st anniversary. FMM'03 was a learning experience. TIP was initial success. SMM'04 we hope to come closer to getting it right. Grateful for excellent private sector and open-source collaboration. Undecided future. The social context (FCC, law enforcement, etc.) of PIC has been clear for a while. Dr. Clark's presentation at TIP and paper make it clear why an Internet2 working group should include a focus on issues beyond the strictly technical. It may be that discussion for a while will be necessary before this study group decides on a specific direction.
  • Growing training programs Testing and evaluate MCUs Remote Collaboration Extensive member Interviews completed March ’04 Data Collaboration Survey with ViDe completed April ‘04 Testbeds: WebOffice and IMFirst data c
  • If not covered in previous slides - what is SIP SIP: Signalling protocol for creating, modifying, and terminating real-time internet media sessions. SIP (and its extensions) support traditional telephony features as well as instant messaging and presence. SIP.edu provides a foundation for SIP experimentation by making schools traditional PBX, Centrex, or VoIP phones reachable using SIP. Dennis is the project leader. Note that a user’s SIP address is the same as Email address.
  • SIP.edu is one of the projects undertaken by the VoIP WG. The goals of the project are increase the number of SIP reachable users. This will encourage further experimentation with SIP and related technologies. SIP.edu leverages already well-know email addresses by mapping them to existing phones using a school’s LDAP directory service. SIP.edu is a simple, low-cost way for schools to get started with SIP. The SIP.edu cookbook is available on the web as an implementation guide. Multiple solutions are available to meet the needs of specific schools. SIP.edu is working with vendors to add SIP.edu functionality to their products and to make package pricing available to Internet2 member institutions.
  • Initial proof of concept installations were done at MIT using a Pingtel SIP proxy and at Yale using an iptel.org proxy. Both schools used Cisco gateways to connect calls to existing PBX phones. LDAP integration was demonstrated by Columbia University - allowing for real-time lookup of email address/phone number mapping using the campus directory. Approximately 100,000 users are now SIP-reachable via their email addresses. Additional schools are in the process of implementing SIP.edu.
  • Stas: A more thorough breakdown of strengths and weaknesses is in order. For example, one weakness of the Internet is its vulnerability to internal attacks A 2x2 matrix might be good here {PSTN, Internet} x {Strengths, Weaknesses} Guy” Don’t say: “The Internet designed to withstand nuclear war. No network could withstand a nuclear war.” Guy: Did you consider mentioning 9-11-01 as an example here? I did, but deliberately didn’t mention it.
  • Slide 1) Nadim El-Khoury from the University of North Carolina at Chapel Hill is the Chair and participation in the working group is very welcome. Please acknolowdge Ken as being the area director.
  • Slide 2) Main goal of VidMid-VC is to integrate middleware into video conferencing with the emphasis on authentication, autherization and resource discovery. Next step is how to bring a federated approach to this technology.
  • Slide 3) commObject which is an architecture that was developped by VidMid-VC and Vide (Video Development Initiative) became an ITU-T standard known as H.350. H.350 defines a directory services architecture for mulitmedia conferencing for H.323, SIP, H.320 and generic protocols. Directory of Directories for Video Conferencing has been put in place by SURFnet in the Netherlands and an initial demo was done last in March 2004. More details will be coming soon on how to register your H.350 Directories and Enterprise directories to be search. The First ever H.350 Workshop was conducted in Indianapolis in March of 2004. This event was sponsored by Internet2, ITU, Radvision, Tandberg, VCON had more than 60 attendees. It concentrated on how to adopt H.350 and what H.350 can do for you. We are listing the Demos that we have done, to emphasize the fact that Vendors are embracing H.350 and to point out the fact that you can use H.350 to self configure endpoints, and introduce authentication which does not exist as of today.
  • Credits: > *Tarun Abhichandani * > (tarun.abhichandani@cgu.edu)* * > *Samir Chatterjee * > *Bengisu Tulu * > *Haiqing Li * > Network Convergence Lab > Claremont Graduate University > Claremont, CA – 91711. > 909-607-4405
  • Credits:
  • 20040421-rtc-forum.ppt

    1. 1. Internet2 Real Time Communication Forum <ul><ul><li>Internet2 Member Meeting, Arlington, VA </li></ul></ul>April 21 st , 2004
    2. 2. Goals for Today <ul><li>Survey Internet2 Landscape </li></ul><ul><ul><li>Who is doing what and why? </li></ul></ul><ul><ul><li>What are the unifying themes, directions, principals? </li></ul></ul><ul><ul><li>How should campuses prepare? </li></ul></ul><ul><li>Understand Broader Landscape </li></ul><ul><ul><li>Four distinguished, invited speakers </li></ul></ul><ul><ul><li>What are the broader technology trends? </li></ul></ul><ul><ul><li>What are the big challenges, opportunities, tradeoffs? </li></ul></ul><ul><li>Panel Discussion </li></ul><ul><ul><li>How can Internet2 best work to advance RTC? </li></ul></ul>
    3. 3. Today's Agenda <ul><li>1:15 – 1:35 Overview of Current Initiatives </li></ul><ul><ul><li>“ Internet2 RTC: Towards a Grand Unified Theory” </li></ul></ul><ul><li>1:35 – 2:15 Invited Speakers </li></ul><ul><ul><li>Andrew Odlyzko, University of Minnesota </li></ul></ul><ul><ul><li>Rodger Will, Ford Motor Corp </li></ul></ul><ul><li>2:15 – 2:45 Coffee </li></ul><ul><li>2:45 – 3:25 Invited Speakers (cont.) </li></ul><ul><ul><li>Peter Saint-Andre, Jabber Software Foundation </li></ul></ul><ul><ul><li>Henning Schulzrinne, Columbia University </li></ul></ul><ul><li>3:25 – 3:45 Panel Discussion </li></ul>
    4. 4. Internet2 RTC: Towards a Grand Unified Theory
    5. 5. Outline <ul><li>Unifying Themes </li></ul><ul><li>The campus/enterprise role </li></ul><ul><li>Survey of Current Activities </li></ul><ul><ul><li>Commons </li></ul></ul><ul><ul><li>I2IM </li></ul></ul><ul><ul><li>PIC </li></ul></ul><ul><ul><li>Research Channel? </li></ul></ul><ul><ul><li>SIP.edu </li></ul></ul><ul><ul><li>VidMid-VC </li></ul></ul><ul><ul><li>Voice DR </li></ul></ul>
    6. 6. The GUT of RTC: Middleware Network Connectivity (high-performance, end-to-end IP transit) Application Connectivity (call routing MW and signaling standards) User User Auth/Z Auth/N Identity Presence Messaging Auth/Z Auth/N Identity Presence Messaging Your campus is here! ASPs Gateways Bridges Trust
    7. 7. Inside the Belly: Alphabet Soup Internet2 Services Campus Services Application Abilene LDAP DNS SIP H.323 Directories Call Control IP SIP/SIMPLE XMPP Presence SAML Shib PKI Auth N/Z DHCP CDP SNMP Location Auto-Config Campus Services BGP policy GUI, display, ... SIP/SIMPLE, XMPP, H.323 Voice Video IM Presence Application RTP, SDP media inCommon Bridging Services PSTN GW MCUs P2P signaling P2P trust
    8. 8. Unifying Themes 1/2 <ul><li>Leveraging Enterprise Assets </li></ul><ul><ul><li>Identity management </li></ul></ul><ul><ul><li>Enterprise directories </li></ul></ul><ul><li>Linking Identities </li></ul><ul><ul><li>H.350 </li></ul></ul><ul><li>Growing Connectivity </li></ul><ul><ul><li>SIP.edu </li></ul></ul><ul><li>Securing RTC </li></ul><ul><ul><li>Authentication </li></ul></ul><ul><ul><li>Authorization </li></ul></ul><ul><ul><li>Network infrastructure </li></ul></ul><ul><ul><li>Physical infrastructure </li></ul></ul><ul><ul><li>VideNet GDS </li></ul></ul><ul><ul><li>Disaster recovery </li></ul></ul><ul><ul><li>Spam prevention </li></ul></ul><ul><ul><li>Encryption </li></ul></ul><ul><ul><li>SIP.edu </li></ul></ul>
    9. 9. Unifying Themes 2/2 <ul><li>Building on Trust </li></ul><ul><ul><li>iCommon </li></ul></ul><ul><ul><li>SIP.edu </li></ul></ul><ul><li>Supporting Open Standards </li></ul>
    10. 10. Real Time Communications
    11. 11. Real Time Communications
    12. 12. Real Time Communications
    13. 13. Current RTC Activities <ul><li>Internet2 Commons </li></ul><ul><li>Integrated Infrastructure for Instant Messaging </li></ul><ul><li>Presence and Integrated Communications </li></ul><ul><li>SIP.edu (VoIP WG) </li></ul><ul><li>Video Middleware-Videoconferencing </li></ul><ul><li>Voice Disaster Recovery </li></ul>
    14. 14. Presence and Integrated Communications WG (PIC) <ul><li>Web Site </li></ul><ul><ul><li>http://pic.internet2.edu/ </li></ul></ul><ul><li>Chair </li></ul><ul><ul><li>Jeremy George, Yale University { email , im , sip } : [email_address] tel: 203/436.4507 </li></ul></ul><ul><li>Program Manager </li></ul><ul><ul><li>Ben Teitelbaum, Internet2 { email , im, sip } : [email_address] </li></ul></ul>Presence and Integrated Communications email:, im:, sip:jeremy.george@yale.edu tel:203/436.4507 email, im:, sip:ben@internet2.edu tel:<if you like> pic.internet2.edu
    15. 15. PIC Charter <ul><li>Foster the deployment of SIP-based communication that integrate multiple communications elements in the </li></ul><ul><li>Develop technical deployment and use cases for campus presence and integrated communications services </li></ul><ul><li>Inform the emerging policy tussle </li></ul>
    16. 16. <ul><li>Chartered July 1 st , 2003 </li></ul><ul><li>Conducted three rich presence trials </li></ul><ul><ul><li>Prototypes of next-gen campus communications services </li></ul></ul><ul><ul><li>Highly-participatory trials at Internet2 meetings </li></ul></ul><ul><ul><li>New network infrastructure, middleware, and clients </li></ul></ul><ul><ul><li>Location-aware technology </li></ul></ul><ul><li>Launched Social Context Study Group </li></ul><ul><ul><li>Studying policy/privacy tussle for presence </li></ul></ul><ul><ul><li>Now in the formative stage </li></ul></ul>PIC Accomplishments
    17. 17. Internet2 Commons <ul><li>Web Site </li></ul><ul><ul><li>http://commons.internet2.edu/ </li></ul></ul><ul><li>Contacts </li></ul><ul><ul><li>Jonathan Tyman, Internet2 Program Manager email: [email_address] </li></ul></ul><ul><ul><li>John Krienke, Internet2 email: [email_address] edu </li></ul></ul><ul><ul><li>Cheryl Munn-Fremon, Internet2 email: [email_address] </li></ul></ul>
    18. 18. Internet2 Commons Charter <ul><li>Promote and facilitate remote collaboration by means of innovative and integrated, standards-based Internet technologies </li></ul><ul><li>Create collaboration services that are... </li></ul><ul><ul><li>Sustainable </li></ul></ul><ul><ul><li>Scalable </li></ul></ul><ul><ul><li>Affordable </li></ul></ul>
    19. 19. Internet2 Commons Accomplishments <ul><li>Launched H.323 videoconferencing service </li></ul><ul><ul><li>Production, subscription-based service </li></ul></ul><ul><ul><li>Standards-based </li></ul></ul><ul><ul><li>Conference streaming and archiving </li></ul></ul><ul><ul><li>24/7 NOC (OARnet/OSU) </li></ul></ul><ul><ul><li>Scheduled and ad hoc use </li></ul></ul><ul><li>Studying Remote Collaboration and Improving Service Suite </li></ul><ul><ul><li>Extensive member interviews </li></ul></ul><ul><ul><li>Data Collaboration Survey with ViDe </li></ul></ul><ul><ul><li>Testing WebOffice and IMFirst </li></ul></ul>
    20. 20. VoIP Working Group <ul><li>Web Site </li></ul><ul><ul><li>http://voip.internet2.edu/ </li></ul></ul><ul><li>Chairs </li></ul><ul><ul><li>Walt Magnussen, Texas A&M University email: [email_address] </li></ul></ul><ul><ul><li>Mike Enyeart, Indiana University email: enyeart@indiana.edu </li></ul></ul><ul><li>Program Manager </li></ul><ul><ul><li>Ben Teitelbaum, Internet2 { email , im, sip } : [email_address] </li></ul></ul>
    21. 21. VoIP WG Charter <ul><li>Umbrella for a variety projects </li></ul><ul><li>Develop and deploy advanced voice communications. </li></ul><ul><li>Understand the implications of network convergence </li></ul><ul><li>Improve the scalability, survivability, and functional richness of voice communications </li></ul>
    22. 22. VoIP WG Accomplishments <ul><li>Workshops </li></ul><ul><ul><li>VoIP Workshop, October 2003, Indianapolis, IN </li></ul></ul><ul><ul><li>VoIP Workshop, April 2002, College Station, TX </li></ul></ul><ul><li>Projects </li></ul><ul><ul><li>H.323 VoIP Testbed </li></ul></ul><ul><ul><ul><li>20+ sites peered through H.323 gatekeepers </li></ul></ul></ul><ul><ul><ul><li>Concluded (but continuing peering relationships) </li></ul></ul></ul><ul><ul><ul><li>Exploring scalable E.164 routing ( e.g. ENUM) </li></ul></ul></ul><ul><ul><li>SIP.edu </li></ul></ul><ul><ul><li>Voice Disaster Recovery </li></ul></ul>
    23. 23. SIP.edu <ul><li>Web Site </li></ul><ul><ul><li>http://voip.internet2.edu/SIP.edu/ </li></ul></ul><ul><li>Project Leader </li></ul><ul><ul><li>Dennis Baron, MIT email: [email_address] sip: [email_address] </li></ul></ul><ul><li>Program Manager </li></ul><ul><ul><li>Ben Teitelbaum, Internet2 email: [email_address] sip: [email_address] </li></ul></ul>
    24. 24. SIP.edu Charter <ul><li>Goals </li></ul><ul><ul><li>Grow number of SIP connectivity and use </li></ul></ul><ul><ul><li>Increase value proposition for end-user SIP adoption </li></ul></ul><ul><ul><li>Promote converged electronic identity </li></ul></ul><ul><ul><li>Low entry-cost means for campuses to... </li></ul></ul><ul><ul><ul><li>Provide a useful initial service </li></ul></ul></ul><ul><ul><ul><li>Start getting their feet wet with SIP </li></ul></ul></ul><ul><li>Means </li></ul><ul><ul><li>SIP.edu Cookbook available on web site </li></ul></ul><ul><ul><li>Partnering with vendors (Cisco) </li></ul></ul><ul><ul><li>Building community of implementers </li></ul></ul>
    25. 25. SIP.edu Architecture INVITE (sip: [email_address] ) DNS SRV query sip.udp.bigu.edu telephoneNumber where mail=”bob” PRI / CAS bigu.edu SIP User Agent Bob's Phone sip. udp.bigu.edu IN SRV ... INVITE (sip:12345@gw.bigu.edu) SIP Proxy DNS SIP-PBX Gateway PBX Campus Directory
    26. 26. SIP.edu Accomplishments <ul><li>Completed proof of concept deployments </li></ul><ul><li>Published SIP.edu whitepaper </li></ul><ul><li>Demonstrated LDAP integration </li></ul><ul><li>Published SIP.edu Cookbook </li></ul><ul><li>Approaching 100,000 reachable users </li></ul>
    27. 27. Voice Disaster Recovery (DR) <ul><li>Web Site </li></ul><ul><ul><li>http://voip.internet2.edu/dr/ </li></ul></ul><ul><li>Project Leader </li></ul><ul><ul><li>Chris Peabody, Georgetown University email: [email_address] </li></ul></ul><ul><li>Program Manager </li></ul><ul><ul><li>Ben Teitelbaum, Internet2 email: [email_address] </li></ul></ul>
    28. 28. Voice DR Charter <ul><li>PSTN and Internet each have strengths and weaknesses </li></ul><ul><li>Combine VoIP and PSTN for better voice survivability than either architecture alone </li></ul><ul><li>Partner with carriers and vendors to provide a disaster recovery service to Internet2 members </li></ul>
    29. 29. Different Networks, Different Strengths / Vulnerabilities <ul><ul><li>Internet allows for gradual degradation of voice quality, rather than call blocking, which is what you want in an emergency </li></ul></ul><ul><li>Open to internal attack </li></ul><ul><li>Mileage may vary (no QoS) </li></ul><ul><li>CO is single point of failure </li></ul><ul><li>Local loop single point of failure </li></ul>Strengths <ul><li>Network routes around failure </li></ul><ul><li>Packet-level call multiplexing </li></ul><ul><li>Adaptive, loss tolerant codecs </li></ul><ul><li>Reliable QoS (once connected) </li></ul><ul><li>Reliable hardware </li></ul><ul><li>Impervious to DoS attack </li></ul>Internet PSTN
    30. 30. Voice DR Accomplishments Virginia GU/MAX Network Gateway Internet2 SIP-PRI Boston Network Gateway SIP-PRI TAMU PSTN Campus LAN LAN Campus
    31. 31. Integrated Infrastructure for Instant Messaging Working Group (I2IM) <ul><li>Web Site </li></ul><ul><ul><li>http://middleware.internet2.edu/i2im/ </li></ul></ul><ul><li>Chair </li></ul><ul><ul><li>Michael Gettes, Duke University Email: gettes@duke.edu </li></ul></ul><ul><li>Area Director </li></ul><ul><ul><li>Ken Klingenstein, Internet2 Email: kjk@internet2.edu </li></ul></ul>
    32. 32. I2IM Charter <ul><li>Research the issues surrounding enterprise integration of IM services with respect to identity, authn and authz. </li></ul><ul><li>Investigate current and future designs of relevant technologies with respect to authz services, and how authz information is transmitted and interpreted, especially between domains; and how to integrate these methods with emerging campus and inter-campus authorization systems.. </li></ul><ul><li>Based on interest and technical feasibility, consider this range of issues for non-proprietary IM technologies. </li></ul><ul><li>Consider and possibly instantiate a national or international federated IM service. It will look at feasibility and applicability of leveraging technical methods like SAML/Shibboleth, and the policy frameworks coming from federations such as InCommon. </li></ul>
    33. 33. I2IM Accomplishments <ul><li>Chartered Fall 2003 </li></ul><ul><li>Developing use cases, scenarios, and requirements: </li></ul><ul><ul><li>Authenticated User </li></ul></ul><ul><ul><li>Anonymous / Pseudonymous User </li></ul></ul><ul><ul><li>Shibboleth-enabled Extensible Messaging and Presence Protocol (XMPP) </li></ul></ul><ul><ul><ul><li>Open, XML-based protocol for near real-time extensible messaging and presence. </li></ul></ul></ul><ul><ul><ul><li>Core protocol of the Jabber Instant Messaging and Presence technology </li></ul></ul></ul><ul><ul><ul><li>Near approval as IETF Standard </li></ul></ul></ul>
    34. 34. Video Middleware- Videoconferencing (VidMid-VC) <ul><li>Web Site </li></ul><ul><ul><li>http://middleware.internet2.edu/video/ </li></ul></ul><ul><li>Chair </li></ul><ul><ul><li>Nadim E. El-Khoury, University of North Carolina at Chapel Hill </li></ul></ul><ul><ul><li>Email: [email_address] </li></ul></ul><ul><li>Area Director </li></ul><ul><ul><li>Ken Klingenstein, Internet2 </li></ul></ul><ul><ul><li>Email: [email_address] </li></ul></ul>
    35. 35. VidMid-VC Charter <ul><li>Further the development of middleware for digital video and related areas. </li></ul><ul><li>Focus on resource discovery, authentication, and authorization for point-to-point and multi-point videoconferencing </li></ul><ul><li>Next on the agenda: Federated approach to Video conferencing </li></ul>
    36. 36. VidMid-VC Accomplishments <ul><li>commObject became an ITU-T standard known as H.350 in August 2003. </li></ul><ul><li>Directory of Directories for Video Conferencing, SURFnet, Netherlands </li></ul><ul><ul><li>Initial Demo, March 2004, Indianapolis, IN </li></ul></ul><ul><li>Workshops </li></ul><ul><ul><li>H.350 Workshop, March 2004, Indianapolis, IN </li></ul></ul><ul><li>Demos </li></ul><ul><ul><li>H.323 endpoint self configuration using H.350 and authentication against LDAP, October 2003, Indianapolis, IN </li></ul></ul><ul><ul><li>ECS gatekeeper using H.350, October 2003, Indianapolis, IN </li></ul></ul><ul><ul><li>SIP User Agent self configuration using H.350 and authentication against LDAP, March 2004, Indianapolis, IN </li></ul></ul>
    37. 37. Panel Discussion
    38. 38. Panelists <ul><li>Moderator </li></ul><ul><ul><li>Steve O.?? Michael G. ?? </li></ul></ul><ul><li>Invited Panelists </li></ul><ul><ul><li>Andrew Odlyzko, University of Minnesota </li></ul></ul><ul><ul><li>Henning Schulzrinne, Columbia University </li></ul></ul><ul><ul><li>Peter Saint-Andre, Jabber Software Foundation </li></ul></ul><ul><ul><li>Rodger Will, Ford Motor Corp </li></ul></ul><ul><li>Internet2 WG Chairs and Project Leaders </li></ul><ul><ul><li>Dennis Baron, MIT </li></ul></ul><ul><ul><li>Nadim Elkhoury, UNC </li></ul></ul><ul><ul><li>Mike Enyeart, Indiana University </li></ul></ul><ul><ul><li>Jeremy George, Yale University </li></ul></ul><ul><ul><li>Michael Gettes, Duke University </li></ul></ul><ul><ul><li>Walt Magnussen, Texas A&M </li></ul></ul><ul><li>Internet2 Staff </li></ul><ul><ul><li>Cheryl Munn-Freemon, Internet2 </li></ul></ul><ul><ul><li>Ken Klingenstein, Internet2 </li></ul></ul><ul><ul><li>Ben Teitelbaum, Internet2 </li></ul></ul>
    39. 40. Scratch Area Beyond this Point
    40. 41. Typical SIP Configuration
    41. 42. Registration Process
    42. 43. Call Flow (Claremont Graduate University SIP Client)
    43. 44. Secure Single Sign On
    44. 45. Redundant Processes Enterprise Directory Workflow, Database, Directory SIP IP-PBX Workflow, Database, Directory H.323 Video Call Server Workflow, Database, Directory Unified Messaging White Pages Enterprise Tools HR, Email, Billing, Parking, SSO, Web, Data Storage, VPN… Users
    45. 46. Directory Enabled Video / VoIP SIP IP-PBX H.323 Video Call Server Unified Messaging Enterprise Directory H.350 Directory White Pages Workflow Management Enterprise Tools HR, Email, Billing, Parking, SSO, Web, Data Storage, VPN… Users
    46. 47. Video Middleware- Videoconferencing (VidMid-VC) <ul><li>Web Site </li></ul><ul><ul><li>http://middleware.internet2.edu/video/ </li></ul></ul><ul><li>Chair </li></ul><ul><ul><li>Nadim E. El-Khoury, University of North Carolina at Chapel Hill Email: [email_address] </li></ul></ul><ul><li>Area Director </li></ul><ul><ul><li>Ken Klingenstein, Internet2 Email: [email_address] </li></ul></ul>
    47. 48. Video Middleware- Videoconferencing (VidMid-VC) <ul><li>Web Site </li></ul><ul><ul><li>http://middleware.internet2.edu/video/ </li></ul></ul><ul><li>Chair </li></ul><ul><ul><li>Nadim E. El-Khoury, University of North Carolina at Chapel Hill </li></ul></ul><ul><ul><li>Email: [email_address] </li></ul></ul><ul><li>Area Director </li></ul><ul><ul><li>Ken Klingenstein, Internet2 </li></ul></ul><ul><ul><li>Email: [email_address] </li></ul></ul>
    48. 49. VidMid-VC Charter <ul><li>Further the development of middleware for digital video and related areas. </li></ul><ul><li>Focus on resource discovery, authentication, and authorization for point-to-point and multi-point videoconferencing </li></ul><ul><li>Next on the agenda: Federated approach to Videoconferencing </li></ul>
    49. 50. VidMid-VC Accomplishments <ul><li>commObject became an ITU-T standard known as H.350, September 2003 </li></ul><ul><li>Video Middleware Cookbook – Directory Services for Multimedia Conferencing (Draft v0.5) released as part of NSF Middleware Initiative – Enterprise and Desktop Integration Technologies (NMI – EDIT) Release 4 </li></ul><ul><li>Partnered with Radvision </li></ul><ul><ul><li>Demo Endpoint self configuration using H.350 and authentication against LDAP, October 2003, Indianapolis, IN </li></ul></ul><ul><ul><li>Demo of ECS gatekeeper using H.350, October 2003, Indianapolis, IN </li></ul></ul><ul><li>Partnered with Claremont Graduate University, CA </li></ul><ul><ul><li>Demo SIP User Agent self configuration using H.350 and authentication against LDAP, March 2004, Indianapolis, IN </li></ul></ul><ul><li>Workshops </li></ul><ul><ul><li>H.350 Workshop, March 2004, Indianapolis, IN </li></ul></ul>
    50. 51. VidMid-VC Accomplishments cont. <ul><li>Directory of Directories for Video Conferencing, SURFnet, Netherlands </li></ul><ul><ul><li>Initial Demo, March 2004, Indianapolis, IN </li></ul></ul><ul><li>ViDe.Net </li></ul><ul><ul><li>100+ US, as well as overseas Universities are interconnected using H.323 network. </li></ul></ul><ul><ul><li>GDS (Global Dialing Scheme) </li></ul></ul><ul><li>Vendors with announced H.350 support </li></ul><ul><ul><li>RADVISION </li></ul></ul><ul><ul><li>Tandberg </li></ul></ul><ul><ul><li>VCON </li></ul></ul><ul><ul><li>HCL </li></ul></ul><ul><li>Demonstrated directory enabled presence and instant messaging </li></ul><ul><li>Demonstrated clickable dialing </li></ul>
    51. 52. What's Next <ul><li>Continue coordination </li></ul><ul><li>Make real </li></ul><ul><li>How to get involved? </li></ul>
    52. 53. VidMid-VC – Next Up: Federated Real Time Communications <ul><li>Will allow </li></ul><ul><ul><li>Inter realm authentication </li></ul></ul><ul><ul><li>Instead of users obtaining all services from their home domain, they will be able to access services from many service providers. </li></ul></ul><ul><ul><li>Users can authenticate each other. For example, an online video doctor can authenticate patients and drug suppliers from other domains, growing the market to more of an e-commerce model. </li></ul></ul><ul><li>Will apply to </li></ul><ul><ul><li>Video conferencing </li></ul></ul><ul><ul><li>VoIP </li></ul></ul><ul><ul><li>IM / Presence </li></ul></ul><ul><ul><li>PSTN </li></ul></ul><ul><ul><li>Cellular network </li></ul></ul><ul><ul><li>Internets 1 & 2 </li></ul></ul><ul><li>Work Plan – Join Us ! </li></ul><ul><ul><li>Year 1 </li></ul></ul><ul><ul><ul><li>Create Architecture </li></ul></ul></ul><ul><ul><ul><li>Standardize through ITU </li></ul></ul></ul><ul><ul><li>Year 2 </li></ul></ul><ul><ul><ul><li>Define protocol specific implementations </li></ul></ul></ul><ul><ul><ul><ul><li>SIP </li></ul></ul></ul></ul><ul><ul><ul><ul><li>H.323 </li></ul></ul></ul></ul><ul><ul><ul><ul><li>etc. </li></ul></ul></ul></ul>This Changes Everything !