Operational Considerations for use of DNS in IoT devices
draft-ietf-opsawg-mud-iot-dns-considerations-02
| Document | Type |
This is an older version of an Internet-Draft whose latest revision state is "Active".
Expired & archived
|
|
|---|---|---|---|
| Authors | Michael Richardson , Wei Pan | ||
| Last updated | 2022-01-12 (Latest revision 2021-07-11) | ||
| Replaces | draft-richardson-opsawg-mud-iot-dns-considerations | ||
| RFC stream | Internet Engineering Task Force (IETF) | ||
| Formats | |||
| Reviews |
IOTDIR Telechat review
(of
-12)
by Dave Thaler
On the right track
DNSDIR Last Call review
(of
-12)
by Nicolai Leymann
Ready w/issues
GENART Early review
by Paul Kyzivat
On the right track
IOTDIR Early review
by Dave Thaler
On the right track
INTDIR Early review
by David Lamparter
On the right track
|
||
| Additional resources | Mailing list discussion | ||
| Stream | WG state | WG Document | |
| Document shepherd | (None) | ||
| IESG | IESG state | Expired | |
| Consensus boilerplate | Unknown | ||
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
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 }
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)