Hi Martin, Trimming:
On 8/28/17 10:52 AM, Martin Bjorklund wrote: >> ONLY. > Ok. The text says "a small number ... including ...". I suggest this > is clarified. So clarified. > Ok, but --ietf does not check indentation etc. Ok. >> Yes. This has been the subject of considerable discussion. I >> propose to modify the model to include an rc:yang-data >> statement, > Ok, but note that this makes your usage of access-lists problematic - > if you define "rc:yang-data mud", you cannot have a file with > "access-lists" within the "mud" container. I don't know how to solve > this... That would be quite bad. Then in the alternative, if we go without rc:yang-data, could we then simply leave the mud container as a presence container? Given the presence of the MUD-URL this has roughly the concept intended with presence as I understand it. > >> For what purpose? > So that the MUD controller knows how to parse the mud file? OTOH, if > it turns out to be necessary, you can add it as a mandatory leaf in a > future model. ok. Let's have a think about that one. If the file is aiming towards self-describing, then this is a good add. Eliot
signature.asc
Description: OpenPGP digital signature
_______________________________________________ OPSAWG mailing list [email protected] https://www.ietf.org/mailman/listinfo/opsawg
