Encode auth filed with 0 in RPC response
On non blocking threads when encoding the RPC response the auth field
was just skipped (64 bits) but not written. Depending on some bit
value in the auth field the size of the auth field may vary and so
on the RPC client the response decoding can fail.
It is safer to write 64 bits with 0 than just skipping 64 bits.