UDP payload size for DNS messages
draft-madi-dnsop-udp4dns-00
Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
---|---|---|---|
Authors | Di Ma , Linjian Song | ||
Last updated | 2016-02-29 (Latest revision 2015-08-28) | ||
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
The classic 512-bytes UDP payload for transporting DNS messages is an embedded dependence on IPv4. As the Internet infrastructure is evolving to IPv6, the very constraint stemming from IPv4 can be removed by the virtue of that IPv6 mandates a MTU of 1280 bytes. This document specifies a new minimum size of UDP packet to carry DNS message, making DNS implementations going forward more adaptive to both applications based on the Internet and infrastructures supporting the Internet.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)