You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 17 Next »

SECTION: GCC, TFs and SIGs

LEAD: Nicole Harris

DEADLINE: Final report April 28th 2017.  All TF and SIG input by 7th April 2017 please.

INFORMATION SEEKING:

o   GCC – vision paper on current state of the community and main challenges to be addressed.

o   TFs and SIGs – top issues that need to be addressed (i.e. the situation now) and view on what users will need in 5 years (i.e. where we need to be/what we need to be ready for).

OVERVIEW: A PPT with an overview of the process is available, which shows what is needed from the TFs and SIGs.  Background from the GPPC perspective is also available, but TF and SIG feedback should not be limited to "stuff we want from the project" but really focus on future trends and requirements.

DOCUMENT STORAGE: Nathalie has created a folder on the Intranet to store all the docs once they are created.

https://intranet.geant.org/gn4/2/Activities/NA3/Shared%20Documents/Forms/AllItems.aspx?RootFolder=%2Fgn4%2F2%2FActivities%2FNA3%2FShared%20Documents%2FREQUIREMENTS%20GATHERING%20REPOSITORY%2FGCC%20TFs%20and%20SIGs&FolderCTID=0x01200092DE4BD2CAD5344DA213EC9987CC86CB&View=%7B5F3C776F-1E6C-43EE-ADF1-D6D3D41248C4%7D&InitialTabId=Ribbon%2EDocument&VisibilityContext=WSSTabPersistence

QUESTIONS TO ASK:

The main question we need feedback on is:

  • What new service / development requirements do you see for NRENs in the next 3 - 5 years?

Supporting questions to help you guide discussions:

  • What are the priorities and specific ideas for innovation in these areas?  What services and capabilities not currently offered by GÉANT will be needed i n 3-5 years?
  • What is the potential impact of new technologies such as orchestration, automation and controlling applications?
  • Do we do enough to bridge the digital divide? If not, how could we make a more effective contribution?
  • Any regrets from opportunities not taken from funding sources, or priorities given to funding sources? 
  • How well do we do at NREN commitments early in the process of service device development?  The use of services, facilities and even the network varies a lot from NREN to NREN:  Should new services or new service features be developed only after a certain minimal number of NRENs express their commitment to offer/use them for their business?
  • Do you think we should make an effort to serve communities outside of the R&E community - following the ECs evolving priorities and flagship projects?
  • Do you see any significant future changes in the NREN business models affecting what they want to get from GÉANT Ass/Ltd. E.g Importance of SLAs and KPIs, use of non-commercial software from GÉANT Ass/Ltd, other projects or research groups.

TO DO: 

Gather information to feed into this process from the Task Forces and SIGs as follows: 

SIG / TFHow will requirements be gathered?Feedback                                      

SIG Greenhouse

Nicole Harris

Via mailing list and discussion with SC.  Nicole to take forward. e-mail sent and awaiting replies.

Developer community waning within the NREN world.  Lots of reliance on OSS but no strategy for long-term support for the software, very few NRENS have development strategy in place alongside procurement strategy, difficulties with maintaining developers.

Work on Docker recipes and approaches. 

SIG Multimedia (was WebRTC)

Peter Szegedi

  

SIG SCOPE

Nadia Sluer

  

SIG-ISM / WISE

Sigita Jurkynaite, Alf Moens (chair)

Sent the questions out to the SC - asked to provide feedback before 7 April. 

SIG-Marcomms and SIG MSP

Laura Durnford, Gitte Kudsk (DeIC), Maria Ristkok (EENet), Lonneke Walk (SURFnet - chair)

 

Laura Durnford / Magda Haver, Walter van Dijk (SURFnet), Mark Tysom (Jisc), Harri Kuusisto (CSC-Funet), Alberto Perez (REDiris), Martin Bech (DeIC - chair)

Planned for upcoming meetings. 

