Javascript disabled? Like other modern websites, the IETF Datatracker relies on Javascript. Please enable Javascript for full functionality.

DNS Transport over TCP - Operational Requirements
RFC 9210 also known as BCP 235

Revision differences

From revision

To revision

Diff format

Document history

Date	By	Action
2023-12-12	(System)	Imported membership of rfc9210 in bcp235 via sync to the rfc-index
2023-12-12	(System)	No history of BCP235 is currently available in the datatracker before this point
2022-12-03	Gunter Van de Velde	Closed request for Last Call review by OPSDIR with state 'Overtaken by Events'
2022-03-22	(System)	Received changes through RFC Editor sync (created alias RFC 9210, changed abstract to 'This document updates RFCs 1123 and 1536. This document requires the … Received changes through RFC Editor sync (created alias RFC 9210, changed abstract to 'This document updates RFCs 1123 and 1536. This document requires the operational practice of permitting DNS messages to be carried over TCP on the Internet as a Best Current Practice. This operational requirement is aligned with the implementation requirements in RFC 7766. The use of TCP includes both DNS over unencrypted TCP as well as over an encrypted TLS session. The document also considers the consequences of this form of DNS communication and the potential operational issues that can arise when this Best Current Practice is not upheld.', changed pages to 29, changed standardization level to Best Current Practice, changed state to RFC, added RFC published event at 2022-03-22, changed IESG state to RFC Published, created updates relation between draft-ietf-dnsop-dns-tcp-requirements and RFC 1123, created updates relation between draft-ietf-dnsop-dns-tcp-requirements and RFC 1536, created alias BCP 235)
2022-03-22	(System)	RFC published