Hi Ranga,
On 10/12/17 4:16 AM, M. Ranganathan wrote: > Hello, > > I am reading through previous discussion on these topics and am still > not quite "getting it". So I request some explanation from the > authors. My understanding is as follows: > > controllers : this is a place holder for things like DNS and DHCP > where the address of the server is not known a-priori. > > my-controller - has me quite confused. Here's the text from the > latest draft: > > "my-controller: Devices associated with the MUD URL of a device that > the administrator admits." > > So my understanding on this is it allows the manufacturer to supply > access control rules which reference devices with the SAME MUD URL. > So you can, for example say how peer devices from this manufacturer can > interact. (?) The way I like to look at it is this: Peer devices = "manufacturer" or "same-manufacturer", and it is the manufacturer of the device that specifies class admittance by default. More intended as many-to-many. "controller" and "my-controller" are more focused on a one-to-many relationship where class admittance is handled by the administrator. Does that help? Eliot
signature.asc
Description: OpenPGP digital signature
_______________________________________________ OPSAWG mailing list OPSAWG@ietf.org https://www.ietf.org/mailman/listinfo/opsawg
