-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 2/26/18 03:15, Eliot Lear wrote: > > > On 26.02.18 06:55, Mahesh Jethanandani wrote: >>> >>>> >>>> >>>> PS: And this is not a shepherd directive, but I found the >>>> whole "source-port-range-or-operator" syntax clumsy. I'm >>>> surprised it didn't look something like: >>>> >>>> OLD <source-port-range-or-operator> <port-range-or-operator> >>>> <range> <lower-port>16384</lower-port> >>>> <upper-port>65535</upper-port> </range> >>>> </port-range-or-operator> </source-port-range-or-operator> >>>> >>>> <source-port-range-or-operator> <port-range-or-operator> >>>> <operator> <operator>eq</operator> <port>21</port> >>>> </operator> </port-range-or-operator> >>>> </source-port-range-or-operator> >>>> >>>> NEW >>>> >>>> <source-port> <range> <lower>16384</lower> >>>> <upper>65535</upper> </range> </source-port> >>>> >>>> <source-port> <operator> <operator>eq</operator> >>>> <port>21</port> </operator> </source-port> >>>> >>> >>> Did you try making the change in the model to see if it work? >>> It will complain that <range> is already used within the >>> container and that it cannot be repeated (for >>> destination-port). >>> >>> <KENT> No, I did not, nor do I intend to get that deep into it. >>> But I recall that Kristian made the same comment before, and >>> was making pull requests before, so maybe he can suggest >>> something? >> >> Kristian’s suggestion requires changing the module. It is not an >> editorial change. And that change will have an impact on the MUD >> draft, which has been sent for publication. >> > > As it happens, we found a bug in our augment statements, and so we > will need to rev one more time. If the change can be made quickly, > I can live with it.
- From an opsawg chair perspective, I am fine with this. Warren may want to weigh in from the AD perspective. Joe -----BEGIN PGP SIGNATURE----- iF0EARECAB0WIQTMiWQHc8wChijkr7lvaI+K/hTPhwUCWpSGsQAKCRBvaI+K/hTP h/NaAKCEhW2WJnfscTPSTlvbDyzsyWfPiACghHZgtMO0sCl49m3NWnLnt126Z1c= =EEbu -----END PGP SIGNATURE----- _______________________________________________ netmod mailing list netmod@ietf.org https://www.ietf.org/mailman/listinfo/netmod
