Search RFCs

RFC Editor

File formats:

Also available:XML file for editing

 

Status:

PROPOSED STANDARD

Updates:

RFC 1995,RFC 5936,RFC 7766

Authors:

W. Toorop
S. Dickinson
S. Sahib
P. Aras
A. Mankin

Stream:

IETF

Source:

dprive (int)

Cite this RFC:TXT  | XML  |  BibTeX

DOI:  https://doi.org/10.17487/RFC9103

Discuss this RFC: Send questions or comments to the mailing listdns-privacy@ietf.org

Other actions:Submit Errata  | Find IPR Disclosures from the IETF  | View History of RFC 9103

Abstract

DNS zone transfers are transmitted in cleartext, which givesattackers the opportunity to collect the content of a zone byeavesdropping on network connections. The DNS Transaction Signature(TSIG) mechanism is specified to restrict direct zone transfer toauthorized clients only, but it does not add confidentiality. Thisdocument specifies the use of TLS, rather than cleartext, to preventzone content collection via passive monitoring of zone transfers: XFRover TLS (XoT). Additionally, this specification updates RFC 1995 andRFC 5936 with respect to efficient use of TCP connections and RFC7766 with respect to the recommended number of connections between aclient and server for each transport.

For the definition ofStatus,seeRFC 2026.

For the definition ofStream, seeRFC 8729.