1. October 2, 2001 Middleware: Pieces and Processes RL "Bob" Morgan, University of Washington

2. Topics Internet2 Middleware Initiative Architecture and Infrastructure MACE Middleware activities Outreach: Calling All Architects

3. Internet2 Middleware Initiative April '99: time to move up the interop stack, start middleware program I2-initiated, campus-driven "Institutional infrastructure architecture"... OK, let's call it "middleware" Intra-campus before Inter-campus Standardization before new development "Somebody should..."; OK, let's!

4. Architecture + Infrastructure Architecture: software modularity on a grand scale Infrastructure: software architecture implemented as institutional services Supporting transparent interconnection of resources (when authorized) and no connection (when not)

5. Infra/Architecture Example Monolithic Portal •user database, authentication scheme, calendar, channels, legacy access, content management, "all in one seamless bundle" •an integration, support, infra problem Infra/Arch-based Portal •same components, but separable, so can work with existing elements, support others as infra itself •an integration asset, not a burden

6. Middleware Dichotomies Infrastructure: concrete, service-oriented Architecture: abstract, design-oriented Directory: Finding stuff Security: Keeping stuff hidden Integration: App-specific functions Consistency: Making all apps the same

7. A Map of Middleware

8. MACE Steering committee for mware activities Initiate, review, track mware projects Evangelize "architecture" issues Establish "shared state" on complex topics Create liaisons with European peers, "Grid" workers, Educause, etc

9. MACE Members •Ken Klingenstein (Internet2, director) •Steven Carmody (Brown), Michael Gettes (Georgetown), Paul Hill (MIT), Jim Jokl (Virginia), RL "Bob" Morgan (Washington, chair), Mark Poepping (CMU), David Wasley (UCOP) •New members: Bruce Vincent (Stanford), Scott Cantor (Ohio State) (tentatively) •European liaisons: Brian Gilmore (Edinburgh), Ton Verschuren (SURFnet) •Grid liaison: Von Welch (Argonne/NCSA) •Educause liaison: Steve Worona

10. I2-MI Process Standardization, best practice, integration IETF-inspired: open, solution-oriented, energy-driven, self-organizing Technical working groups with lists, phone calls, home pages, documents I2 supplies flywheel, scribing support Capture that thought!

11. Directory activities Directory service: the institutional PDA EduPerson schema: basic standards HE Dir of Dirs: basic inter-campus interop, scaling, policy Directory challenges: privacy, data ownership, app integration, semantics, multi-directory linkage, objects other than people, groups,...

12. Security Activities Focus: Authentication + Authorization HE PKI: establishing basic interop, basic policy agreements, right "weight", working with US FPKI Shibboleth: Inter-organizational web authentication and authorization WebISO: Intra-campus web sign-on

13. Integration Activities Video middleware: directory and A&A support for conferencing and streaming •conferencing/presence attributes, endpoint authentication, datastream protection, ITU standards,... MaceMed: middleware support for academic medical centers •HIPAA, HIPAA, HIPAA

14. Outreach Middleware courseware (I2MCP?) New: establishing I2 "IT architect" lists for announcements and discussion New: "Joint Architects" meeting (ala I2 Joint Techs) in early 2002 TERENA "networks for collaboration" Limerick, Ireland, June 2002 (www.terena.nl)www.terena.nl

15. Futures More Inter-campus infra experiments Authorization Web services, XML Content control (aka Digital Rights Mgt) But mostly, more integration And more campus participation!

16. NSF Middleware Initiative NSF-funded program to establish standard environment for scientific computing Internet2, Educause, SURA + GRIDS Challenge: linking campus-wide infra with big-science-specific infra The work begins now...