Returning additional answers in DNS responses
draft-fujiwara-dnsop-additional-answers-01
| Document | Type | Expired Internet-Draft (individual) | |
|---|---|---|---|
| Author | Kazunori Fujiwara | ||
| Last updated | 2018-07-16 (latest revision 2018-01-10) | ||
| Stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats |
Expired & archived
pdf
htmlized (tools)
htmlized
bibtex
|
||
| Stream | Stream state | (No stream defined) | |
| Consensus Boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | |||
| Responsible AD | (None) | ||
| Send notices to | (None) | ||
https://www.ietf.org/archive/id/draft-fujiwara-dnsop-additional-answers-01.txt
Abstract
This document proposes to document the ability to provide multiple answers in single DNS response. For example, authoritative servers may add a NSEC resource record or A/AAAA resource records of the query name. This is especially useful as, in many cases, the entity making the request has no a priori knowledge of what other questions it will need to ask. It is already possible (an authoritative server MAY already sends what it wants in the additional section). This document does not propose any protocol changes, just explanations of an already acceptable practice.
Authors
Kazunori Fujiwara (fujiwara@jprs.co.jp)
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)