One of the thoughts I had before David posted the beginning of this thread is that maybe we  could use this opportunity to update rxsock itself, so that it better uses the newish APIs and is object orientated than rather than procedural. 
Upwards-compatible could be tricky.  

Maybe just add a new library ('rxsock6'?) which is unencumbered by past history.