Presentation by SURFnet:

  • Envision needing more services focused on campus domain, ICT services etc and so GEANT would need to help improve national service delivery and economies of scale.
  • Current GEANT portfolio reflects tech- driven services. IN NL have started to facilitate coalitions of the wiling – Ict managers  etc to help develop and launch new services, result in extension of the portfolio. So want demand aggregation, joint tendering, tender management as something GEANT can do to support.
  • Need staff available to facilitate large-sclae procurement, operation management in trust, security & cloud – GEANT leans on NRENs for running T&I and security services, would be good if its staff could do that. Also if could support the ICT mangmnt of orgs such as NATO, ESA, UN that need GEANT and NREN resources.
  • GEANT academy to help NRENs acquire skillsets.
  • Automation of network services.
  • Just entering campus domain with service that allows us to manage their wifi – would be good to use a control plane to include campus domains.
  • Clouds – many campuses want to get rid of ICT depts. And use commercial solutions via NREN as broker. See commercial services where we know our customers want to be able to get them from us.
  • Want white label applications or software so can incorporate into NREN own portfolio
  • Open protocols and software are a must
  • Standardisation where possible.

Presentation by DeIC

  • Want GEANT to be the vehicle for everything we want to do in common among the NERns
  • Want cost reductions and opp for NRENs to make money supplying stuff to the rest of the community
  • Abolish the GENAT backbone and have it base on NREN connections and cross-border fibres
  • Network-side DDoD mitigation service
  • Joint procurements
  • NREN-to-NREN service provisioning
  • Enable eduGAIN to support ad hoc federations.
  • Orchestration of point-to-point connections through open APIs
  • Users, funders etc should come up with KPIs and we come up with the numbers.
  • Services should be white-labeled in several levels.
  • As a community should have a complete portfolio - if a new country emerged should have an ‘NREN-as-a-service’ offering.
  • funding model for NERNS has big impact. RedIRIS centrally funded, DeIC more in competition with others.

SIG-NGN

Brook Schofield, Rob Evans (chair)

Question posed to the entire mailing list. Awaiting comments.

Feedback in the STF meeting collected by Annabel/Nathalie might be relevant.

 

SIG-NOC

Charlie van Genuchten, Brian Nisbet (chair)

To be discussed with the SIG-NOC steering committee on April 5
  • There is a trend towards 24/7 support.
    • With the increase of international cooperation and exchange, clients have users from different time-zones and different countries, so they expect their students and employees to be able to have access to the network from any place at any time.
  • There will be a need for more managed services :
    • Radius
    • Authentication services
    • Federated sign on
    • Things that have been installed at one point in time and if they break, there is no one to fix them, especially in this age of automation.
  • More and more networks are being merged, which will bring new challenges in the future.
  • More input to come this evening and on Friday

SIG-PMV

Kurt Baumann

Via mailing list and discussion with SC.  Nicole to take forward. e-mail sent and awaiting replies. 

SIG-TNE

Esther Wilkinson, Sigita Jurkynaite

 new group, unlikely to be significant feedback at this stage. 

TF-CSIRT

Nicole Harris, Sigita Jurkynaite, Baiba Kasina (chair)

To be discussed with TF-CSIRT Steering Committee at upcoming retreat.  

TF-RED

Sylvia Kuipers + (TBC)

Planned for upcoming meetings. new group, unlikely to be significant feedback at this stage.

TF-Storage / SIG-CISS

Peter Szegedi, SC members

  
TF-MNM / other mobility groups 
  • licensed/unlicensed spectrum for education and research purposes.
  • the E-SIM for uniform access to unwired services and other cool related stuff.
  • Internet of Things: LoRaWAN infrastructure (or others in the licensed/unlicensed spectrum band, e.g. 802.11ah/NB-IoT).
  • LTE-U.
  • Internet of Things: "Smart Campus".
  • Indoor Location Based Services.
  • Fixed/Mobile integration on campuses, helping institutes purchasing the right "mobile service".
  • Supporting/pushing Wifi-calling at the campus.
  • DAS-networks: still needed, or obsolete?
  • Robust and redundant unwired network deployments (at campus) for emergency situations.
  • 5G projects and developments.
  • Wireless service (and beyond?!) by NRENs: do's and don'ts.
  • Cooperating with initiative such as WIFI4EU (or FON, iPASS, Boingo...).
  • developments and next steps for govroam internationally.
General 
  • Internet of Things. 
  • Data (with EUDAT? or RDA?)
  • Education / Humanities (with EUNIS?).
  • Campus Middleware (Internet2 / TIER).
  • Extending TCS (ACME Protocol Support + Lets Encrypt)
  • Usability.
  • 5G stuff.
  • Legal.
  • No labels