ok cool.  I definitely prefer another name to encode/decode; otherwise it blends in with the other calls and makes it look like we're encoding addrs twice. 

I think my last suggestion then (and it occurs to me that this might not be what i said before, sorry!) is that we keep the in-memory struct (in entity_addr_t) as a native sockaddr_storage (so that it can be readily used), and pretty much only use ceph_sockaddr_storage at the encode/decode stage when sending it over the wire.