On Mon, Aug 19, 2019 at 3:28 PM <[email protected]> wrote: > > A New Internet-Draft is available from the on-line Internet-Drafts > directories. > This draft is a work item of the Domain Name System Operations WG of the > IETF. > > Title : DNS Resolver Information Self-publication > Authors : Puneet Sood > Roy Arends > Paul Hoffman > Filename : draft-ietf-dnsop-resolver-information-00.txt > Pages : 9 > Date : 2019-08-19 > > Abstract: > This document describes methods for DNS resolvers to self-publish > information about themselves, such as whether they perform DNSSEC > validation or are available over transports other than what is > defined in RFC 1035. The information is returned as a JSON object. > The names in this object are defined in an IANA registry that allows > for light-weight registration. Applications and operating systems > can use the methods defined here to get the information from > resolvers in order to make choices about how to send future queries > to those resolvers. > > > The IETF datatracker status page for this draft is: > https://datatracker.ietf.org/doc/draft-ietf-dnsop-resolver-information/ > > There are also htmlized versions available at: > https://tools.ietf.org/html/draft-ietf-dnsop-resolver-information-00 > > https://datatracker.ietf.org/doc/html/draft-ietf-dnsop-resolver-information-00
Minor confusion? Section 2 Retrieving Resolver Information by DNS "they only need code to handle the RESINFO RRtype that is not in" "not" seems wrong here. They only need to handle the specified reverse IP, and everything else will be NXDOMAIN or NODATA by default. -- Bob Harold
_______________________________________________ DNSOP mailing list [email protected] https://www.ietf.org/mailman/listinfo/dnsop
