DNS Transport over TCP - Operational Requirements
draft-kristoff-dnsop-dns-tcp-requirements-01
The information below is for an old version of the document.
| Document | Type |
This is an older version of an Internet-Draft whose latest revision state is "Replaced".
Expired & archived
|
|
|---|---|---|---|
| Author | John Kristoff | ||
| Last updated | 2017-03-02 (Latest revision 2016-08-29) | ||
| Replaced by | draft-ietf-dnsop-dns-tcp-requirements, RFC 9210 | ||
| RFC stream | (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
This document encourages the practice of permitting DNS messages to be carried over TCP on the Internet. It also describes some of the consequences of this behavior and the potential operational issues that can arise when this best common practice is not applied.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)