20040421-rtc-forum.ppt
DESCRIPTION
TRANSCRIPT
Internet2 Real Time Communication Forum
Internet2 Member Meeting, Arlington, VA
April 21st , 2004
2
Goals for Today
Survey Internet2 Landscape• Who is doing what and why?• What are the unifying themes, directions, principals?• How should campuses prepare?
Understand Broader Landscape • Four distinguished, invited speakers• What are the broader technology trends?• What are the big challenges, opportunities, tradeoffs?
Panel Discussion• How can Internet2 best work to advance RTC?
3
Today's Agenda
1:15 – 1:35 Overview of Current Initiatives• “Internet2 RTC: Towards a Grand Unified Theory”
1:35 – 2:15 Invited Speakers• Andrew Odlyzko, University of Minnesota• Rodger Will, Ford Motor Corp
2:15 – 2:45 Coffee2:45 – 3:25 Invited Speakers (cont.)
• Peter Saint-Andre, Jabber Software Foundation• Henning Schulzrinne, Columbia University
3:25 – 3:45 Panel Discussion
Internet2 RTC: Towards a Grand Unified Theory
5
Outline
Unifying ThemesThe campus/enterprise roleSurvey of Current Activities
• Commons• I2IM• PIC • Research Channel?
• SIP.edu• VidMid-VC• Voice DR
6
Network Connectivity(high-performance, end-to-end IP transit)
Application Connectivity(call routing MW and signaling standards)
Use
rThe GUT of RTC: Middleware
User
Aut
h/Z
Auth/NIdentity
PresenceMessaging
Auth/Z
Auth/NIdentity
PresenceMessaging
Your campus is here!
ASPsGatewaysBridges
Trust
7
Inside the Belly: Alphabet Soup
Abilene
LDAPDNS
SIPH.323
Directories Call Control
IP
SIP/SIMPLEXMPP
Presence
SAMLShibPKI
Auth N/Z
DHCPCDPSNMP
Location Auto-ConfigC
ampu
s Ser
vice
s
BGP policy
GUI, display, ...
SIP/SIMPLE, XMPP, H.323
Voice Video IM Presence
App
licat
ion
RTP, SDP media
inCommonInternet2 Services
Bridging ServicesPSTN GW
MCUs
Cam
pus S
ervi
ces
App
licat
ion
P2P signalingP2P trust
8
Unifying Themes1/2
Leveraging Enterprise Assets• Identity management• Enterprise directories
Linking Identities• H.350
Growing Connectivity• SIP.edu
Securing RTC• Authentication• Authorization
• Network infrastructure• Physical infrastructure
• VideNet GDS
• Disaster recovery• Spam prevention• Encryption
• SIP.edu
9
Unifying Themes2/2
Building on Trust• iCommon• SIP.edu
Supporting Open Standards
10
Real Time Communications
EnterpriseDir
H.350
Client
User
Proxy
RTC: SIP Example
AuthN NetworkSecurity AuthZ
Client
User
Proxy
AuthZ AuthNNetworkSecurity
EnterpriseDir
H.350
Security Domain 1 Security Domain 2
11
Real Time Communications
RTC: Various Clients
User
AuthN NetworkSecurity AuthZ
User
AuthZ AuthNNetworkSecurity
Security Domain 1 Security Domain 2
SIPClient
H.323Client
IMClient
VoIPClient
XClient
EnterpriseDir
H.350Server ServerEnterpriseDir
H.350
12
Real Time Communications
RTC: Future...
Client
AuthN NetworkSecurity AuthZ
Client
User
AuthZ AuthNNetworkSecurity
Security Domain 1 Security Domain 2
User
PICPIC
Server Server
EnterpriseDir
H.350
EnterpriseDir
H.350
13
Current RTC Activities
Internet2 CommonsIntegrated Infrastructure for Instant Messaging
Presence and Integrated CommunicationsSIP.edu (VoIP WG)Video Middleware-VideoconferencingVoice Disaster Recovery
14
Presence and Integrated Communications WG (PIC)
Web Site• http://pic.internet2.edu/
Chair• Jeremy George, Yale University{email, im, sip}: [email protected]:203/436.4507
Program Manager• Ben Teitelbaum, Internet2{email, im, sip}: [email protected]
15
PIC Charter
Foster the deployment of SIP-based communication that integrate multiple communications elements in the
Develop technical deployment and use cases for campus presence and integrated communications services
Inform the emerging policy tussle
16
Chartered July 1st, 2003Conducted three rich presence trials
• Prototypes of next-gen campus communications services
• Highly-participatory trials at Internet2 meetings• New network infrastructure, middleware, and clients• Location-aware technology
Launched Social Context Study Group• Studying policy/privacy tussle for presence• Now in the formative stage
PIC Accomplishments
17
Internet2 Commons
Web Site• http://commons.internet2.edu/
Contacts• Jonathan Tyman, Internet2Program Manageremail: [email protected]
• John Krienke, Internet2email: [email protected]
• Cheryl Munn-Fremon, Internet2email: [email protected]
18
Internet2 Commons Charter
Promote and facilitate remote collaboration by means of innovative and integrated, standards-based Internet technologies
Create collaboration services that are...• Sustainable• Scalable• Affordable
19
Internet2 Commons Accomplishments
Launched H.323 videoconferencing service• Production, subscription-based service• Standards-based• Conference streaming and archiving• 24/7 NOC (OARnet/OSU)• Scheduled and ad hoc use
Studying Remote Collaboration and Improving Service Suite
• Extensive member interviews• Data Collaboration Survey with ViDe • Testing WebOffice and IMFirst
20
VoIP Working Group
Web Site• http://voip.internet2.edu/
Chairs• Walt Magnussen, Texas A&M Universityemail: [email protected]
• Mike Enyeart, Indiana Universityemail: [email protected]
Program Manager• Ben Teitelbaum, Internet2{email, im, sip}: [email protected]
21
VoIP WG Charter
Umbrella for a variety projectsDevelop and deploy advanced voice communications.
Understand the implications of network convergence
Improve the scalability, survivability, and functional richness of voice communications
22
VoIP WG Accomplishments
Workshops• VoIP Workshop, October 2003, Indianapolis, IN• VoIP Workshop, April 2002, College Station, TX
Projects• H.323 VoIP Testbed
–20+ sites peered through H.323 gatekeepers–Concluded (but continuing peering relationships)–Exploring scalable E.164 routing (e.g. ENUM)
• SIP.edu• Voice Disaster Recovery
23
SIP.edu
Web Site• http://voip.internet2.edu/SIP.edu/
Project Leader• Dennis Baron, MITemail: [email protected]:[email protected]
Program Manager• Ben Teitelbaum, Internet2email: [email protected]:[email protected]
24
SIP.edu Charter
Goals• Grow number of SIP connectivity and use• Increase value proposition for end-user SIP adoption• Promote converged electronic identity• Low entry-cost means for campuses to...
–Provide a useful initial service–Start getting their feet wet with SIP
Means• SIP.edu Cookbook available on web site• Partnering with vendors (Cisco)• Building community of implementers
25
SIP.edu Architecture
SIPProxyDNS
SIP-PBXGateway PBX
INVITE(sip:[email protected])
DNS SRV query sip.udp.bigu.edu
telephoneNumber where mail=”bob”
PRI / CASbigu.edu
CampusDirectory
SIP User Agent
Bob's Phone
sip. udp.bigu.edu IN SRV ...
INVITE(sip:[email protected])
26
SIP.edu Accomplishments
Completed proof of concept deploymentsPublished SIP.edu whitepaperDemonstrated LDAP integrationPublished SIP.edu CookbookApproaching 100,000reachable users
27
Voice Disaster Recovery (DR)
Web Site• http://voip.internet2.edu/dr/
Project Leader• Chris Peabody, Georgetown Universityemail: [email protected]
Program Manager• Ben Teitelbaum, Internet2email: [email protected]
28
Voice DR Charter
PSTN and Internet each have strengths and weaknesses
Combine VoIP and PSTN for better voice survivability than either architecture alone
Partner with carriers and vendors to provide a disaster recovery service to Internet2 members
29
Different Networks, Different Strengths / Vulnerabilities
•Open to internal attack•Mileage may vary (no QoS)
•CO is single point of failure•Local loop single point of failure
Stre
ngth
s•Network routes around failure•Packet-level call multiplexing•Adaptive, loss tolerant codecs
•Reliable QoS (once connected)•Reliable hardware•Impervious to DoS attack
InternetPSTN
Internet allows for gradual degradation of voice quality, rather than call blocking, which is what you want in an emergency
30
Voice DR Accomplishments
Virginia
GU/MAX
Network Gateway
Internet2
SIP-PRI
Boston
Network Gateway
SIP-PRI
TAMU
PSTN
Campus
LAN LAN
Campus
31
Integrated Infrastructure for Instant Messaging Working Group (I2IM)
Web Site• http://middleware.internet2.edu/i2im/
Chair• Michael Gettes, Duke UniversityEmail: [email protected]
Area Director• Ken Klingenstein, Internet2Email: [email protected]
32
I2IM Charter
1.Research the issues surrounding enterprise integration of IM services with respect to identity, authn and authz.
2.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..
3.Based on interest and technical feasibility, consider this range of issues for non-proprietary IM technologies.
4.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.
33
I2IM Accomplishments
Chartered Fall 2003 Developing use cases, scenarios, and requirements:
• Authenticated User• Anonymous / Pseudonymous User • Shibboleth-enabled Extensible Messaging and Presence Protocol (XMPP)
–Open, XML-based protocol for near real-time extensiblemessaging and presence.
–Core protocol of the Jabber Instant Messaging and Presence technology
–Near approval as IETF Standard
34
Video Middleware-Videoconferencing (VidMid-VC)
Web Site• http://middleware.internet2.edu/video/
Chair• Nadim E. El-Khoury, University of North Carolina at Chapel Hill
Email: [email protected]
Area Director• Ken Klingenstein, Internet2Email: [email protected]
35
VidMid-VC Charter
Further the development of middleware for digital video and related areas.
Focus on resource discovery, authentication, and authorization for point-to-point and multi-point videoconferencing
Next on the agenda: Federated approach to Video conferencing
36
VidMid-VC Accomplishments
commObject became an ITU-T standard known as H.350 in August 2003.
Directory of Directories for Video Conferencing, SURFnet, Netherlands
• Initial Demo, March 2004, Indianapolis, IN
Workshops• H.350 Workshop, March 2004, Indianapolis, IN
Demos• H.323 endpoint self configuration using H.350 and authentication
against LDAP, October 2003, Indianapolis, IN• ECS gatekeeper using H.350, October 2003, Indianapolis, IN• SIP User Agent self configuration using H.350 and authentication
against LDAP, March 2004, Indianapolis, IN
Panel Discussion
38
Panelists
Moderator• Steve O.?? Michael G. ??
Invited Panelists• Andrew Odlyzko, University of Minnesota• Henning Schulzrinne, Columbia University• Peter Saint-Andre, Jabber Software Foundation• Rodger Will, Ford Motor Corp
Internet2 WG Chairs and Project Leaders• Dennis Baron, MIT• Nadim Elkhoury, UNC• Mike Enyeart, Indiana University• Jeremy George, Yale University• Michael Gettes, Duke University• Walt Magnussen, Texas A&M
Internet2 Staff• Cheryl Munn-Freemon, Internet2• Ken Klingenstein, Internet2• Ben Teitelbaum, Internet2
39
40
Scratch Area Beyond this Point
41
Typical SIP Configuration
42
Registration Process
43
Call Flow (Claremont Graduate University SIP Client)
44
Secure Single Sign On
45
Redundant Processes
EnterpriseDirectory
Workflow,Database,Directory
SIP IP-PBX
Workflow,Database,Directory
H.323 VideoCall Server
Workflow,Database,Directory
UnifiedMessaging
WhitePages
Enterprise ToolsHR, Email, Billing, Parking, SSO, Web,
Data Storage, VPN…
Users
46
Directory Enabled Video / VoIP
EnterpriseDirectory
H.350Directory
SIP IP-PBX
H.323 VideoCall Server
UnifiedMessaging
WhitePages
Workflow Management
Enterprise ToolsHR, Email, Billing, Parking, SSO, Web,
Data Storage, VPN…
Users
47
Video Middleware-Videoconferencing (VidMid-VC)
Web Site• http://middleware.internet2.edu/video/
Chair• Nadim E. El-Khoury, University of North Carolina at Chapel HillEmail: [email protected]
Area Director• Ken Klingenstein, Internet2Email: [email protected]
48
Video Middleware-Videoconferencing (VidMid-VC)
Web Site• http://middleware.internet2.edu/video/
Chair• Nadim E. El-Khoury, University of North Carolina at Chapel Hill
Email: [email protected]
Area Director• Ken Klingenstein, Internet2Email: [email protected]
49
VidMid-VC Charter
Further the development of middleware for digital video and related areas.
Focus on resource discovery, authentication, and authorization for point-to-point and multi-point videoconferencing
Next on the agenda: Federated approach to Videoconferencing
50
VidMid-VC Accomplishments commObject became an ITU-T standard known as H.350,
September 2003 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
Partnered with Radvision• Demo Endpoint self configuration using H.350 and authentication against
LDAP, October 2003, Indianapolis, IN• Demo of ECS gatekeeper using H.350, October 2003, Indianapolis, IN
Partnered with Claremont Graduate University, CA• Demo SIP User Agent self configuration using H.350 and authentication
against LDAP, March 2004, Indianapolis, IN Workshops
• H.350 Workshop, March 2004, Indianapolis, IN
51
VidMid-VC Accomplishments cont.
Directory of Directories for Video Conferencing, SURFnet, Netherlands
• Initial Demo, March 2004, Indianapolis, IN ViDe.Net
• 100+ US, as well as overseas Universities are interconnected using H.323 network.
• GDS (Global Dialing Scheme) Vendors with announced H.350 support
• RADVISION• Tandberg• VCON• HCL
Demonstrated directory enabled presence and instant messaging
Demonstrated clickable dialing
52
What's Next
Continue coordinationMake real
How to get involved?
53
VidMid-VC – Next Up: Federated Real Time Communications
Will allow• Inter realm authentication• Instead of users obtaining all services from their home
domain, they will be able to access services from many service providers.
• 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.
Will apply to• Video conferencing• VoIP• IM / Presence• PSTN• Cellular network• Internets 1 & 2
Work Plan – Join Us !• Year 1
– Create Architecture– Standardize through ITU
• Year 2– Define protocol specific
implementations• SIP• H.323• etc.
This Changes
Everything !