Hi, I will not be there, but yes I think bandwidth is just one of many attributes we can define in MUD profiles, additional feature of MUD would be to identify the IoT device functionality, to say this device has a camera stream available on port YXZ, that alerts can be seen at this URL, that the control panel can be access at this URL, and more. I have many examples at the end of this presentation. https://github.com/CIRALabs/Secure-IoT-Home-Gateway/blob/master/CIRA%20Labs%20-%20Secure%20Home%20Gateway%20Project%202018-09.pdf
Jacques From: OPSAWG <[email protected]> On Behalf Of Eliot Lear Sent: October 20, 2018 3:50 PM To: [email protected] Subject: [OPSAWG] Fwd: New Version Notification for draft-lear-opsawg-mud-bw-profile-00.txt This is a little ditty that Jerome Henry and I have started in response to some requests that we have some ability to profile bandwidth usage in a MUD file. This is a very brief draft. I would appreciate if I could have 10 minutes to talk about it. There are a few questions that I would like to ask the room. Specifically: 1. In profiling bandwidth, would you like in the model (a) an aggregate statement of how bandwidth is supposed to be used, (b) a fine grain view by port/service, or (c) both? 2. Does the draft have the right units in there? Right now I list both packets per second and bits per second with a configurable time period. 3. Is this something you would be interested in reviewing, pursuing, editing, etc.'ing? Thanks! Eliot
_______________________________________________ OPSAWG mailing list [email protected] https://www.ietf.org/mailman/listinfo/opsawg
