3 namespace "urn:opendaylight:params:xml:ns:yang:vpp:acl";
6 revision "2016-12-14" {
8 "Initial revision of vpp-acl model.";
11 import ietf-access-control-list {
15 import vpp-classifier {
16 prefix "vpp-classifier";
19 typedef interface-mode {
25 grouping acl-base-attributes {
27 "Defines references to classify tables.
28 At least one table reference should be specified.";
31 type vpp-classifier:classify-table-ref;
38 type vpp-classifier:classify-table-ref;
45 type vpp-classifier:classify-table-ref;
52 grouping ietf-acl-base-attributes {
54 "Provides limited support for ietf-acl model.";
56 container access-lists {
58 "Defines references to ietf-acl lists. Before assignment to interface,
59 ACL lists are merged into 3 type of acls (l2, ip4 and ip6) that are supported by vpp.
60 Then 3 corresponding chains of tables and sessions are created and assigned to the interface
61 as l2, ip4 and ip6 classify table chains.
62 User ordering is preserved in each group separately.
64 Assignment update/delete removes all created tables and sessions and repeats process described above.
65 Update/delete of ACL lists referenced here is not permitted (assignment needs to be removed first).
67 Read is supported only for acls that were created and assigned by Honeycomb agent
68 (corresponding metadata are present).
70 Limitations (due to vpp limitations):
71 - egress rules are currently ignored (HONEYCOMB-234)
72 - L4 rules are currently not supported (limited support will by provided by HONEYCOMB-218)
73 - mixing L2/L3/L4 rules is currently not supported (limited support will by provided by HONEYCOMB-233)
74 - L2 only rules on L3 interfaces are not supported (not allowed by vpp,
75 in the future defining L2/L3 pairs should be partially supported)
76 - vlan tags are supported only for sub-interfaces defined as exact-match";
86 type acl:access-control-list-ref;
97 "Default action applied to packet that does not match any of rules defined in assigned ACLs.
98 It is translated to single classify table and applied at the end of assigned chains.";
105 "The way ACLs are translated depends on the interface mode.
106 In case of L2 interfaces (bridge/interconnection)
107 classify tables are assigned as l2_table using input_acl_set_interface (ether type matching is automatically
108 added in case of L3 rules).
109 In case of L3 interfaces, classify tables are assigned as ip4/ip6 tables.
111 It is the user responsibility to choose mode that matches target interface.