Re: Service vs. Port vs. SRV (following Eliot's presentation)

[Keith Moore <[e-mail]>]

> So changing our model to focus on SRV has some interesting implications.

for instance,

SRV puts more fine-grained control in the hands of a DNS administrator - 
  even in cases where the host owner and DNS admin aren't part of the 
same entity.  (do you really want your ISP dictating which ports you run 
services on, or being able to vector traffic intended for your host to 
other hosts?)

SRV slows down connection establishment.  we already have a lot of 
overhead in DNS lookups (A + AAAA records and sometimes PTR records), 
TCP setup, SSL/TLS setup, etc.

SRV has the potential to create problems if retroactively applied to 
existing apps as the behavior of a SRV-aware client will differ from 
that of a non-SRV-aware client.

the design of getaddrinfo() is such that it could be used to do SRV 
lookup, but (if not done carefully) this would break that aren't defined 
to use SRV.