In order to ease connection tracking we should attach some metadata to Netty channels that can be retrieved either via the REST or via protocol specific APIs (e.g. Resp's CLIENT INFO)
The following information should be attached:

• ID: a unique per-server identifier. For compatibility with RESP, use a 64bit int
• Principal: the main principal associated with the connection
• Client library name and version. Set by the client. For example, HTTP would use the User Agent header
• Name: a client defined name (cfr. Resp's CLIENT SETNAME)
• Creation timestamp