Today’s meeting continued the review of the Trust and Identity portfolio and business model. Last month’s conversation included eduroam and the InCommon Certificate Service. Today will cover the InCommon Federation and software development.
Almost 970 participants
500 research, colleges and universities actively use the federation - that is, they publish metadata
About 210 sponsored participants actively use the federation
The remaining participants (~260) are either organizations coming up to speed on federation or are Certificate Service subscribers who only intend to use the Certificate Service
The InCommon participation fees support InCommon services and activities
Fees were increased in 2017 to close gaps in operational maturity, service maturity, scaling, and security. This generated $750,000 in new revenues for InCommon operations
The Steward Program long-term business model is to be determined. Currently, MCNC is the only Steward at this point, but there are other regionals interested and it is critical to recruit move into the program. There is also interest from Kevin Thompson (NSF) in the Steward Program’s potential to provide access to scientific instrumentation and databases for K-12 educational purposes.
Another gap is a place for CIOs and technical people from InCommon participants to gather. There is a perception that the Internet2 meetings aren’t for those folks.
Software Engineering, Development, TIER
The core software components of the Internet2 community software engineering and development efforts (Shibboleth, Grouper, COmanage) all originated with funding from the National Science Foundation (over $10M over the years)
There was also discussion about what is happening in the commercial sector that could potentially be a threat to InCommon, particularly if we leave it to those entities to control the conversation. We are in a good position to “own” the conversation. The PAG will continue this discussion next month.