TFMobility future Klaas Wierenga klaascisco com TFMobility Ume
TF-Mobility future Klaas Wierenga klaas@cisco. com TF-Mobility, Umeå, 8 July 2008 University of the Future © 2007 Cisco Systems, Inc. All rights reserved. Cisco Public 1
Where We Are § Two tasks forces finishing their terms in September 2008 § TF-Mobility –eduroam-NG, metering, other mobile technologies, sensor networks § TF-EMC 2 –TACAR, campus issues, directories, diagnostics, federation coordination and Grid liaison University of the Future © 2007 Cisco Systems, Inc. All rights reserved. Cisco Public 2
Achievements § eduroam –Well beyond our borders § Rad. Sec –Driving industry trends § TACAR –First stakes in the Grid camp § SCS –Almost universal service § SCHAC –Bologna and more § REFEDS gatherings –Re-focusing federation interoperation University of the Future © 2007 Cisco Systems, Inc. All rights reserved. Cisco Public 3
And Focus Problems § Too narrow in TF-Mobility –Most development work has moved to GN 2 –Need to find new topics to concentrate on § Too wide in TF-EMC 2 –Lots of topics to discuss in meetings –Insufficient time for in-depth discussion –And even more activities wanting consideration University of the Future © 2007 Cisco Systems, Inc. All rights reserved. Cisco Public 4
Middleware Is Cool § The basis for any network service –Vendors are already aware of it –And we have made good connections with them § A way for innovation at reasonable costs –Software intensive –Open source implementations are common place § The core for inter-institutional collaboration –Bologna is the word –Liaisons with other bodies: EUNIS University of the Future © 2007 Cisco Systems, Inc. All rights reserved. Cisco Public 5
But We Need to Focus § Middleware has a too wide meaning § Depending on the community –And where the community feels the stuff is –Middleware is the layer connecting the stuff to the rest of the world in a seamless manner § Our stuff is academic and research networking –But the definition above is still too wide –And perceived needs must be dealt first § Let’s concentrate on –Enhancing current achievements –Widen their application areas –Explore demanding aspects University of the Future © 2007 Cisco Systems, Inc. All rights reserved. Cisco Public 6
Proposed Course of Action § Continue with two TFs, re-focusing them –And making a better share of interests § Concentrated on –Collaborative service definition and deployment –Exploratory pilots –Standards and best practices –Coordination • National activities • Beyond the NREN community • Beyond Trans-European limits University of the Future © 2007 Cisco Systems, Inc. All rights reserved. Cisco Public 7
Two New Middleware TFs § With interest areas assigned across the protocol stack § One focused on middleware related to network services –Going beyond mobility technologies § One focused on infrastructure services –Specifically, on identity-related ones –Both for the network and the application layers § Coordinated by ECAM § And continuing with other activities –Euro. CAMPs –Grid-NRENs connections University of the Future © 2007 Cisco Systems, Inc. All rights reserved. Cisco Public 8
Across the Stack § Bottom layer of the application –PKI –Directories and schemas –{Con-, inter-}federation –Reputation The Application § Top layer of the network The Middleware –Mobility –Network access –Endpoint assessment The Network University of the Future © 2007 Cisco Systems, Inc. All rights reserved. –Provider integration Cisco Public 9
TF on Network Middleware § Mobility issues –Beyond around eduroam § Network access in general – 802. 1 x on everything § NEA –The other side of TNC § Control planes –Connection with NGN activities § Collaboration with providers –The 3 G use case §. . . University of the Future © 2007 Cisco Systems, Inc. All rights reserved. Cisco Public 10
TF on Identity Infrastructure § PKI –TACAR and SCS § Schemas –Making SCHAC grow § Directories –Steps towards semantics § Federations, confederations, inter-federations –Including the third ‘A’? § Reputation systems –Starting with e-mail applications §. . . University of the Future © 2007 Cisco Systems, Inc. All rights reserved. Cisco Public 11
To Conclude § Middleware activities have made relevant achievements –But need a re-focus § Essentially, keeps things going –If it works, don’t touch it § But redefine goals and areas –Well, touch it a little to keep it working University of the Future © 2007 Cisco Systems, Inc. All rights reserved. Cisco Public 12
Possible Activities § Investigate use cases for federated NEA –Definition of ‘cleanliness’ § collaboration with other communities "free services" (municipal, google, yahoo, FON etc. ) –Policy wrt remediation § reports –Remote posture § DNSsec § universal ethernet (UETS)? § Network desktop § cloud computing? § LBS § edu. Token § campus middleware issues wrt networking § Interworking with operators § Diagnostics? § Eduroam beyond Europe § reputation systems (anti-spam, anti-spit, p 2 p etc. ) § mesh, ad-hoc, p 2 p University of the Future © 2007 Cisco Systems, Inc. All rights reserved. § enum Cisco Public 13
- Slides: 13