Page tree
Skip to end of metadata
Go to start of metadata

Statement of purpose


The true value of eduroam increases with its ubiquity. eduroam in every primary and secondary educational institution, library, and public space boosts the value proposition of the service immensely and regional networks and community anchor institutions present a unique and powerful partner to address this scaling issue. At the same time, this helps make community services, and the community that provides them, more sticky. K12s, as well as libraries and museums that are part of the K12 ecosystem, have thus far been underserved by eduroam in the US. eduroam Support Organizations (SOs) leverage their existing relationships with K12s, libraries, and museums to address this need. 

To better enable eduroam Support Organizations to serve these communities, Internet2 is undergoing a pilot with a small cohort of organizations to offer the service to K12s, libraries, and museums in their states and region. The Utah Education and Telehealth Network, which was the first regional to become a Support Organization, will work with Internet2 and the new SOs during this pilot. Internet2 will provide the SOs with a simplified business model, training and resources to build the expertise of their staff, and ongoing support. At the end of the first year Internet2 will work with the participants to assess successes and challenges of the pilot. Internet2 will take that feedback and look for changes to the model or fee structure. The next round of participants will then be welcome to sign up as Support Organizations.

Key responsibilities of Support organizations include:

  • Provisioning service for new K12, library, and museum constituents
  • Ongoing first level support for constituents
  • Providing an inventory of constituents
  • Participate in collaborative meetings with other participants. Discuss feedback, requests, program ideas with the Support Organization community

For an idea of what statewide deployments might look like for a Support Organization, we encourage you to read the report which was written at the end of Internet2 and UETN's yearlong statewide K12 program pilot for eduroam. 

Adding new participants to eduroam Support Organizations

2022 Cohort - Call for proposals

Internet2 will announce the call for 2022's cohort in October. Interested organizations should review the proposal process and rubric provided below. 

Members of the eAC along with InCommon eduroam team staff contributed to the review of the submitted plans. Considerations were be given to diversity of organization type and support structure in addition to level of readiness.

2021 Cohort Process

The InCommon eduroam team opened a call for participation in 2020. The team announced the 2021 Pilot schools the week of December 14th, with the expectation the participating candidates have fully executed their legal agreements by January 31, 2021. Network Nebraska and the Sun Corridor Network were selected to join Utah Education and Telehealth Network as eduroam's Support Organizations. 


Proposal Rubric for 2022 Cohort

Candidates are expected to submit a plan for the deployment of eduroam K12 organizations within their state. The plans are to include what percentage of the total K12 organizations the plan supports, who would be deploying the required supporting infrastructure, a description of their infrastructure and how a candidate intends to create a sustainable support model. The plans will be judged by the below criteria. Feedback will be provided on each submitted plan. 

eduroam Support Organization candidates must respond to each requirement. The top row shows how each High/Medium/Low readiness level is defined. These requirements will also be weighted. For example, a candidate’s response for “Serve K12s, libraries, museums” will carry a higher value than their response to “Using eduroam internally”.


Organizational Requirements

High

Medium

Low

Serve K12s, libraries, museums

Directly engages with these communities to provide network and other services 

Has partnered with another organization or state government entity which engages with these communities to provide network and other services 

No direct engagement with these communities 

Can ensure its constituents and their users abide by terms of agreement

Existing contracts with K-12 in state/region, can sign agreements on behalf of K-12

Some contracts for services provided to K-12s in state/region

No vehicle for monitoring compliance

Using eduroam internally 

Yes

Rolling eduroam out

Joining now

Additional factors which make your organization a good fit for the program

All/most of the “Medium” and…

Experience with IAM, partnership or operational connection with state educational departments

Engagement on Regional calls, Existing relationship with Internet2 (e.g. network connection, participation in CAP, NET+ service engagements…)

N/A

Planning Requirements

High

Medium

Low

Roll-out team and roles identified and have cycles 

Staff time is allocated in the following areas: help desk, identity management, wireless, documentation, and communication leads

Staff time is allocated in the following areas: help desk, identity management, wireless

Identified roles but are still assembling their team

Early adopters identified and agree to take part in the plan

Adopters have piloted service and/or demonstrated interest

Provides a list of schools/districts that have expressed willingness to adopt

Provides list of possible adopters

One or more eduroam pilots/implementations completed (bonus points for K12, museums, libraries already subscribing)

Existing contracts in place and implemented

One or more K12 districts are in the process of provisioning service

No K12s currently using eduroam

Constituent Infrastructure Requirements

High

Medium

Low

Wired network infrastructure

  • Network connectivity to site 
  • Local network

More than 90% of the constituents meet the criteria

60-89% of the constituents meet the criteria

Fewer than 60% of the constituents meet the criteria

802.1x compliant wireless infrastructure

  • Wireless APs, 802.1x compliant
  • Controller or management system for wireless APs

More than 90% of the constituents meet the criteria

60-89% of the constituents meet the criteria

Fewer than 60% of the constituents meet the criteria

Identity store

  • An authentication server
  • User accounts populated onto server

More than 90% of the constituents meet the criteria

60-89% of the constituents meet the criteria

Fewer than 60% of the constituents meet the criteria

RADIUS Server

  • Server running a variant of RADIUS
  • Configurations made to the local network to allow it to route authentication requests

More than 90% of the constituents meet the criteria

60-89% of the constituents meet the criteria

Fewer than 60% of the constituents meet the criteria

Resources

Document Repository

Participant Resources









  • No labels