On Thu, Oct 26, 2017 at 2:18 PM, Eliot Lear <l...@cisco.com> wrote: > > > On 10/26/17 7:26 PM, M. Ranganathan wrote: > > > I would like to suggest that an ACL name be directly derived from a a MUD URL > instead of scoping it this way (so that it can be specified independently of > the MUD file while achieving the scoping goal you had in mind). > > > That would ease the pain of implementation. > > > Can you make this a requirement? > > > > That's a reference to an object outside of our model. I think I could > write those words, but to be safe, your code should still bind the scoping > to that file. And so I'm not sure of the point. >
I would suggest something a little more drastic - i.e. remove the notion of scoping by file and tie the ACL names to a MUD file using a unique ACL names (that could be derived from the MUD URL for example). The ACLs can be changed independently of the MUD files (except for the ACL names) that way. That would be the utility. > > Eliot > -- M. Ranganathan
_______________________________________________ OPSAWG mailing list OPSAWG@ietf.org https://www.ietf.org/mailman/listinfo/opsawg
