Upper limit values for DNS
draft-fujiwara-dnsop-dns-upper-limit-values-05
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Kazunori Fujiwara , Yorgos Thessalonikefs | ||
| Last updated | 2026-08-13 (Latest revision 2026-02-09) | ||
| 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
DNS was designed to have as few hard upper limits as possible to allow for future extensibility. However, the lack of a clear upper limit leads to vulnerabilities, and several attack methods have been reported. This document collects upper limit values implemented by DNS software to avoid vulnerabilities.
Authors
Kazunori Fujiwara
Yorgos Thessalonikefs
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)