MUD processing and extensions for Secure Home Gateway Project
draft-richardson-opsawg-securehomegateway-mud-01
| Document | Type |
This is an older version of an Internet-Draft whose latest revision state is "Replaced".
Expired & archived
|
|
|---|---|---|---|
| Authors | Michael Richardson , Jacques Latour , Faud Khan | ||
| Last updated | 2019-09-12 (Latest revision 2019-03-11) | ||
| Replaced by | draft-richardson-mud-qrcode, RFC 9238 | ||
| RFC stream | (None) | ||
| Formats | |||
| Additional resources | |||
| 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
This document details the mechanism used by the CIRA Secure Home Gateway and CIRA MUD integration server to return MUD artifacts to participating gateway systems. The work in [I-D.ietf-opsawg-mud] creates a relationship between a device's manufacturer and a border gateway that may need to enforce policy. This document ads an additional relationship to a service provider, trusted by the border gateway to enhance or modify the stated security policy.
Authors
Michael Richardson
Jacques Latour
Faud Khan
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)