jhg03a commented on pull request #5043: URL: https://github.com/apache/trafficcontrol/pull/5043#issuecomment-698421536
It's required for us, but I think it ought to be required generally even though it's not been enforced today. The goal of tracking the mapping of ASNs to Cachegroups is so that a transitive mapping between subnets and cachegroups can be created as part of CZF file generation. Trying to assign the same subnet to multiple cachegroups doesn't make a ton of sense to me. Keep in mind too that some entities don't break their subnets into geographically based ASNs which CDNs have no control over or input on. So in this case the argument for multiple mapping could be made but it's still just guessing at that point as the CZF file used by TR will only ever use one path to the best of my knowledge. I think that's still the right behavior as well because you want IPs to land in cachegroups by way of CZF hits consistently. Having multiple options there could lead to indeterminate behavior also making cachegroup capacity planning more difficult. ---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected]
