Patrik Faltstrom wrote: > Not URI as the owner for the URI is prefixed with the service and protocol. My misunderstanding, sorry. > And due to the higher efficiency why I think URI is better than "HTTP > redirect via well-known-url". HTTP redirection redirects an entire URL to another URL and is well defined. However, though rfc7553 states: but instead of returning a hostname and port number, the URI record returns a full URI. As such, it can be viewed as a more powerful resource record than SRV. URI RR can not be used by applications without URL specifications, whereas SRV can be used by any applications using hostnames (and having IANA registered (or, well known?) service name). Worse, even with applications with URL specifications, what happens if the following URL: <scheme0>:<userinfo0>@<host0>:<port0><path0>?<query0> invokes URI query using <scheme0> and <host0> results in: <scheme1>:<userinfo1>@<host1>:<port1><path1>?<query1> How the original and the resulting components can be combined? Obviously, scheme and host will be replaced, but how other fields should be combined/replaced? SRV is already bad with port numbers, which I addressed in draft-ohta-urlsrv-00. Masataka Ohta