+95
−0
Loading
A partner learned our zones only from the CreateFederation answer, so an
agreement written after federating never reached it, and deleting a
federation left both sides' zone subscriptions behind; a new federation then
showed zones as subscribed that nobody had subscribed to.
As the provider, FM sends ZONES ADD/REMOVE to the partner's partnerStatusLink
when an agreement create or update changes the zones that partner is offered.
A partner we can't reach catches up on its next GetFederationDetails; the
agreement is stored either way.
As the consumer, FM applies ZONES ADD/REMOVE callbacks to the partner's
offered zones, and replaces them with every GetFederationDetails answer.
Deleting a federation drops the partner's subscriptions to our zones (when the
partner deletes it) or our subscriptions and the zones it offered (when we
do), since OPG.04 keeps subscriptions under the federation context.
Co-Authored-By:
Claude Opus 5.5 <noreply@anthropic.com>