Flexibility for "primaries" for complex infrastructure designs?

[karldyson]

I asked this in the Mattermost, but best I ask here to track any discussion.

In some more complex implementations, there may be a situation as follows:

[unsigned primary]-->[signer]-->[distribution]-->[anycast edge]

The edge may even have further layers of distribution for large global infrastructures.

Clearly each "layer" of the infrastructure would have different upstream "primaries".

Do we want to try and be flexible enough to cover such scenarios at the risk of adding quite some complexity?

[wtoorop]

Well.. when using catalog groups, each layer could have a different primary associated with that group