Glue In DNS Referral Responses Is Not Optional
draft-ietf-dnsop-glue-is-not-optional-00
The information below is for an old version of the document.
| Document | Type | Expired Internet-Draft (dnsop WG) | |
|---|---|---|---|
| Author | Mark P. Andrews | ||
| Last updated | 2020-12-05 (Latest revision 2020-06-03) | ||
| Replaces | draft-andrews-dnsop-glue-is-not-optional | ||
| Stream | Internet Engineering Task Force (IETF) | ||
| Formats |
Expired & archived
plain text
xml
htmlized
pdfized
bibtex
|
||
| Stream | WG state | WG Document | |
| Document shepherd | (None) | ||
| IESG | IESG state | Expired | |
| Consensus boilerplate | Unknown | ||
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of
the expired Internet-Draft can be found at:
https://www.ietf.org/archive/id/draft-ietf-dnsop-glue-is-not-optional-00.txt
https://www.ietf.org/archive/id/draft-ietf-dnsop-glue-is-not-optional-00.txt
Abstract
The DNS uses glue records to allow iterative clients to find the addresses of nameservers that live within the delegated zone. Glue records are expected to be returned as part of a referral and if they cannot be fitted into the UDP response, TC=1 MUST be set to inform the client that the response is incomplete and that TCP SHOULD be used to retrieve the full response.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)