On 7/28/15 4:35 PM, Viktor Dukhovni wrote: > This is based in part on the architectural assumption that in many > cases the right way to process it on the client side will be a > hand-off a local DNS service.
I think the primary concern about that is the possibility of introducing additional latency, given that we're trying to minimize the DANE performance hit on clients like browsers, who tend to be extremely sensitive to delay. We probably need clearer discussion about what we're trying to optimize for. But in either case, whether we're using a resolver in a DNS library or handing it off to a service, encoding the records in DNS wire format is going to be easiest for implementers. Several people have talked about writing their own bare-bones resolver that does not use an entire DNS library but I don't have any sense that that's going to be a common case. It's worth talking to people working with highly constrained devices in any event. Thanks, Melinda _______________________________________________ dane mailing list [email protected] https://www.ietf.org/mailman/listinfo/dane
