Proposed Terms of Reference

1. Project Background

1.1 Context

Following on from the success of eduroam as a service within the global NREN community, several organisations are exploring the potential of replicating this service more broadly within the public sector as govroam.

Belnet and the Dutch govroam foundation (govroam-NL) have recently agreed to operate jointly with the further development and cooperation of govroam within their repsective countries, and recognise the importance of initiating a process around the internationalisation of govroam at an early point within the project.  Belnet and govroam-NL have approached GÉANT to provide coordination support to this effort.

A lack of international coordination in the initial phase will jeopardise the common aim to achieve the final goal of having only one international govroam service, based on a common interworking philosophy and following the same standards, procedure and methods. 

It is proposed that a project and framework be developed within the context of the GÉANT Community Programme to support the development of govroam based on the aims and workplan described below.

1.2 Reason

1.3 Benefits

The benefits for GÉANT and its members:

• As shown from the GÉANT compendium, many NRENs have some remit for serving and supporting government departments.  Supporting the roll-out of govroam would be a "quick win" to supporting connectivity within those departments.
• NRENs and GÉANT receive various grants and financial support from government departments.  The roll-out of govroam is a good showcase and quick-win to show the value add that NRENs can bring.
• Potential for cross-roaming can be of benefit to both communities, broaden the reach of both networks.
• Implementation at EC buildings would provide opportunities and benefits for a wide variety of communities. 

The benefits to the govroam community:

• Beginning standardisation work as early as possible within a global initiative means that participating countries will not have to migrate from local develops to internationally compliant processes and can implement services
• Building on the experience of eduroam means that govroam can be establish at an escalated rate and learn from the collective knowledge of experts in the NREN community. 
• govroam and eduroam can both benefit from joint developments in terms of support tools and processes.
• Potential for cross-roaming can be of benefit to both communities, broaden the reach of both networks.

1.4 Audience

Recognising the indispensable role of the NREN’s to support the introduction of govroam in their home countries, it should be kept in mind that govroam is aimed at a different target group and will only be successful if the services are accepted as specific services for the public sector and if the services fit well in the specific organisational structures, the customs, the working methods and the culture and traditions of this sector.  The position of individual NRENs regarding govroam is likely to differ greatly depending on the remit and funding structure in each national context.  A rough overview of the current position of NRENs with regard to government department connectivity is available, based on answers provided to the GÉANT Compendium.

GÉANT will provide both open communication lists that any interested party will be invited to join and lists for closed working groups within govroam as appropriate.

2.  Project Aims:

1. • • To development one international govroam service;

     • To establish compliance, interoperability and governance development for govroam;

     • To allow per territory deployment via non-profit operators (and NREN crossover);

     • To support close co-operation with the NREN/GÉANT community;

     • To define the meaning of “public sector” as a target group;

     • To avoid technological and operator divergence.
       
       

3.  Work plan:

• 
  
  • Website, wiki and communication support.
  • Definition of organisation and user eligibility.
  • govroam compliance statement.
  • securing rights.
  • branding.
  • Support for implementation discussions.
  • Exploring existing tools.

WORKPACKAGES	DESCRIPTION	COMMENT	ASSIGNED TO	START DATE	END DATE	STATUS
1. Pre-project (preparation)
2. Initiation
2.1
2.2
3.  Subsequent stages depending on the project (execution)
3.1
3.2
3.3
4. Delivery

4. Resource Requirements