This one might have a larger chance of being accepted, since it provides some things which HTTP standard bodies and HTTP client vendors want. It doesn’t (at this stage, anyway) provide for the load-balancing “weight” field from the SRV record, but it does support MX-style priority numbers, and also port numbers. Very interesting, to say the least.
e.g. _http._tcp.example.com and _https._tcp.example.com
It seems there was such a draft: https://tools.ietf.org/html/draft-andrews-http-srv-02