2004-06-02 kl. 08.50 skrev Johan Danielsson:

> Applicability Statement
>
>    In general, it is expected that SRV records will be used by clients
>    for applications where the relevant protocol specification indicates
>    that clients should use the SRV record. Such specification MUST
>    define the symbolic name to be used in the Service field of the SRV
>    record as described below. It also MUST include security
>    considerations. Service SRV records SHOULD NOT be used in the 
> absence
>    of such specification.
>
> How do you implement this?

Ah, well, I skipped that. But if one want the default case to be not to 
look up SRV records, it'd be easy to add an additional flag check to 
the initial if case (line 1552 in the file, line 439 in the patch). 
This would be a new flag not listed in the getaddrinfo() RFC in that 
case.

I'd question if it's required. DNS SRV records would not be more 
vulnerable than the A/AAAA records themselves, but I guess a SHOULD NOT 
should be honored. Another reason could be to limit the number of DNS 
lookups.
-- 
Pelle Johansson
<morth@morth.org>