Keith Moore wrote:
Since every web service has its own URI, SRV records don't work well to specify ports for web services.
That is a over generalization because an object identified by a URI, in general, is not accessible and not a target of web services. Instead, for objects accessible by single IP addresses and single port numbers, we can safely assume the following URL syntax: <scheme>://[<userinfo>@]<host>[:<port0>]<path>[?<query>] The problem, then, is that automatic conversion from the URL (assuming <host> is not a raw IP address but a domain name) to: _<service>._<proto>.<host> SRV <priority> <weight> <port1> <target> is impossible without some global database to convert <scheme> to <service> and <proto>, which is another level of indirection, which can be annoying. Instead, _<scheme>.<host> SRV <priority> <weight> <port1> <target> should simply work and the original URL will be converted to: <scheme>://[<userinfo>@]<target>:<port><path>[?<query>] interpretation of which depends on <scheme> and not affected by SRV. A remaining problem is lack of specification on how <port0> and <port1> interact resulting in <port>. See draft-ohta-urlsrv-00.txt for detailed discussions, though it assumes: _<scheme>._<proto>.<host> SRV ... which was fine when practically all the <proto> was TCP. Masataka Ohta
