DNS Transport over TCP - Operational Requirements
draft-kristoff-dnsop-dns-tcp-requirements-02
Document | Type |
Replaced Internet-Draft
(dnsop WG)
Expired & archived
|
|
---|---|---|---|
Author | John Kristoff | ||
Last updated | 2017-05-26 (Latest revision 2017-03-13) | ||
Replaced by | draft-ietf-dnsop-dns-tcp-requirements | ||
RFC stream | Internet Engineering Task Force (IETF) | ||
Intended RFC status | (None) | ||
Formats | |||
Additional resources | Mailing list discussion | ||
Stream | WG state | Adopted by a WG | |
Document shepherd | (None) | ||
IESG | IESG state | Replaced by draft-ietf-dnsop-dns-tcp-requirements | |
Consensus boilerplate | Unknown | ||
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 upheld.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)