MUD processing and extensions for Secure Home Gateway Project
draft-richardson-opsawg-securehomegateway-mud-01
| Document | Type | Expired Internet-Draft (individual) | |||
|---|---|---|---|---|---|
| Last updated | 2019-09-12 (latest revision 2019-03-11) | ||||
| Stream | (None) | ||||
| Intended RFC status | (None) | ||||
| Formats |
Expired & archived
pdf
htmlized
bibtex
|
||||
| Additional URLs |
|
||||
| Stream | Stream state | (No stream defined) | |||
| Consensus Boilerplate | Unknown | ||||
| RFC Editor Note | (None) | ||||
| IESG | IESG state | Expired | |||
| Telechat date | |||||
| Responsible AD | (None) | ||||
| Send notices to | (None) | ||||
https://www.ietf.org/archive/id/draft-richardson-opsawg-securehomegateway-mud-01.txt
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
(mcr+ietf@sandelman.ca)
Jacques Latour
(jacques.latour@cira.ca)
Faud Khan
(faud.khan@twelvedot.com)
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)