> On 11 Jul 2018, at 1:16 pm, John R Levine <jo...@taugh.com> wrote:
>
>> On Tue, Jul 10, 2018 at 11:08:37PM -0400, John Levine wrote:
>>> There's over 6000 service names defined for SRV. That's a lot of rrtypes.
>>
>> But HTTP/HTTPS is the one we have by far the most problems with.
>
> True, and there have been some proposals for DNS records to return http
> parameters.
>
> It's always been my impression that the http crowd believe that the
> overhead of a two DNS lookups is too slow, for some meaning of too slow.
Which is predicated on the recursive server not filling in the additional
section.
Recursive servers can and do fill the additional section with SRV (starting
with NAPTR
records) then add A, AAAA and TLSA records. They can lookup missing record
before
returning the SRV or NAPTR records (there is code to do that for SRV). Its
easy to
do the same thing for other record types.
> Regards,
> John Levine, jo...@taugh.com, Taughannock Networks, Trumansburg NY
> Please consider the environment before reading this e-mail. https://jl.ly
>
> _______________________________________________
> DNSOP mailing list
> DNSOP@ietf.org
> https://www.ietf.org/mailman/listinfo/dnsop
--
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742 INTERNET: ma...@isc.org
_______________________________________________
DNSOP mailing list
DNSOP@ietf.org
https://www.ietf.org/mailman/listinfo/dnsop
