100 likes | 123 Views
USHER CA serves U.S. higher education with root certificates, focusing on emerging needs like campus SSL, two-factor authentication, and federated digital signatures. Explore governance, requirements, pricing, and an Early Adopters' Program.
E N D
USHERU.S. Higher Education Root Certificate Authority John Krienke Manager, Integrated Operations, Internet2 Operations Manager, InCommon
Outline • CA for Higher Ed • Operations • Governance • Requirements and Pricing • Early Adopters’ Program • Timeline
1. USHER CA • The root for U.S. Higher Education • Emerging Needs • Campus SSL • Custom CAs (e.g., Temporary Conference Wireless Access) • Two-factor Authentication • CREN expirations • Campus VPNs • EduRoam • LionShare • Grids & Virtual Organizations • Bandwidth Management, security, e2e performance, • Federated Digital Signatures • Promise of secure, trusted exchange
2. Operations: Synergy Inter-realm and Intra-realm HEBCA (Educause) RA USHER CA (Internet2) PA PA OA Dartmouth
2. Operations: Sub CAs High LoA Low LoA USHER CA USHER Heavy USHER Lite Policy OID
3. Governance • The USHER Policy Authority • Michael Gettes • Jim Jokl (Chair) • Mark Luker • Barry Ribbeck • Jeff Schiller • Renee Shuey • David Wasley
4. Requirements and Pricing • Descriptive and/or Prescriptive • U.S. Higher Ed and Partners • Pricing Model: • RA services • Single Subscription Fee for Enterprise Cert • Cost Recovery • Incentive for Adoption • Input
5. PKI Early Adopters’ Program • Goals • Promote the use of PKi as a tool for business needs of institution • Improve the security and efficiency of networked interactions • Focus on local applications that might have broad and/or inter-institutional use • Output • Technical wisdom • Applications/infrastructure interactions • User/client issues and resolutions • Business plans • Recommendations for next steps, tuning the services • Local Project Support, Internet2 Flywheel, Technical Sharing, Visibility, Initial and Final Meetings • RFP soon: 5 - 10 institutions, Identify possibilities for federal interaction: C4, federated signatures, etc., jumpstart USHER
6. USHER Timeline July '05 • PA starts to iron out governance, CP, CPS • RPS draft with HEBCA PA • Agreements between organizations • Subscriber Agreement • Invitation to Early Adopters’ Program August '05 • Selection of ~ 5 - 10 Early Adopters • USHER Web presence September '05 • USHER goes live • Early Adopters meet March '06 • Early Adopter Program Ends • Technology Profiles and Best Practices written
Addendum: Challenges Technology Adoption Source: Thwarted Innovation, Zemsky and Massy, The Learning Alliance Questions? jcwk@internet2.edu