Fragmentation Avoidance in DNS
draft-fujiwara-dnsop-avoid-fragmentation-03
| Document | Type | Replaced Internet-Draft (dnsop WG) | |
|---|---|---|---|
| Last updated | 2020-04-27 (latest revision 2020-04-12) | ||
| Replaced by | draft-ietf-dnsop-avoid-fragmentation | ||
| Stream | IETF | ||
| Intended RFC status | Best Current Practice | ||
| Formats |
Expired & archived
pdf
htmlized (tools)
htmlized
bibtex
|
||
| Stream | WG state | Adopted by a WG | |
| Document shepherd | No shepherd assigned | ||
| IESG | IESG state | Replaced by draft-ietf-dnsop-avoid-fragmentation | |
| Consensus Boilerplate | Yes | ||
| Telechat date | |||
| Responsible AD | (None) | ||
| Send notices to | (None) | ||
https://www.ietf.org/archive/id/draft-fujiwara-dnsop-avoid-fragmentation-03.txt
Abstract
Path MTU discovery remains widely undeployed due to security issues, and IP fragmentation has exposed weaknesses in application protocols. Currently, DNS is known to be the largest user of IP fragmentation. It is possible to avoid IP fragmentation in DNS by limiting response size where possible, and signaling the need to upgrade from UDP to TCP transport where necessary. This document proposes to avoid IP fragmentation in DNS.
Authors
Kazunori Fujiwara
(fujiwara@jprs.co.jp)
Paul Vixie
(paul@redbarn.org)
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)