Registration flow

decoy registrar:

Detector tracks TLS flows, looks for first AppData from client, looks for elligator-tagged ciphertext, and extracts registration. Shares reg with application via zmq.

Then application ingests registrations in ingestRegistration() (https://github.com/refraction-networking/conjure/blob/46fea9be3592c26b8841d53438264af5b740a544/pkg/station/lib/registration_ingest.go#L129). If this is a detector-based registration, then share with API via tryShareRegistrationOverAPI()

Registration API:

Here the registration API accepts the reg, and then shares it with all the stations (applications), but does not share with other reg server

Conclusion:

decoy registrations could be heard by 1 or more registration API servers, but other registration types should be partitioned across reg API servers