In recent years a few people (myself included) have tried again to inject the use of DNS service records into the HTTP/2 effort and have been consistently knock

In recent years a few people (myself included) have tried again to inject the use of DNS service records into the HTTP/2 effort and have been consistently knocked back by the authors. Last I looked, the new standard was studiously burying its head in the sand and avoiding mentioning lower-layer resolution issues at all, as though things like dual-stack IP, port number variation or the zone-apex issue were Somebody Else's Problem. Whilst I think they are glaring UX issues for HTTP clients that arise directly from the continuing and mistaken default of resolving address records. Of course what we get instead is unspecified and even conflicting* behaviour, which I think just stinks. Many other standards have managed to get it together by specifying the use of SRV. I gave up trying to change the entrenched positions. * there is language in the draft that advises against multiple connections, conflicting with the current "Happy Eyeballs" dual-stack resolution workaround.