RFC 5966: DNS Transport over TCP - Implementation Requirements
This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 7766.
Current version: RFC 7766 — DNS Transport over TCP - Implementation Requirements
In plain English — editorial summary, not part of the RFC
This document updates the requirements for the support of TCP as a transport protocol for DNS implementations. [STANDARDS-TRACK]
Document record
- Document ID
- RFC5966
- Published
- August 2010
- Authors
- R. Bellis
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- int
- Pages
- 7
- Also known as
- —
- Obsoleted by:
- RFC 7766
Topics
Referenced by
One later RFC formally updates or obsoletes part of this document.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 7828The edns-tcp-keepalive EDNS0 OptionCurrent
April 2016
- RFC 6097Local Mobility Anchor (LMA) Discovery for Proxy Mobile IPv6Current
February 2011
- RFC 5625DNS Proxy Implementation GuidelinesCurrent
August 2009
- RFC 6418Multiple Interfaces and Provisioning Domains Problem StatementCurrent
November 2011
- RFC 6604xNAME RCODE and Status Bits ClarificationCurrent
April 2012
- RFC 5205Host Identity Protocol (HIP) Domain Name System (DNS) ExtensionsObsoleted
April 2008
- RFC 6731Improved Recursive DNS Server Selection for Multi-Interfaced NodesCurrent
December 2012
- RFC 6975Signaling Cryptographic Algorithm Understanding in DNS Security Extensions (DNSSEC)Current
July 2013
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?