Controller Identification Extension for MUD
draft-lear-opsawg-mud-controller-candidates-00
Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
---|---|---|---|
Author | Eliot Lear | ||
Last updated | 2020-01-02 (Latest revision 2019-07-01) | ||
RFC stream | (None) | ||
Intended RFC status | (None) | ||
Formats | |||
Yang Validation | ☯ 0 errors, 0 warnings | ||
Additional resources |
Yang catalog entry for ietf-mud-controller-candidate@2019-06-20.yang
Yang impact analysis for draft-lear-opsawg-mud-controller-candidates |
||
Stream | Stream state | (No stream defined) | |
Consensus boilerplate | Unknown | ||
RFC Editor Note | (None) | ||
IESG | IESG state | Expired | |
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
Manufacturer Usage Descriptions (MUD) are a means by which devices can establish expectations about how they are intended to behave, and how the network should treat them. This extension provides a means for a MUD controller to identify itself through its own MUD file.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)