DNS Privacy, Authorization, Special Uses, Encoding, Characters, Matching, and Root Structure: Time for Another Look?
RFC 8324, “DNS Privacy, Authorization, Special Uses, Encoding, Characters, Matching, and Root Structure: Time for Another Look?”, is an Informational document published in February 2018 by J. Klensin. The canonical text is published by the RFC Editor.
Abstract
The basic design of the Domain Name System was completed almost 30 years ago. The last half of that period has been characterized by significant changes in requirements and expectations, some of which either require changes to how the DNS is used or can be accommodated only poorly or not at all. This document asks the question of whether it is time to either redesign and replace the DNS to match contemporary requirements and expectations (rather than continuing to try to design and implement incremental patches that are not fully satisfactory) or draw some clear lines about functionality that is not really needed or that should be performed in some other way.
What “Informational” means
Published for the general information of the community. It does not define an IETF standard and carries no standards-track status.
The canonical text of RFC 8324 is hosted at rfc-editor.org. Available in TXT,HTML.
- RFC 8323 CoAP over TCP, TLS, and WebSockets
- RFC 8325 Mapping Diffserv to IEEE 802.11
- RFC 8322 Resource-Oriented Lightweight Information Exchange
- RFC 8326 Graceful BGP Session Shutdown
- RFC 8321 Alternate-Marking Method for Passive and Hybrid Performance Monitoring
- RFC 8327 Mitigating the Negative Impact of Maintenance through BGP Session Culling
- RFC 8320 LDP Extensions to Support Maximally Redundant Trees
- RFC 8328 Policy-Based Management Framework for the Simplified Use of Policy Abstractions