| CARVIEW |
Select Language
HTTP/2 200
date: Mon, 14 Jul 2025 12:48:33 GMT
content-type: text/html; charset=UTF-8
content-encoding: gzip
vary: Accept-Encoding
strict-transport-security: max-age=31536000; includeSubDomains
x-frame-options: SAMEORIGIN
x-xss-protection: 1; mode=block
x-content-type-options: nosniff
cf-cache-status: DYNAMIC
server: cloudflare
cf-ray: 95f1228b9977b080-BLR
alt-svc: h3=":443"; ma=86400
Information on RFC 5966 » RFC Editor
Search RFCs
RFC 5966
DNS Transport over TCP - Implementation Requirements, August 2010
- File formats:
- Status:
- PROPOSED STANDARD
- Obsoleted by:
- RFC 7766
- Updates:
- RFC 1035, RFC 1123
- Author:
- R. Bellis
- Stream:
- IETF
- Source:
- dnsext (int)
Cite this RFC: TXT | XML | BibTeX
DOI: https://doi.org/10.17487/RFC5966
Discuss this RFC: Send questions or comments to the mailing list dnsext@ietf.org
Other actions: Submit Errata | Find IPR Disclosures from the IETF | View History of RFC 5966
Abstract
This document updates the requirements for the support of TCP as a transport protocol for DNS implementations. [STANDARDS-TRACK]
For the definition of Status, see RFC 2026.
For the definition of Stream, see RFC 8729.
IAB • IANA • IETF • IRTF • ISE • ISOC • IETF Trust
Reports • Privacy Statement • Site Map • Contact Us