Exchanging services between NRENs Challenges Initiatives and recent
Exchanging services between NRENs: Challenges, Initiatives and recent results TERENA Networking Conference 2011, Prague Deputy Director Martin Bech, UNI • C / Forskningsnettet. dk martin. bech@uni-c. dk 17/5 -2011
The services that make up an NREN – where do they come from? • NRENs provide a range of services – from basic internet provision to advanced database and cloud services • These services make up what we call the service portfolio of the particular NREN • The typical number of services of a “standard NREN” is around 30 NREN Forskningsnettet Uninett SUnet (DK) (N) (S) FUnet (FI) RHnet Red. IRIS (IS) (ES) Services 29 37 15 44 28 32 Source: Nordunet Inter. NREN service map and TERENA Service Map pilot Service Exchange between NRENs Martin Bech 10/2/2020 2
The services in the service portfolio – where do they come from? Source Typical examples Home made by the NREN DNS, NTP Direct re-sale of a commercial product Red. IRIS Spam Filter, i. Pass, virus scanner software (with little or no value addition to the service itself) Produced by members of the NREN Grid services, WAYF. dk, media repositories [Edumedia] From a regional network organization (NORDUnet) MCU Service From GEANT/Dante/EU Projects i. SHARE, Auto. BAHN, Perf. SONAR A combination, probably with some local value addition Adobe Connect Service And then there is the case we look at here: Directly from another NREN, where it is originally produced in one of the ways above Service Exchange between NRENs 10/2/2020 3 Martin Bech
Why do we pursue the idea of direct service exchange between NRENs? • If the service is already a success in one NREN community, it will probably be a good first approximation of what your own NREN needs • A way to a more complete service portfolio for the NREN • Better economy of scale for the providing NREN • More value for money for the in-sourcing NREN • As many services are quite similar across the NRENs, this makes all the more sense. Service Exchange between NRENs Martin Bech 10/2/2020 4
The basic idea of the NORDUnet CTO Forum… The (CTO-like people of the) Nordic NRENs discuss all practical topics relevant to their community, e. g. : • Common projects • Cost sharing models for cross-border fibres • Compare service portfolios • Exchange of services when feasible Service Exchange between NRENs Martin Bech 10/2/2020 5
The Inter. NREN service provisioning working group • Initiated by the CTO Forum (after a EU-proposal on the subject that was not funded) • Making the relevant people in the NRENs work on service exchange Service Exchange between NRENs Martin Bech 10/2/2020 6
10/2/2020 8 Source: https: //portal. nordu. net/display/NORDUwiki/NREN+Services+map Service Exchange between NRENs Martin Bech
Service Exchange between NRENs Martin Bech 10/2/2020 9
Service Exchange between NRENs Martin Bech 10/2/2020 10
Service Exchange between NRENs Martin Bech 10/2/2020 11
Service Exchange between NRENs Martin Bech 10/2/2020 12
How we work with service comparison • Inspiration for what my NREN is missing • Get good ideas for new services • Gradually harmonize terminology • Compare service offerings, category per category • Finding best-of-breed among comparable services • Exchanging services • Operating services jointly Service Exchange between NRENs Martin Bech 10/2/2020 13
Obstacles To move beyond mutual inspiration is easier if we remove some of the obstacles: 0. Knowledge of what is available (service map) 1. A model for payment/cost recovery/procurement 2. Inter-NREN service exchange must be foreseen in calls for tenders and contracts 3. Federated AAI 4. Translation enabling 5. IPR clearing Service Exchange between NRENs Martin Bech 10/2/2020 14
Removing obstacles (1): Model for cost recovery and procurement Today, we have NORDUnet as a common serviceprovider Uninett NORDUnet SUNET FUNet Payment Service Exchange between NRENs Martin Bech 10/2/2020 15 Forskningsnettet RHnet
Obstacles(1): Direct exchange presents a procurement problem • EU procurement rules demand a regular call for tender • Difficult to create pilot trials, because everyone should have the same information as the trial partner in a subsequent call for tender • Also a burden for the supplying NREN Uninett SUNET ? Payment Service Exchange between NRENs Martin Bech 10/2/2020 16
Removing obstacles (1): How procurement is handeled • Simply by adding it to the NORDUnet portfolio Uninett NORDUnet SUNET FUNet Payment Service Exchange between NRENs Martin Bech 10/2/2020 17 Forskningsnettet RHnet
Removing obstacles (1): The legal status of a clearing-house According to a recent legal expert opinion, if a service is in the portfolio of NORDUnet, it may be procured directly by the NRENs without a call for tender process, because • The NRENs are part of their state government administrations • The governments or the NRENs own NORDUnet jointly • NORDUnet has no other owners and is entirely economically dependent on its owners • Obtaining a service from such a joint venture is considered just like producing it yourself Therefore: No call for tender However, there may be a remaining question concerning the obligation of NORDUnet to procure by call for tender Service Exchange between NRENs Martin Bech 10/2/2020 18
Removing obstacles (1): Still a basic obligation to call for tender • No clearing-house can make the obligation to call for tender go away completely • If an NREN supplies to another NREN a service procured from outside by call for tender – then there is no problem (provided this is forseen in call and contract) • If an NREN supplies to another NREN a service which is homemade, then the procuring NREN still has an obligation to call for tender • The solution to this is to make the service a community project, where all participating NRENs contribute with development resources, making the supplier/procurer roles disappear. The ongoing development of NSI is an example of this Service Exchange between NRENs Martin Bech 10/2/2020 19
Call for tender process – also on behalf of NREN 2 and the Clearing-house Removing obstacles (1): Relying of the call of tender by one NREN Supplier 1 Supplier 2 Supplier 3 Supplier 4 Supplier 5 Maybe a clearing-house NREN 1 Service Exchange between NRENs Martin Bech 10/2/2020 20 NREN 2
Removing obstacles (1): Other NRENs have to call for tenders to procure a home-made service Supplier 1 Maybe a clearing-house Supplier 2 NREN 1 Supplier 3 Home-made service Supplier 4 Supplier 5 Service Exchange between NRENs Martin Bech 10/2/2020 21 NREN 2
Removing obstacles (1): Dissolving the supplier/procurer roles by making the service a community effort Supplier 1 Maybe a clearing-house Supplier 2 NREN 1 Supplier 3 NREN 2 Supplier 4 Home-made service Supplier 5 Service Exchange between NRENs Martin Bech 10/2/2020 22
Removing obstacles (2): Foreseeing service exchange • When a service is entirely home-made by one NREN, it is normally simple to supply it to another NREN. Think of web-site hosting as an example. • The contracts must allow for providing the service to other than your own NREN • When you do procurement using EU rules, you must tick the box ”purchasing on behalf of other contracting authorities” But beware: • When the service / products are sourced through a general State Procurement Process that do not include other territories, they can not be used. Service Exchange between NRENs Martin Bech 10/2/2020 23
Removing obstacles (2): Example of EU Call for Tenders • NORDUnet made a contract with Juniper stating that the connected NRENs could also buy equipment under the contract • However, in the original call for tender, they forgot to tick the box: Service Exchange between NRENs Martin Bech 10/2/2020 24
Obstacles (2): Foreseeing service exchange in contracts • This is not always easy as can be seen from this example: • Forskningsnettet in Denmark has an Adobe Connect service, based on a contract covering the national NREN • SUNet in Sweden has an Adobe Connect service, based on a similar contract • We call Adobe in order to negotiate a common procurement and hope for better prices, but their reaction was that now we are not academic, but a service provider and hence will have to pay more than double… Service Exchange between NRENs Martin Bech 10/2/2020 25
Removing obstacles (3): Federated AAI • Not mandatory to have in place (i. e. Forskningsnettet provides i. Pass to SURFnet in a pilot trial) • The Kalmar Union Service Exchange between NRENs Martin Bech 10/2/2020 26
Service exchange – existing and proposed • Sharing of housing and facilities • Basic server operation • i. Pass • H. 323 MCU and gatekeeper • Filesender/LOBBER • Anti-SPAM service …and more are to come as can be seen from the Inter-NREN service exchange map Service Exchange between NRENs Martin Bech 10/2/2020 27
Source: https: //portal. nordu. net/display/NORDUwiki/Inter. NREN_services_and_trials Service Exchange between NRENs Martin Bech 10/2/2020 28
Taking this idea to the next step: Europe • A topic for recent activities in the TF-MSP taskforce in TERENA • Starting with a service map for the European NRENs Service Exchange between NRENs Martin Bech 10/2/2020 29
TF-MSP Service Map example: Red. IRIS Service Exchange between NRENs Martin Bech 10/2/2020 30
Source: https: //confluence. terena. org/display/msp/Red. IRIS Service Map (cont’d) Service Exchange between NRENs Martin Bech 10/2/2020 31
Further ideas for service exchange for European NRENs • TERENA or Dante could act as a ”cleaing-house” for cost recovery etc. This should be studied closer! • A set of ”best practices” for creating ”exchangable” services has been proposed • Pan-European federated access for NREN services are created in GN 3: edu. GAIN • Examples of shared services already exist (fibres out of Europe, cross-boarder fibres, …) Service Exchange between NRENs Martin Bech 10/2/2020 32
Status of service exchange initiatives today (May 2011) Nordic Inter-NREN initiative Service Map Harmonizing concepts Procurement model Contracts and calls allow service exchange Federated AAI Translation enabling IPR issues resolved (where applicable) Service Exchange between NRENs Martin Bech 10/2/2020 34 TF-MSP initiative
- Slides: 32