Hraban, the reason this bug is unresolved is that there is no standard for HTTP in SRV. someone needs to write an RFC and get it approved. Mark Andrews wrote a draft, but it never reached RFC status.
the SRV spec says that a standard must explicitly support SRV, you can't just apply it to a random protocol. it also says that the name from IANA assigned numbers should be used, but the registration for port 80 specifies several names: "http", "www" and "www-http". in other words, it's not clear if you should query for _http._tcp or _www._tcp -- this is why a formal specification is needed.
IETF is open for anyone to submit a draft. it just takes some time and interest for writing formal documents and engaging in IETF discussions.
Hraban, the reason this bug is unresolved is that there is no standard for HTTP in SRV. someone needs to write an RFC and get it approved. Mark Andrews wrote a draft, but it never reached RFC status.
the SRV spec says that a standard must explicitly support SRV, you can't just apply it to a random protocol. it also says that the name from IANA assigned numbers should be used, but the registration for port 80 specifies several names: "http", "www" and "www-http". in other words, it's not clear if you should query for _http._tcp or _www._tcp -- this is why a formal specification is needed.
IETF is open for anyone to submit a draft. it just takes some time and interest for writing formal documents and engaging in IETF discussions.