Adding client ID to identify clients (and retrieve specific context)?

Although I can workaround it by generating a random UUID and both server and client agree to use that as a universal identifier, are there any better way to do this in tarpc without having to manually resolve the data context (not tracing context) all the time?

Right now, I use this to solve the client retry issue because the client can disconnect intermittently. Once the "key agreement" is established, I can replay the client messages logically so that we can resume on working. However, this also means the RPC methods must not have any side effect (i.e. idempotent)