Reporting MUD behavior to vendors
draft-lear-opsawg-mud-reporter-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Eliot Lear , Mudumbai Ranganathan | ||
| Last updated | 2020-01-06 (Latest revision 2019-07-05) | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Yang Validation | ☯ 0 errors, 0 warnings | ||
| Additional resources |
Yang catalog entry for ietf-mud-reporter-collector@2019-06-21.yang
Yang catalog entry for ietf-mud-reporter-extension@2019-06-21.yang Yang catalog entry for ietf-mud-reporter@2019-06-21.yang Yang impact analysis for draft-lear-opsawg-mud-reporter |
||
| 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
As with other technology, manufacturers would like to understand how networks implementing MUD are treating devices that are providing MUD URLs and MUD files. This memo specifies an extension to MUD that permits certain behaviors to be reported.
Authors
Eliot Lear
Mudumbai Ranganathan
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)