DNS Transport over TCP - Operational Requirements
draft-kristoff-dnsop-dns-tcp-requirements-02
Document | Type | Replaced Internet-Draft (dnsop WG) | |
---|---|---|---|
Author | John Kristoff | ||
Last updated | 2017-05-26 (latest revision 2017-03-13) | ||
Replaced by | draft-ietf-dnsop-dns-tcp-requirements | ||
Stream | IETF | ||
Intended RFC status | (None) | ||
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-dns-tcp-requirements | |
Consensus Boilerplate | Unknown | ||
Telechat date | |||
Responsible AD | (None) | ||
Send notices to | (None) |
This Internet-Draft is no longer active. A copy of
the expired Internet-Draft can be found at
https://www.ietf.org/archive/id/draft-kristoff-dnsop-dns-tcp-requirements-02.txt
https://www.ietf.org/archive/id/draft-kristoff-dnsop-dns-tcp-requirements-02.txt
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
John Kristoff (jtk@depaul.edu)
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)