NETMOD WG M. Jethanandani
Internet-Draft VMware
Intended status: Standards Track S. Agarwal
Expires: May 10, 2019 Cisco Systems, Inc.
L. Huang
D. Blair
November 6, 2018
Network Access Control List (ACL) YANG Data Modeldraft-ietf-netmod-acl-model-21
Abstract
This document defines a data model for Access Control List (ACL). An
ACL is a user-ordered set of rules, used to configure the forwarding
behavior in device. Each rule is used to find a match on a packet,
and define actions that will be performed on the packet.
Status of This Memo
This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet-
Drafts is at https://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."
This Internet-Draft will expire on May 10, 2019.
Copyright Notice
Copyright (c) 2018 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents
(https://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must
Jethanandani, et al. Expires May 10, 2019 [Page 1]

Internet-Draft ACL YANG model November 2018
o Packet header matches apply to fields visible in the packet such
as address or Class of Service (CoS) or port numbers.
o In case a vendor supports it, metadata matches apply to fields
associated with the packet but not in the packet header such as
input interface or length of the packet as received over the wire.
The actions specify what to do with the packet when the matching
criteria are met. These actions are any operations that would apply
to the packet, such as counting, policing, or simply forwarding. The
list of potential actions is unbounded depending on the capabilities
of the networking devices.
Access Control List is also widely knowns as ACL (pronounce as [ak-uh
l]) or Access List. In this document, Access Control List, ACL and
Access List are used interchangeably.
The matching of filters and actions in an ACE/ACL are triggered only
after the application/attachment of the ACL to an interface, VRF,
vty/tty session, QoS policy, or routing protocols, amongst various
other configuration attachment points. Once attached, it is used for
filtering traffic using the match criteria in the ACEs and taking
appropriate action(s) that have been configured against that ACE. In
order to apply an ACL to any attachment point other than an
interface, vendors would have to augment the ACL YANG model.
Editorial Note (To be removed by RFC Editor)
This draft contains many placeholder values that need to be replaced
with finalized values at the time of publication. This note
summarizes all of the substitutions that are needed. Please note
that no other RFC Editor instructions are specified anywhere else in
this document.
Artwork in this document contains shorthand references to drafts in
progress. Please apply the following replacements
o "XXXX" --> the assigned RFC value for this draft both in this
draft and in the YANG models under the revision statement.
o Revision date in model, in the format 2018-11-06 needs to get
updated with the date the draft gets approved. The date also
needs to get reflected on the line with <CODE BEGINS>.
Jethanandani, et al. Expires May 10, 2019 [Page 3]

Internet-Draft ACL YANG model November 20181.1. Definitions and Acronyms
ACE: Access Control Entry
ACL: Access Control List
CoS: Class of Service
DSCP: Differentiated Services Code Point
ICMP: Internet Control Message Protocol
IP: Internet Protocol
IPv4: Internet Protocol version 4
IPv6: Internet Protocol version 6
MAC: Media Access Control
PBR: Policy Based Routing
TCP: Transmission Control Protocol
UDP: User Datagram Protocol
1.2. Terminology
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
"OPTIONAL" in this document are to be interpreted as described in BCP14 [RFC2119] [RFC8174] when, and only when, they appear in all
capitals, as shown here.
1.3. Tree Diagram
For a reference to the annotations used in tree diagrams included in
this draft, please see YANG Tree Diagrams [RFC8340].
2. Problem Statement
This document defines a YANG 1.1 [RFC7950] data model for the
configuration of ACLs. The model defines matching rules for commonly
used protocols such as, Ethernet, IPv4, IPv6, TCP, UDP and ICMP. If
more protocols need to be supported in the future, this base model
can be augmented. An example of such an augmentation can be seen in
the Appendix.
Jethanandani, et al. Expires May 10, 2019 [Page 4]

Internet-Draft ACL YANG model November 2018
ACL implementations in every device may vary greatly in terms of the
filter constructs and actions that they support. Therefore, this
draft proposes a model that can be augmented by standard extensions
and vendor proprietary models.
3. Understanding ACL's Filters and Actions
Although different vendors have different ACL data models, there is a
common understanding of what Access Control List (ACL) is. A network
system usually has a list of ACLs, and each ACL contains an ordered
list of rules, also known as Access Control Entries (ACE). Each ACE
has a group of match criteria and a group of actions. The match
criteria allow for definition of contents of the packet headers or
metadata, if supported by the vendor. Packet header matching applies
to fields visible in the packet such as address or CoS or port
numbers. Metadata matching applies to fields associated with the
packet, but not in the packet header, such as input interface, packet
length, or source or destination prefix length. The actions can be
any sort of operation from logging to rate limiting or dropping to
simply forwarding. Actions on the first matching ACE are applied
with no processing of subsequent ACEs.
The model also includes a container to hold overall operational state
for each ACL and operational state for each ACE. One ACL can be
applied to multiple targets within the device, such as interface of a
networking device, applications or features running in the device,
etc. When applied to interfaces of a networked device, distinct ACLs
are defined for the ingress (input) or egress (output) interface.
This draft tries to address the commonalities between all vendors and
create a common model, which can be augmented with proprietary
models. The base model is simple in design, and we hope to achieve
enough flexibility for each vendor to extend the base model.
The use of feature statements in the model allows vendors to
advertise match rules they are capable and willing to support. There
are two sets of feature statements a device needs to advertise. The
first set of feature statements specify the capability of the device.
These include features such as "Device can support matching on
Ethernet headers" or "Device can support matching on IPv4 headers".
The second set of feature statements specify the combinations of
headers the device is willing to support. These include features
such as "Plain IPv6 ACL supported" or "Ethernet, IPv4 and IPv6 ACL
combinations supported".
Jethanandani, et al. Expires May 10, 2019 [Page 5]

Internet-Draft ACL YANG model November 20184. ACL YANG Models4.1. IETF Access Control List module
"ietf-access-control-list" module defines the "acls" container that
has a list of "acl". Each "acl" has information identifying the
access list by a name ("name") and a list ("aces") of rules
associated with the "name". Each of the entries in the list
("aces"), indexed by the string "name", has containers defining
"matches" and "actions".
The model defines several ACL types and actions in the form of
identities and features. Features are used by implementors to select
the ACL types the system can support and identities are used to
validate the types that have been selected. These types are
implicitly inherited by the "ace", thus safeguarding against
misconfiguration of "ace" types in an "acl".
The "matches" define criteria used to identify patterns in "ietf-
packet-fields". The choice statements within the match container
allow for selection of one header within each of "l2", "l3", or "l4"
headers. The "actions" define behavior to undertake once a "match"
has been identified. In addition to permit and deny for actions, a
logging option allows for a match to be logged that can later be used
to determine which rule was matched upon. The model also defines the
ability for ACLs to be attached to a particular interface.
Statistics in the ACL can be collected for an "ace" or for an
"interface". The feature statements defined for statistics can be
used to determine whether statistics are being collected per "ace",
or per "interface".
This module imports definitions from Common YANG Data Types
[RFC6991], and A YANG Data Model for Interface Management [RFC8343].
<CODE BEGINS> file "ietf-access-control-list@2018-11-06.yang"
module ietf-access-control-list {
yang-version 1.1;
namespace "urn:ietf:params:xml:ns:yang:ietf-access-control-list";
prefix acl;
import ietf-yang-types {
prefix yang;
reference
"RFC 6991 - Common YANG Data Types.";
}
Jethanandani, et al. Expires May 10, 2019 [Page 10]

Internet-Draft ACL YANG model November 2018
/*
* Groupings
*/
grouping acl-counters {
description
"Common grouping for ACL counters";
leaf matched-packets {
type yang:counter64;
config false;
description
"Count of the number of packets matching the current ACL
entry.
An implementation should provide this counter on a
per-interface per-ACL-entry basis if possible.
If an implementation only supports ACL counters on a per
entry basis (i.e., not broken out per interface), then the
value should be equal to the aggregate count across all
interfaces.
An implementation that provides counters on a per entry per
interface basis is not required to also provide an aggregate
count, e.g., per entry -- the user is expected to be able
implement the required aggregation if such a count is
needed.";
}
leaf matched-octets {
type yang:counter64;
config false;
description
"Count of the number of octets (bytes) matching the current
ACL entry.
An implementation should provide this counter on a
per-interface per-ACL-entry if possible.
If an implementation only supports ACL counters per entry
(i.e., not broken out per interface), then the value
should be equal to the aggregate count across all interfaces.
An implementation that provides counters per entry per
interface is not required to also provide an aggregate count,
e.g., per entry -- the user is expected to be able implement
the required aggregation if such a count is needed.";
}
Jethanandani, et al. Expires May 10, 2019 [Page 17]

Internet-Draft ACL YANG model November 2018
}
/*
* Configuration and monitoring data nodes
*/
container acls {
description
"This is a top level container for Access Control Lists.
It can have one or more acl nodes.";
list acl {
key "name";
description
"An Access Control List (ACL) is an ordered list of
Access Control Entries (ACE). Each ACE has a
list of match criteria and a list of actions.
Since there are several kinds of Access Control Lists
implemented with different attributes for
different vendors, this model accommodates customizing
Access Control Lists for each kind and, for each vendor.";
leaf name {
type string {
length "1..64";
}
description
"The name of access list. A device MAY restrict the length
and value of this name, possibly space and special
characters are not allowed.";
}
leaf type {
type acl-type;
description
"Type of access control list. Indicates the primary intended
type of match criteria (e.g. ethernet, IPv4, IPv6, mixed,
etc) used in the list instance.";
}
container aces {
description
"The aces container contains one or more ace nodes.";
list ace {
key "name";
ordered-by user;
description
"List of Access Control Entries (ACEs)";
leaf name {
type string {
length "1..64";
}
description
Jethanandani, et al. Expires May 10, 2019 [Page 18]

Internet-Draft ACL YANG model November 2018
"A unique name identifying this Access Control
Entry (ACE).";
}
container matches {
description
"The rules in this set determine what fields will be
matched upon before any action is taken on them.
The rules are selected based on the feature set
defined by the server and the acl-type defined.
If no matches are defined in a particular container,
then any packet will match that container. If no
matches are specified at all in an ACE, then any
packet will match the ACE.";
choice l2 {
container eth {
when "derived-from-or-self(/acls/acl/type, " +
"'acl:eth-acl-type')";
if-feature match-on-eth;
uses pf:acl-eth-header-fields;
description
"Rule set that matches ethernet headers.";
}
description
"Match layer 2 headers, for example ethernet
header fields.";
}
choice l3 {
container ipv4 {
when "derived-from-or-self(/acls/acl/type, " +
"'acl:ipv4-acl-type')";
if-feature match-on-ipv4;
uses pf:acl-ip-header-fields;
uses pf:acl-ipv4-header-fields;
description
"Rule set that matches IPv4 headers.";
}
container ipv6 {
when "derived-from-or-self(/acls/acl/type, " +
"'acl:ipv6-acl-type')";
if-feature match-on-ipv6;
uses pf:acl-ip-header-fields;
uses pf:acl-ipv6-header-fields;
description
"Rule set that matches IPv6 headers.";
Jethanandani, et al. Expires May 10, 2019 [Page 19]

Internet-Draft ACL YANG model November 2018
}
uses acl-counters;
}
}
}
}
list interface {
if-feature interface-attachment;
key "interface-id";
description
"List of interfaces on which ACLs are set";
leaf interface-id {
type if:interface-ref;
description
"Reference to the interface id list key";
}
container ingress {
uses interface-acl;
description
"The ACLs applied to ingress interface";
}
container egress {
uses interface-acl;
description
"The ACLs applied to egress interface";
}
}
}
}
}
<CODE ENDS>
4.2. IETF Packet Fields module
The packet fields module defines the necessary groups for matching on
fields in the packet including ethernet, ipv4, ipv6, and transport
layer fields. The "type" node determines which of these fields get
included for any given ACL with the exception of TCP, UDP and ICMP
header fields. Those fields can be used in conjunction with any of
the above layer 2 or layer 3 fields.
Since the number of match criteria are very large, the base draft
does not include these directly but references them by 'uses'
statement to keep the base module simple. In case more match
Jethanandani, et al. Expires May 10, 2019 [Page 24]

Internet-Draft ACL YANG model November 2018
}
grouping acl-tcp-header-fields {
description
"Collection of TCP header fields that can be used to
setup a match filter.";
leaf sequence-number {
type uint32;
description
"Sequence number that appears in the packet.";
}
leaf acknowledgement-number {
type uint32;
description
"The acknowledgement number that appears in the
packet.";
}
leaf data-offset {
type uint8 {
range "5..15";
}
description
"Specifies the size of the TCP header in 32-bit
words. The minimum size header is 5 words and
the maximum is 15 words thus giving the minimum
size of 20 bytes and maximum of 60 bytes,
allowing for up to 40 bytes of options in the
header.";
}
leaf reserved {
type uint8;
description
"Reserved for future use.";
}
leaf flags {
type bits {
bit cwr {
position 1;
description
"Congestion Window Reduced (CWR) flag is set by
the sending host to indicate that it received
a TCP segment with the ECE flag set and had
responded in congestion control mechanism.";
Jethanandani, et al. Expires May 10, 2019 [Page 33]

Internet-Draft ACL YANG model November 2018
reference
"RFC 3168: The Addition of Explicit Congestion
Notification (ECN) to IP.";
}
bit ece {
position 2;
description
"ECN-Echo has a dual role, depending on the value
of the SYN flag. It indicates:
If the SYN flag is set (1), that the TCP peer is ECN
capable. If the SYN flag is clear (0), that a packet
with Congestion Experienced flag set (ECN=11) in IP
header was received during normal transmission
(added to header by RFC 3168). This serves as an
indication of network congestion (or impending
congestion) to the TCP sender.";
reference
"RFC 3168: The Addition of Explicit Congestion
Notification (ECN) to IP.";
}
bit urg {
position 3;
description
"Indicates that the Urgent pointer field is significant.";
}
bit ack {
position 4;
description
"Indicates that the Acknowledgment field is significant.
All packets after the initial SYN packet sent by the
client should have this flag set.";
}
bit psh {
position 5;
description
"Push function. Asks to push the buffered data to the
receiving application.";
}
bit rst {
position 6;
description
"Reset the connection.";
}
bit syn {
position 7;
description
"Synchronize sequence numbers. Only the first packet
sent from each end should have this flag set. Some
Jethanandani, et al. Expires May 10, 2019 [Page 34]

Internet-Draft ACL YANG model November 2018
other flags and fields change meaning based on this
flag, and some are only valid for when it is set,
and others when it is clear.";
}
bit fin {
position 8;
description
"Last package from sender.";
}
}
description
"Also known as Control Bits. Contains 9 1-bit flags.";
reference
"RFC 793: Transmission Control Protocol (TCP).";
}
leaf window-size {
type uint16;
units "bytes";
description
"The size of the receive window, which specifies
the number of window size units beyond the segment
identified by the sequence number in the acknowledgment
field that the sender of this segment is currently
willing to receive.";
}
leaf urgent-pointer {
type uint16;
description
"This field is an offset from the sequence number
indicating the last urgent data byte.";
}
leaf options {
type binary {
length "1..40";
}
description
"The length of this field is determined by the
data offset field. Options have up to three
fields: Option-Kind (1 byte), Option-Length
(1 byte), Option-Data (variable). The Option-Kind
field indicates the type of option, and is the
only field that is not optional. Depending on
what kind of option we are dealing with,
the next two fields may be set: the Option-Length
field indicates the total length of the option,
Jethanandani, et al. Expires May 10, 2019 [Page 35]

Internet-Draft ACL YANG model November 2018
and the Option-Data field contains the value of
the option, if applicable.";
}
}
grouping acl-udp-header-fields {
description
"Collection of UDP header fields that can be used
to setup a match filter.";
leaf length {
type uint16;
description
"A field that specifies the length in bytes of
the UDP header and UDP data. The minimum
length is 8 bytes because that is the length of
the header. The field size sets a theoretical
limit of 65,535 bytes (8 byte header + 65,527
bytes of data) for a UDP datagram. However the
actual limit for the data length, which is
imposed by the underlying IPv4 protocol, is
65,507 bytes (65,535 minus 8 byte UDP header
minus 20 byte IP header).
In IPv6 jumbograms it is possible to have
UDP packets of size greater than 65,535 bytes.
RFC 2675 specifies that the length field is set
to zero if the length of the UDP header plus
UDP data is greater than 65,535.";
}
}
grouping acl-icmp-header-fields {
description
"Collection of ICMP header fields that can be
used to setup a match filter.";
leaf type {
type uint8;
description
"Also known as Control messages.";
reference
"RFC 792: Internet Control Message Protocol (ICMP),
RFC 4443: Internet Control Message Protocol (ICMPv6)
for Internet Protocol Version 6 (IPv6)
Specifciation.";
}
Jethanandani, et al. Expires May 10, 2019 [Page 36]

Internet-Draft ACL YANG model November 2018
<?xml version="1.0" encoding="UTF-8"?>
<config xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
<acls
xmlns="urn:ietf:params:xml:ns:yang:ietf-access-control-list">
<acl>
<name>sample-ipv4-acl</name>
<type>ipv4-acl-type</type>
<aces>
<ace>
<name>rule1</name>
<matches>
<tcp>
<destination-port>
<operator>neq</operator>
<port>21</port>
</destination-port>
</tcp>
</matches>
<actions>
<forwarding>drop</forwarding>
</actions>
</ace>
</aces>
</acl>
</acls>
</config>
5. Security Considerations
The YANG module specified in this document defines a schema for data
that is designed to be accessed via network management protocol such
as NETCONF [RFC6241] or RESTCONF [RFC8040]. The lowest NETCONF layer
is the secure transport layer and the mandatory-to-implement secure
transport is SSH [RFC6242]. The lowest RESTCONF layer is HTTPS, and
the mandatory-to-implement secure transport is TLS [RFC8446].
The NETCONF Access Control Model (NACM [RFC8341]) provides the means
to restrict access for particular NETCONF users to a pre-configured
subset of all available NETCONF protocol operations and content.
There are a number of data nodes defined in the YANG module which are
writable/creatable/deletable (i.e., config true, which is the
default). These data nodes may be considered sensitive or vulnerable
in some network environments. Write operations (e.g., <edit-config>)
to these data nodes without proper protection can have a negative
effect on network operations.
Jethanandani, et al. Expires May 10, 2019 [Page 43]

Internet-Draft ACL YANG model November 2018
These are the subtrees and data nodes and their sensitivity/
vulnerability:
/acls/acl/aces: This list specifies all the configured access
control entries on the device. Unauthorized write access to this
list can allow intruders to modify the entries so as to permit
traffic that should not be permitted, or deny traffic that should
be permitted. The former may result in a DoS attack, or
compromise the device. The latter may result in a DoS attack.
The impact of an unauthorized read access of the list will allow
the attacker to determine which rules are in effect, to better
craft an attack.
/acls/acl/aces/ace/actions/logging: This node specifies ability to
log packets that match this ace entry. Unauthorized write access
to this node can allow intruders to enable logging on one or many
ace entries, overwhelming the server in the process. Unauthorized
read access of this node can allow intruders to access logging
information, which could be used to craft an attack the server.
6. IANA Considerations
This document registers three URIs and three YANG modules.
6.1. URI Registration
This document registers three URIs in the IETF XML registry
[RFC3688]. Following the format in RFC 3688, the following
registration is requested to be made:
URI: urn:ietf:params:xml:ns:yang:ietf-access-control-list
URI: urn:ietf:params:xml:ns:yang:ietf-packet-fields
URI: urn:ietf:params:xml:ns:yang:ietf-ethertypes
Registrant Contact: The IESG.
XML: N/A, the requested URI is an XML namespace.
6.2. YANG Module Name Registration
This document registers three YANG module in the YANG Module Names
registry YANG [RFC6020].
Jethanandani, et al. Expires May 10, 2019 [Page 44]

Internet-Draft ACL YANG model November 2018
name: ietf-access-control-list
namespace: urn:ietf:params:xml:ns:yang:ietf-access-control-list
prefix: acl
reference: RFC XXXX
name: ietf-packet-fields
namespace: urn:ietf:params:xml:ns:yang:ietf-packet-fields
prefix: packet-fields
reference: RFC XXXX
name: ietf-ethertypes
namespace: urn:ietf:params:xml:ns:yang:ietf-ethertypes
prefix: ethertypes
reference: RFC XXXX
7. Acknowledgements
Alex Clemm, Andy Bierman and Lisa Huang started it by sketching out
an initial IETF draft in several past IETF meetings. That draft
included an ACL YANG model structure and a rich set of match filters,
and acknowledged contributions by Louis Fourie, Dana Blair, Tula
Kraiser, Patrick Gili, George Serpa, Martin Bjorklund, Kent Watsen,
and Phil Shafer. Many people have reviewed the various earlier
drafts that made the draft went into IETF charter.
Dean Bogdanovic, Kiran Agrahara Sreenivasa, Lisa Huang, and Dana
Blair each evaluated the YANG model in previous drafts separately,
and then worked together to created a ACL draft that was supported by
different vendors. That draft removed vendor specific features, and
gave examples to allow vendors to extend in their own proprietary
ACL. The earlier draft was superseded with this updated draft and
received more participation from many vendors.
Authors would like to thank Jason Sterne, Lada Lhotka, Juergen
Schoenwalder, David Bannister, Jeff Haas, Kristian Larsson and Einar
Nilsen-Nygaard for their review of and suggestions to the draft.
8. References8.1. Normative References
[RFC0791] Postel, J., "Internet Protocol", STD 5, RFC 791,
DOI 10.17487/RFC0791, September 1981,
<https://www.rfc-editor.org/info/rfc791>.
[RFC0792] Postel, J., "Internet Control Message Protocol", STD 5,
RFC 792, DOI 10.17487/RFC0792, September 1981,
<https://www.rfc-editor.org/info/rfc792>.
Jethanandani, et al. Expires May 10, 2019 [Page 45]

Internet-Draft ACL YANG model November 2018
in the packet header such as overall packet length. In another
example, /ietf-acl:acls/ietf-acl:acl/ietf-acl:aces/ietf-acl:ace/ietf-
acl:actions are augmented with a new choice of actions.
module: example-newco-acl
augment /acl:acls/acl:acl/acl:aces/acl:ace/acl:matches:
+--rw (protocol-payload-choice)?
| +--:(protocol-payload)
| +--rw protocol-payload* [value-keyword]
| +--rw value-keyword enumeration
+--rw (metadata)?
+--:(packet-length)
+--rw packet-length? uint16
augment /acl:acls/acl:acl/acl:aces/acl:ace/acl:actions:
+--rw (action)?
+--:(count)
| +--rw count? uint32
+--:(policer)
| +--rw policer? string
+--:(hiearchical-policer)
+--rw hierarchitacl-policer? string
augment /acl:acls/acl:acl/acl:aces/acl:ace/acl:actions:
+--rw default-action? identityref
A.2. Linux nftables
As Linux platform is becoming more popular as networking platform,
the Linux data model is changing. Previously ACLs in Linux were
highly protocol specific and different utilities were used (iptables,
ip6tables, arptables, ebtables), so each one had separate data model.
Recently, this has changed and a single utility, nftables, has been
developed. With a single application, it has a single data model for
filewall filters and it follows very similarly to the ietf-access-
control list module proposed in this draft. The nftables support
input and output ACEs and each ACE can be defined with match and
action.
The example in Section 4.3 can be configured using nftable tool as
below.
nft add table ip filter
nft add chain filter input
nft add rule ip filter input ip protocol tcp ip saddr \
192.0.2.1/24 drop
The configuration entries added in nftable would be.
Jethanandani, et al. Expires May 10, 2019 [Page 51]

Internet-Draft ACL YANG model November 2018
table ip filter {
chain input {
ip protocol tcp ip saddr 192.0.2.1/24 drop
}
}
We can see that there are many similarities between Linux nftables
and IETF ACL YANG data models and its extension models. It should be
fairly easy to do translation between ACL YANG model described in
this draft and Linux nftables.
A.3. Ethertypes
The ACL module is dependent on the definition of ethertypes. IEEE
owns the allocation of those ethertypes. This model is being
included here to enable definition of those types till such time that
IEEE takes up the task of publication of the model that defines those
ethertypes. At that time, this model can be deprecated.
<CODE BEGINS> file "ietf-ethertypes@2018-11-06.yang"
module ietf-ethertypes {
namespace "urn:ietf:params:xml:ns:yang:ietf-ethertypes";
prefix ethertypes;
organization
"IETF NETMOD (NETCONF Data Modeling Language)";
contact
"WG Web: <http://tools.ietf.org/wg/netmod/>
WG List: <mailto:netmod@ietf.org>
Editor: Mahesh Jethanandani
<mjethanandani@gmail.com>";
description
"This module contains the common definitions for the
Ethertype used by different modules. It is a
placeholder module, till such time that IEEE
starts a project to define these Ethertypes
and publishes a standard.
At that time this module can be deprecated.";
revision 2018-11-06 {
description
"Initial revision.";
Jethanandani, et al. Expires May 10, 2019 [Page 52]