From: [email protected] <[email protected]> Sent: 15 October 2021 12:24
Re-, Please see inline. Cheers, Med > -----Message d'origine----- > De : tom petch <[email protected]> > Envoyé : vendredi 15 octobre 2021 13:12 > > From: [email protected] <[email protected]> > Sent: 15 October 2021 11:58 > > Hi Rob, Tom, all, > > The trees are different because we are not importing the acl module, but > are reusing "packet-fields" from RFC8519 to define the classification > rules. > > Please note that trees in vpn-common are printed with "--tree-print- > groupings". > > <tp> > That feature I do not understand. I agree that you are reusing packet- > fields from RFC8519 but that module has 'grouping port-range-or-operator' > with no mention AFAICT of a 'source' or a 'destination' in the identifier. > Did you edit all those in as well? [Med] Here is an excerpt of the "ports" grouping in vpn-common: == choice source-port { description "Choice of specifying the source port or referring to a group of source port numbers."; container source-port-range-or-operator { description "Source port definition."; uses packet-fields:port-range-or-operator; } } == which will be pronted as: 1: grouping ports 2: +-- (source-port)? 3: | +--:(source-port-range-or-operator) 4: | +-- source-port-range-or-operator 5: | +-- (port-range-or-operator)? 6: | +--:(range) 7: | | +-- lower-port inet:port-number 8: | | +-- upper-port inet:port-number 9: | +--:(operator) 10: | +-- operator? operator 11: | +-- port inet:port-number The names in lines 1-4 are those in the common module, 5-11 are those in packet-fields. <tp2> Ah yes, I said that I did not understand Tree Diagrams:-(. The name printed is that of the container above the 'uses'. I did spot the misalignment first and then tried to work out the underlying YANG and failed, hence my comment! Tom Petch _______________________________________________ netmod mailing list [email protected] https://www.ietf.org/mailman/listinfo/netmod
