On Thu, Oct 26, 2017 at 1:14 PM, Eliot Lear <l...@cisco.com> wrote:
> The acl name comes directly from draft-ietf-netmod-acl. However, if it is
> not clear, the scope is intended to be solely within a MUD file itself. I
> can add words to that effect as part of LC if nobody objects.
>
> Eliot
>
Hi Eliot:
I had mean to suggest the following change:
leaf acl-name {
type leafref {
path "/acl:access-lists/acl:acl/acl:acl-name";
}
description
"The name of the ACL for this entry.The name is
scoped ONLY to the MUD file, and may not be unique
in any other circumstance.";
}
leaf acl-type {
type identityref {
base acl:acl-base;
}
description
"The type of the ACL for this entry. ";
}
However, I have a suggested change to the naming scheme :
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?
Thanks,
Ranga.
> On 10/26/17 7:12 PM, M. Ranganathan wrote:
>
> leaf acl-name {
> type leafref {
> path "/acl:access-lists/acl:acl/acl:acl-name";
> }
> description
> "The name of the ACL for this entry.";
> }
> leaf acl-type {
> type identityref {
> base acl:acl-base;
> }
> description
> "The type of the ACL for this entry. The name is
> scoped ONLY to the MUD file, and may not be unique
> in any other circumstance.";
> }
>
>
>
>
>
>
> This is a nit (perhaps has already been reported):
>
> Does the description comment on scope belong with the acl-name node?
>
> Thanks
>
> --
> M. Ranganathan
>
>
> _______________________________________________
> OPSAWG mailing listOPSAWG@ietf.orghttps://www.ietf.org/mailman/listinfo/opsawg
>
>
>
--
M. Ranganathan
_______________________________________________
OPSAWG mailing list
OPSAWG@ietf.org
https://www.ietf.org/mailman/listinfo/opsawg
