Operational Considerations for use of DNS in IoT devices

Document Type Replaced Internet-Draft (individual)
Author Michael Richardson 
Last updated 2020-09-22
Replaced by draft-ietf-opsawg-mud-iot-dns-considerations
Stream (None)
Intended RFC status (None)
Expired & archived
pdf htmlized bibtex
Additional Resources
- GitHub Repository
- Mailing List
- Mailing List
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Replaced by draft-ietf-opsawg-mud-iot-dns-considerations
Telechat date
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at


This document details concerns about how Internet of Things devices use IP addresses and DNS names. The issue becomes acute as network operators begin deploying RFC8520 Manufacturer Usage Description (MUD) definitions to control device access. This document explains the problem through a series of examples of what can go wrong, and then provides some advice on how a device manufacturer can best make deal with these issues. The recommendations have an impact upon device and network protocol design. {RFC-EDITOR, please remove. Markdown and issue tracker for this document is at https://github.com/mcr/iot-mud-dns-considerations.git }


Michael Richardson (mcr+ietf@sandelman.ca)

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)