DNS Resolver Information Self-publication
draft-ietf-dnsop-resolver-information-01
Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
---|---|---|---|
Authors | Puneet Sood , Roy Arends , Paul E. Hoffman | ||
Last updated | 2021-07-09 (Latest revision 2020-02-11) | ||
Replaces | draft-sah-resolver-information, draft-sah-resinfo-doh | ||
RFC stream | (None) | ||
Intended RFC status | (None) | ||
Formats | |||
Stream | Stream state | (No stream defined) | |
Consensus boilerplate | Unknown | ||
RFC Editor Note | (None) | ||
IESG | IESG state | Expired | |
Telechat date | (None) | ||
Responsible AD | (None) | ||
Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
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. There is a GitHub repo for this draft where pull requests can be issued: https://github.com/DNSOP/draft-ietf-dnsop-resolver- information However, starting issues on the WG mailing list is preferred.
Authors
Puneet Sood
Roy Arends
Paul E. Hoffman
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)