Les causes : Free a trop de clients  (ou version différente : Free n'a pas assez de GGC - il pensait que SFR a mis 2x plus de GGC uniquement pour chauffer le datacenter, or il semblerait qu'ils aient une autre utilisation)

Citation de: Florian le 14 septembre 2015 à 14:22:34

Techniquement ça doit être jouable pour Free et SFR de mieux balancer entre les GCC d'une même région en attendant un upgrade ... ?

Malheureusement c'est exclusivement à la main de l'aiguilleur de Google, il va falloir aux équipes de nos collègues beaucoup de persuasion et de tickets...

Ou c'est Google qui gère la chose ?

6.3 What to Announce Over the Peering Session
Google Global Cache uses BGP only as a mechanism to communicate the prefixes of users that should be served
from a node. It is not used for routing or to determine if the cache is online. An interruption to the BGP session
has no effect on the cache.

6.3.1 User and Resolver Prefixes
In order for the GGC node to perform optimally, both the IP address of the user and the IP address of the
DNS resolver they are using must be advertised to the cache.
While the vast majority of end user traffic is delivered by GGC nodes based on the end user’s IP address alone, a
small subset of requests use the IP address of the DNS resolver being used by the end user.
Optionally, Google also supports EDNS and you can increase the number of queries based on the user’s actual IP
address by implementing Client Subnet Information in DNS Requests.
Besides mapping, the user IP addresses are used to build an access control list on the node itself.
Note: GGC will ignore private IP addresses (i.e.: RFC 1918).

6.3.2 Peers and Downstream ASNs
Prefixes from other ASNs can be mapped to the cache as well, providing the following conditions are met:
• Both the DNS resolver and user prefixes must be advertised in order to both map and serve those users
from the cache
• If the other AS transits an AS with a peering relationship with Google, their traffic will not be mapped to
the cache. If an exception is required, please contact ggc@google.com.
• Do not send the full Internet routing table to the GGC node. Only send the prefixes that should be served
from the node.