Reporting Information from DNS Authoritative Servers
draft-pp-dnsop-authinfo-00
|
| Document |
Type |
|
Active Internet-Draft (individual)
|
|
Authors |
|
Paul Hoffman
,
Puneet Sood
|
|
Last updated |
|
2020-09-09
|
|
Stream |
|
(None)
|
|
Intended RFC status |
|
(None)
|
|
Formats |
|
plain text
pdf
htmlized (tools)
htmlized
bibtex
|
| Stream |
Stream state |
|
(No stream defined) |
|
Consensus Boilerplate |
|
Unknown
|
|
RFC Editor Note |
|
(None)
|
| IESG |
IESG state |
|
I-D Exists
|
|
Telechat date |
|
|
|
Responsible AD |
|
(None)
|
|
Send notices to |
|
(None)
|
Network Working Group P. Hoffman
Internet-Draft ICANN
Intended status: Standards Track P. Sood
Expires: March 12, 2021 Google
September 08, 2020
Reporting Information from DNS Authoritative Servers
draft-pp-dnsop-authinfo-00
Abstract
This document defines a new DNS RRtype, AUTHINFO, that is used by
authoritative servers to publish information about themselves. This
information can be useful because a recursive resolver can determine
an authoritative server's capabilities, such as whether an
authoritative server supports the EDNS(0) client subnet extension.
Status of This Memo
This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet-
Drafts is at https://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."
This Internet-Draft will expire on March 12, 2021.
Copyright Notice
Copyright (c) 2020 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents
(https://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of
Hoffman & Sood Expires March 12, 2021 [Page 1]
Internet-Draft DNS AUTHINFO September 2020
the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License.
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
1.1. Definitions . . . . . . . . . . . . . . . . . . . . . . . 2
2. Authoritative Server Information . . . . . . . . . . . . . . 2
3. Contents of the Returned I-JSON Object . . . . . . . . . . . 3
3.1. Example . . . . . . . . . . . . . . . . . . . . . . . . . 4
4. Using AUTHINFO Responses for Detecting Client Subnet Support 4
4.1. Example . . . . . . . . . . . . . . . . . . . . . . . . . 4
5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 4
5.1. AUTHINFO RRtype . . . . . . . . . . . . . . . . . . . . . 4
5.2. Registry for DNS Authoritative Server Information . . . . 5
5.3. Registration for ecs-supported in the IANA DNS
Authoritative Server Information Registry . . . . . . . . 5
6. Security Considerations . . . . . . . . . . . . . . . . . . . 5
7. References . . . . . . . . . . . . . . . . . . . . . . . . . 5
7.1. Normative References . . . . . . . . . . . . . . . . . . 5
7.2. Informative References . . . . . . . . . . . . . . . . . 6
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 6
1. Introduction
It is sometimes useful for a DNS recursive resolver to know the
capabilities of an authoritative server before sending queries.
Because the record with this information can be signed with DNSSEC,
it can be used to help a recursive resolver know whether to expect
particular EDNS(0) [RFC6891] options in responses. Other uses for
the information may be developed in the future.
1.1. Definitions
The term "authoritative server" is defined in [RFC8499].
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
"OPTIONAL" in this document are to be interpreted as described in BCP
14 [RFC2119] [RFC8174] when, and only when, they appear in all
capitals, as shown here.
2. Authoritative Server Information
A recursive resolver that wants to use the DNS to get information
about an authoritative server sends a query of <some_name>/IN/
AUTHINFO to the authoritative server. The name <some_name> is a
placeholder for any zone for which the authoritative server is
Hoffman & Sood Expires March 12, 2021 [Page 2]
Internet-Draft DNS AUTHINFO September 2020
authoritative. For example, if an authoritative server is
authoritative for example.com, the query could be example.com/IN/
Show full document text