DNS Referral Response Size Issues
draft-ietf-dnsop-respsize-13
| Document | Type |
This is an older version of an Internet-Draft whose latest revision state is "Expired".
Expired & archived
|
|
|---|---|---|---|
| Authors | Paul A. Vixie , Akira Kato | ||
| Last updated | 2012-03-26 (Latest revision 2011-09-13) | ||
| RFC stream | Internet Engineering Task Force (IETF) | ||
| Formats | |||
| Additional resources | Mailing list discussion | ||
| Stream | WG state | WG Document | |
| Document shepherd | Peter Koch | ||
| IESG | IESG state | Expired (IESG: Dead) | |
| Consensus boilerplate | Unknown | ||
| Telechat date | (None) | ||
| Responsible AD | Ron Bonica | ||
| IESG note | ** No value found for 'doc.notedoc.note' ** | ||
| Send notices to | <sra+dnsop@hactrn.net>,<dmm@1-4-5.net> |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
With a mandated default minimum maximum UDP message size of 512 octets, the DNS protocol presents some special problems for zones wishing to expose a moderate or high number of authority servers (NS RRs). This document explains the operational issues caused by, or related to this response size limit, and suggests ways to optimize the use of this limited space. Guidance is offered to DNS server implementors and to DNS zone operators.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)