While net/rpc supports HTTPS trivially in the server, there's no built-in way for a
client to connect to one since rpc.DialHTTPPath calls net.Dial itself. With some
duplicated code from client.go it's possible to create a working DialHTTPSPath in user
code, though this is suboptimal since DialHTTPPath references an unexported package
variable which must be duplicated.

https://golang.org/cl/100140043 implements rpc.DialHTTPS and rpc.DialHTTPSPath
which are exact analogues to DialHTTP and DialHTTPPath apart from also accepting a
tls.Config. This issue is mainly to track that CL during the 1.3 code freeze.

I originally proposed this at
https://groups.google.com/forum/#!topic/golang-nuts/M0LwsijM9bo; no objections were
offered.