Internet2 Middleware Initiative

Discussion Outline  What is Middleware why is it important why is it hard  What are the major components of middleware  Where are we today  Internet2 Middleware Initiative

What is middleware?  specialized networked services that are shared by applications and users  a set of core software components that permit scaling of applications and networks  tools that take the complexity out of application integration

What is middleware?  sits above the network as the second layer of the IT infrastructure  the intersection of what networks designers and applications developers each do not want to do

Why is middleware important?  Enables a scalable approach to ubiquitous computing  With interoperability, permits academic research community to collaborate nationally and internationally and utilize specialized network resources  Middleware is necessary for the deployment and creation of advanced applications

As an end user it offers me...  single logons  a single place for my personalized information  institutional file systems for archive and backup  permission to use distant scientific resources  access to digital libraries

As a developer it offers me…  Building blocks for faster software development  Abstractions to hide networking details  The ability to focus on content issues rather than programming challenges

As a CIO it offers me...  the second layer of the IT infrastructure  leverage to both instructional and research missions  scalable infrastructure for applications  a more secure IT environment  a chance to resolve the silos and fiefdoms of information

A Map of Middlewareland Network-layer middleware Core middleware Ubiquitous Computing Upperware Research Oriented Upperware Business Upperware

Core Middleware  Identity - the first characteristics of who you are  Authentication - how you prove or establish that you are that identity each time you connect  Directories - where the rest of an identity’s characteristics are kept  Authorization - what an identity is permitted to do

Middleware and Higher Ed  We have different characteristics than corporations mobility multiple roles per individual non-monetary economies Open Records and FERPA

Middleware and Higher Ed  Some pieces have small commercial markets remote instrument control coscheduling of distributed resources digital libraries

Middleware and Higher Ed  By role and mission we are often pre-market roaming profiles interoperability among competitors

What makes it hard?  Technology issues where are the products Where are the protocols for interoperability  Practice issues Design and designers What’s the metadata Top-level authorities

What makes it hard?  Policy issues FERPA and Open Records Legacy systems, legacy thoughts

I2MI  Starting discussion - NPPAC and TAC  Next steps  Doing the work - on a continuing basis  Dissemination - dissemination and dissemination

NPPAC Discussion  Defining the IT environmental needs  Recognizing current constraints on campus IT organizations  Policy issues and reality checks

Technical Advisory Committee  Defining the technical requirements  University IT architects - the best and the brightest CMU, Stanford, MIT, Michigan, Washington, California, Brown, Notre Dame  Partners - Educause, PACI, CNI  I2 Staff

I2MI Goals  Interoperable middleware infrastructures help campuses develop infrastructures coordinate interoperability  Get some key apps involved digital video inter-institutional resource sharing

I2MI Goals  Work for the PACI and other research needs  Link to network layer needs  Understand what automating the policy layer takes

First Phase Work (6-12 mo)  Capture what we know now.  Get campuses understanding the issues.  Establish some basic public domain tools.  Synchronize activities with partners.

First Phase Work (6-12 mo)  Influence vendors.  Engage and inform political processes - AACRAO,NACUBO, NACUA, NASULGC,etc.  Continuously distill and disseminate.

Intelligence gathering  Talk to advanced campuses Identify common issues Identify distinctive factors Gather implementation approaches Leave in place ongoing intelligence gathering

Intelligence gathering  Work with PACI sites  Digital video  Digital libraries and inter- institutional resource sharing  Help distill and disseminate vendor information

Dissemination  Interoperability requires broad information and consensus  Roadmaps  Work with our partners

Dissemination  Work with the membership In seminars In tech talks on the net On the web At member meetings In print

I2MI RoadMaps  Outline the issues  Suggest decision criteria for implementations  Identify vendor products and associated issues  Point to leadership approaches  Establish interoperability criteria

Establish tools  Vendor interoperability  Link middleware to applications  Foster public tools Solidify key glues and adhesives Point to reference implementations

Create standards and consensus  Synchronize partners  Convene consensus processes on needed conventions  Educate political processes - AACRAO,NACUBO, NACUA, NASULGC

Second Phase Work (12-24 mo)  Create cadres of institutions to somewhat synchronously deploy campus-wide middleware.  Provide technical support services and facilitate intercampus communications.  Harvest information and disseminate.

Supporting second phase participants  Communicate and enhance participant efforts  Identify key technologies and associated products  Foster middleware-based applications  Bring in expertise

Supporting second phase participants  Capture design wisdom and the art of the practice  Influence vendors to make products more higher-ed friendly  Inform campus policy processes

What we can do…  Depends on what you can do on your campus  Depends on what our partners can do  Depends on what you can help