Hello all,
Thank you, Marco.
Each such physically separated network may qualify as a separate end site. Furthermore, where an individual end site has different routing requirements (for example due to security-separated environments) the IPv6 policy explicitly allows multiple assignments to that same end site.
I would like to build on those two clarifications.
To provide a concrete example, we can consider a single data-centre facility operated by one infrastructure provider.
Each tenant/subscriber has a direct contractual relationship with the provider, and each environment has one stable /48. Although they share the same physical premises, the networks are separately connected and administered.
One of those tenants also operates twelve persistent virtual network environments inside its tenant environment. The infrastructure provider makes the assignments directly. The environments fall into exactly three groups:
This is intended as a concrete case where the physical site, the operational site and the routing site do not coincide. Each environment is stable and retains the same /48.
Depending on the test applied, the relevant End Site could be:
Possible directions for clarification might therefore include defining the End Site by the subscriber relationship, physical premises, routing boundary, operational domain, or an explicit combination of those factors.
I would be interested in how others would classify the three groups above and which underlying test they would apply.
Best Regards,
Yuli