...
Detailed information on eduroam availability in the neighbourhood of the pilot schools can be found in Appendix A. : Eduroam near schools - details.
Pilot schools, as well as eduroam availability in their neighbourhood, are depicted in the interactive map below (click the map).
2.3.1 All Up2U pilot countries
...
One of possible implementations is based on geo-located Domain Name Server (DNS) service that responds to a user’s domain lookup query indicating the IP address of the proxy (edge) server that is the “nearest” for the user. Then, the user communicates with the edge server and, if the edge server has the desired content (cache), no transfer to and from the origin server is needed. Otherwise, the edge server fetches first the content from the origin server, and the first user requesting this particular piece of data waits for the response a little bit longer.TODO: provide better image of geoDNS layout
Various benefits can come from using CDN. From end-user perspective, it is an increased Quality of Experience: data download time and latency are reduced, and availability of the service is improved (if a desired data is available in an edge server then a downtime of the origin server does not prevent users to access the data). From the network perspective, CDN provides better network performance: the number of hops during the data transfers is reduced, possibility of bandwidth saturation is lowered, and the traffic in backbone network is also reduced. From the content provider perspective CDN causes lower costs: less network load and reduced possibility of service downtime.
...
A communication that we can definitely improve is end-users’ access to static data. Most of the static data we deal with in the project can be found in content repositories of multimedia objects. As shown in the previous section, this is where a CDN can be successfully implemented, and the effectiveness of the CDN can be improved by the underlying network. The point-to-point network services cannot be applied for this case, because it would be then difficult and expensive to add new edge servers and set up circuits between a new server and all existing repositories. However, the VPN solutions from GÉANT portfolio could be easily used to support the CDN. If we put all the content repositories (i.e. origin servers) and the edge servers in a common MD-VPN or L3-VPN, then it will be easy and costless to quickly manage changes: adding or removing edge servers or repositories. In this case, data isolation across the GÉANT IP and even an allocated bandwidth could be ensured.
...
If we choose MD-VPN, as the simpler VPN solution without bandwidth allocation, to support the CDN, we shall consider to manually use GÉANT BoD when larger data transfers between some points in the CDN are expected. Such a common case could be adding new edge servers or repositories to the CDN. A new “empty” edge server can be “warmed up”, i.e. forced to fill up the cache with large amounts of data from the origin servers, to improve quality of experience for users who first request the cache for particular multimedia objects.
...