draft-ietf-netmod-acl-model-11.txt   draft-ietf-netmod-acl-model-12.txt 
NETMOD WG D. Bogdanovic NETMOD WG M. Jethanandani
Internet-Draft Volta Networks Internet-Draft Cisco Systems, Inc
Intended status: Standards Track M. Jethanandani Intended status: Standards Track L. Huang
Expires: December 17, 2017 Cisco Systems, Inc Expires: March 5, 2018 General Electric
L. Huang
General Electric
S. Agarwal S. Agarwal
Cisco Systems, Inc. Cisco Systems, Inc.
D. Blair D. Blair
Cisco Systems, INc Cisco Systems, INc
June 15, 2017 September 1, 2017
Network Access Control List (ACL) YANG Data Model Network Access Control List (ACL) YANG Data Model
draft-ietf-netmod-acl-model-11 draft-ietf-netmod-acl-model-12
Abstract Abstract
This document describes a data model of Access Control List (ACL) This document describes a data model of Access Control List (ACL)
basic building blocks. basic building blocks.
Editorial Note (To be removed by RFC Editor) Editorial Note (To be removed by RFC Editor)
This draft contains many placeholder values that need to be replaced This draft contains many placeholder values that need to be replaced
with finalized values at the time of publication. This note with finalized values at the time of publication. This note
summarizes all of the substitutions that are needed. Please note summarizes all of the substitutions that are needed. Please note
that no other RFC Editor instructions are specified anywhere else in that no other RFC Editor instructions are specified anywhere else in
this document. this document.
Artwork in this document contains shorthand references to drafts in Artwork in this document contains shorthand references to drafts in
progress. Please apply the following replacements progress. Please apply the following replacements
o "XXXX" --> the assigned RFC value for this draft. 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 (Oct 12, 2016) needs to get updated with o Revision date in model needs to get updated with the date the
the date the draft gets approved. The date also needs to get draft gets approved. The date also needs to get reflected on the
reflected on the line with <CODE BEGINS>. line with <CODE BEGINS>.
Status of This Memo Status of This Memo
This Internet-Draft is submitted in full conformance with the This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on December 17, 2017. This Internet-Draft will expire on March 5, 2018.
Copyright Notice Copyright Notice
Copyright (c) 2017 IETF Trust and the persons identified as the Copyright (c) 2017 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
skipping to change at page 2, line 37 skipping to change at page 2, line 37
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3
1.1. Definitions and Acronyms . . . . . . . . . . . . . . . . 3 1.1. Definitions and Acronyms . . . . . . . . . . . . . . . . 3
2. Problem Statement . . . . . . . . . . . . . . . . . . . . . . 4 2. Problem Statement . . . . . . . . . . . . . . . . . . . . . . 4
3. Understanding ACL's Filters and Actions . . . . . . . . . . . 4 3. Understanding ACL's Filters and Actions . . . . . . . . . . . 4
3.1. ACL Modules . . . . . . . . . . . . . . . . . . . . . . . 5 3.1. ACL Modules . . . . . . . . . . . . . . . . . . . . . . . 5
4. ACL YANG Models . . . . . . . . . . . . . . . . . . . . . . . 9 4. ACL YANG Models . . . . . . . . . . . . . . . . . . . . . . . 9
4.1. IETF Access Control List module . . . . . . . . . . . . . 9 4.1. IETF Access Control List module . . . . . . . . . . . . . 9
4.2. IETF Packet Fields module . . . . . . . . . . . . . . . . 18 4.2. IETF Packet Fields module . . . . . . . . . . . . . . . . 18
4.3. An ACL Example . . . . . . . . . . . . . . . . . . . . . 28 4.3. An ACL Example . . . . . . . . . . . . . . . . . . . . . 31
4.4. Port Range Usage Example . . . . . . . . . . . . . . . . 28 4.4. Port Range Usage Example . . . . . . . . . . . . . . . . 32
5. Security Considerations . . . . . . . . . . . . . . . . . . . 29 5. Security Considerations . . . . . . . . . . . . . . . . . . . 33
6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 30 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 34
7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 30 7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 34
8. Open Issues . . . . . . . . . . . . . . . . . . . . . . . . . 31 8. Open Issues . . . . . . . . . . . . . . . . . . . . . . . . . 35
9. References . . . . . . . . . . . . . . . . . . . . . . . . . 31 9. References . . . . . . . . . . . . . . . . . . . . . . . . . 35
9.1. Normative References . . . . . . . . . . . . . . . . . . 31 9.1. Normative References . . . . . . . . . . . . . . . . . . 35
9.2. Informative References . . . . . . . . . . . . . . . . . 32 9.2. Informative References . . . . . . . . . . . . . . . . . 36
Appendix A. Extending ACL model examples . . . . . . . . . . . . 32 Appendix A. Extending ACL model examples . . . . . . . . . . . . 36
A.1. Example of extending existing model for route filtering . 32 A.1. Example of extending existing model for route filtering . 36
A.2. A company proprietary module example . . . . . . . . . . 34 A.2. A company proprietary module example . . . . . . . . . . 38
A.3. Example to augment model with mixed ACL type . . . . . . 42 A.3. Linux nftables . . . . . . . . . . . . . . . . . . . . . 44
A.4. Linux nftables . . . . . . . . . . . . . . . . . . . . . 43 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 45
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 44
1. Introduction 1. Introduction
Access Control List (ACL) is one of the basic elements to configure Access Control List (ACL) is one of the basic elements used to
device forwarding behavior. It is used in many networking concepts configure device forwarding behavior. It is used in many networking
such as Policy Based Routing, Firewalls etc. technologies such as Policy Based Routing, Firewalls etc.
An ACL is an ordered set of rules that is used to filter traffic on a An ACL is an ordered set of rules that is used to filter traffic on a
networking device. Each rule is represented by an Access Control networking device. Each rule is represented by an Access Control
Entry (ACE). Entry (ACE).
Each ACE has a group of match criteria and a group of action Each ACE has a group of match criteria and a group of action
criteria. criteria.
The match criteria consist of a tuple of packet header match criteria The match criteria consist of a tuple of packet header match criteria
and can have metadata match criteria as well. and can have metadata match criteria as well.
skipping to change at page 3, line 31 skipping to change at page 3, line 31
o Packet header matches apply to fields visible in the packet such o Packet header matches apply to fields visible in the packet such
as address or class of service or port numbers. as address or class of service or port numbers.
o In case vendor supports it, metadata matches apply to fields o In case vendor supports it, metadata matches apply to fields
associated with the packet but not in the packet header such as associated with the packet but not in the packet header such as
input interface or overall packet length input interface or overall packet length
The actions specify what to do with the packet when the matching The actions specify what to do with the packet when the matching
criteria is met. These actions are any operations that would apply criteria is met. These actions are any operations that would apply
to the packet, such as counting, policing, or simply forwarding.The to the packet, such as counting, policing, or simply forwarding.The
list of potential actions is endless depending on the innovations of list of potential actions is endless depending on the capabilities of
the networked devices. the networked devices.
Access Control List is also widely knowns as ACL (pronounce as [ak-uh 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 l]) or Access List. In this document, Access Control List, ACL and
Access List are used interchangeably. Access List are used interchangeably.
The matching of filters and actions in an ACE/ACL are triggered only The matching of filters and actions in an ACE/ACL are triggered only
after application/attachment of the ACL to an interface, VRF, vty/tty after application/attachment of the ACL to an interface, VRF, vty/tty
session, QoS policy, routing protocols amongst various other config session, QoS policy, routing protocols amongst various other config
attachment points. Once attached, it is used for filtering traffic attachment points. Once attached, it is used for filtering traffic
skipping to change at page 5, line 36 skipping to change at page 5, line 36
If there is a need to define new "matches" choice, such as IPFIX If there is a need to define new "matches" choice, such as IPFIX
[RFC5101], the container "matches" can be augmented. [RFC5101], the container "matches" can be augmented.
For a reference to the annotations used in the diagram below, see For a reference to the annotations used in the diagram below, see
YANG Tree Diagrams [I-D.ietf-netmod-yang-tree-diagrams]. YANG Tree Diagrams [I-D.ietf-netmod-yang-tree-diagrams].
module: ietf-access-control-list module: ietf-access-control-list
+--rw access-lists +--rw access-lists
+--rw acl* [acl-type acl-name] +--rw acl* [acl-type acl-name]
+--rw acl-name string +--rw acl-name string
+--rw acl-type acl-type +--rw acl-type acl-type
+--ro acl-oper-data +--ro acl-oper-data
+--rw access-list-entries +--rw aces
+--rw ace* [rule-name] +--rw ace* [rule-name]
+--rw rule-name string +--rw rule-name string
+--rw matches +--rw matches
| +--rw l2-acl {l2-acl}? | +--rw l2-acl {l2-acl}?
| | +--rw destination-mac-address? yang:mac-ad | | +--rw destination-mac-address? yang:mac-ad
dress dress
| | +--rw destination-mac-address-mask? yang:mac-ad | | +--rw destination-mac-address-mask? yang:mac-ad
dress dress
| | +--rw source-mac-address? yang:mac-ad | | +--rw source-mac-address? yang:mac-ad
dress dress
| | +--rw source-mac-address-mask? yang:mac-ad | | +--rw source-mac-address-mask? yang:mac-ad
dress dress
| | +--rw ether-type? string | | +--rw ether-type? string
| +--rw ipv4-acl {ipv4-acl}? | +--rw ipv4-acl {ipv4-acl}?
| | +--rw tos? uint8 | | +--rw dscp? inet:dscp
| | +--rw ecn? uint8
| | +--rw length? uint16 | | +--rw length? uint16
| | +--rw ttl? uint8 | | +--rw ttl? uint8
| | +--rw protocol? uint8 | | +--rw protocol? uint8
| | +--rw source-port-range! | | +--rw source-port-range!
| | | +--rw lower-port inet:port-number | | | +--rw lower-port inet:port-number
| | | +--rw upper-port? inet:port-number | | | +--rw upper-port? inet:port-number
| | | +--rw operation? operator
| | +--rw destination-port-range! | | +--rw destination-port-range!
| | | +--rw lower-port inet:port-number | | | +--rw lower-port inet:port-number
| | | +--rw upper-port? inet:port-number | | | +--rw upper-port? inet:port-number
| | | +--rw opearations? operator
| | +--rw ihl? uint8 | | +--rw ihl? uint8
| | +--rw flags? bits | | +--rw flags? bits
| | +--rw offset? uint16 | | +--rw offset? uint16
| | +--rw identification? uint16 | | +--rw identification? uint16
| | +--rw destination-ipv4-network? inet:ipv4-prefi | | +--rw destination-ipv4-network? inet:ipv4-prefi
x x
| | +--rw source-ipv4-network? inet:ipv4-prefi | | +--rw source-ipv4-network? inet:ipv4-prefi
x x
| +--rw ipv6-acl {ipv6-acl}? | +--rw ipv6-acl {ipv6-acl}?
| | +--rw tos? uint8 | | +--rw dscp? inet:dscp
| | +--rw ecn? uint8
| | +--rw length? uint16 | | +--rw length? uint16
| | +--rw ttl? uint8 | | +--rw ttl? uint8
| | +--rw protocol? uint8 | | +--rw protocol? uint8
| | +--rw source-port-range! | | +--rw source-port-range!
| | | +--rw lower-port inet:port-number | | | +--rw lower-port inet:port-number
| | | +--rw upper-port? inet:port-number | | | +--rw upper-port? inet:port-number
| | | +--rw operation? operator
| | +--rw destination-port-range! | | +--rw destination-port-range!
| | | +--rw lower-port inet:port-number | | | +--rw lower-port inet:port-number
| | | +--rw upper-port? inet:port-number | | | +--rw upper-port? inet:port-number
| | | +--rw opearations? operator
| | +--rw next-header? uint8 | | +--rw next-header? uint8
| | +--rw destination-ipv6-network? inet:ipv6-prefi | | +--rw destination-ipv6-network? inet:ipv6-prefi
x x
| | +--rw source-ipv6-network? inet:ipv6-prefi | | +--rw source-ipv6-network? inet:ipv6-prefi
x x
| | +--rw flow-label? inet:ipv6-flow- | | +--rw flow-label? inet:ipv6-flow-
label label
| +--rw l2-l3-ipv4-acl {mixed-ipv4-acl}? | +--rw l2-l3-ipv4-acl {mixed-ipv4-acl}?
| | +--rw destination-mac-address? yang:mac-ad | | +--rw destination-mac-address? yang:mac-ad
dress dress
skipping to change at page 6, line 46 skipping to change at page 7, line 4
| | +--rw destination-ipv6-network? inet:ipv6-prefi | | +--rw destination-ipv6-network? inet:ipv6-prefi
x x
| | +--rw source-ipv6-network? inet:ipv6-prefi | | +--rw source-ipv6-network? inet:ipv6-prefi
x x
| | +--rw flow-label? inet:ipv6-flow- | | +--rw flow-label? inet:ipv6-flow-
label label
| +--rw l2-l3-ipv4-acl {mixed-ipv4-acl}? | +--rw l2-l3-ipv4-acl {mixed-ipv4-acl}?
| | +--rw destination-mac-address? yang:mac-ad | | +--rw destination-mac-address? yang:mac-ad
dress dress
| | +--rw destination-mac-address-mask? yang:mac-ad | | +--rw destination-mac-address-mask? yang:mac-ad
dress dress
| | +--rw source-mac-address? yang:mac-ad | | +--rw source-mac-address? yang:mac-ad
dress dress
| | +--rw source-mac-address-mask? yang:mac-ad | | +--rw source-mac-address-mask? yang:mac-ad
dress dress
| | +--rw ether-type? string | | +--rw ether-type? string
| | +--rw tos? uint8 | | +--rw dscp? inet:dscp
| | +--rw ecn? uint8
| | +--rw length? uint16 | | +--rw length? uint16
| | +--rw ttl? uint8 | | +--rw ttl? uint8
| | +--rw protocol? uint8 | | +--rw protocol? uint8
| | +--rw source-port-range! | | +--rw source-port-range!
| | | +--rw lower-port inet:port-number | | | +--rw lower-port inet:port-number
| | | +--rw upper-port? inet:port-number | | | +--rw upper-port? inet:port-number
| | | +--rw operation? operator
| | +--rw destination-port-range! | | +--rw destination-port-range!
| | | +--rw lower-port inet:port-number | | | +--rw lower-port inet:port-number
| | | +--rw upper-port? inet:port-number | | | +--rw upper-port? inet:port-number
| | | +--rw opearations? operator
| | +--rw ihl? uint8 | | +--rw ihl? uint8
| | +--rw flags? bits | | +--rw flags? bits
| | +--rw offset? uint16 | | +--rw offset? uint16
| | +--rw identification? uint16 | | +--rw identification? uint16
| | +--rw destination-ipv4-network? inet:ipv4-p | | +--rw destination-ipv4-network? inet:ipv4-p
refix refix
| | +--rw source-ipv4-network? inet:ipv4-p | | +--rw source-ipv4-network? inet:ipv4-p
refix refix
| +--rw l2-l3-ipv6-acl {mixed-ipv6-acl}? | +--rw l2-l3-ipv6-acl {mixed-ipv6-acl}?
| | +--rw destination-mac-address? yang:mac-ad | | +--rw destination-mac-address? yang:mac-ad
dress dress
| | +--rw destination-mac-address-mask? yang:mac-ad | | +--rw destination-mac-address-mask? yang:mac-ad
dress dress
| | +--rw source-mac-address? yang:mac-ad | | +--rw source-mac-address? yang:mac-ad
dress dress
| | +--rw source-mac-address-mask? yang:mac-ad | | +--rw source-mac-address-mask? yang:mac-ad
dress dress
| | +--rw ether-type? string | | +--rw ether-type? string
| | +--rw tos? uint8 | | +--rw dscp? inet:dscp
| | +--rw ecn? uint8
| | +--rw length? uint16 | | +--rw length? uint16
| | +--rw ttl? uint8 | | +--rw ttl? uint8
| | +--rw protocol? uint8 | | +--rw protocol? uint8
| | +--rw source-port-range! | | +--rw source-port-range!
| | | +--rw lower-port inet:port-number | | | +--rw lower-port inet:port-number
| | | +--rw upper-port? inet:port-number | | | +--rw upper-port? inet:port-number
| | | +--rw operation? operator
| | +--rw destination-port-range! | | +--rw destination-port-range!
| | | +--rw lower-port inet:port-number | | | +--rw lower-port inet:port-number
| | | +--rw upper-port? inet:port-number | | | +--rw upper-port? inet:port-number
| | | +--rw opearations? operator
| | +--rw next-header? uint8 | | +--rw next-header? uint8
| | +--rw destination-ipv6-network? inet:ipv6-p | | +--rw destination-ipv6-network? inet:ipv6-p
refix refix
| | +--rw source-ipv6-network? inet:ipv6-p | | +--rw source-ipv6-network? inet:ipv6-p
refix refix
| | +--rw flow-label? inet:ipv6-f | | +--rw flow-label?
low-label | | inet:ipv6-flow-label
| +--rw l2-l3-ipv4-ipv6-acl {l2-l3-ipv4-ipv6-acl}? | +--rw l2-l3-ipv4-ipv6-acl {l2-l3-ipv4-ipv6-acl}?
| | +--rw destination-mac-address? yang:mac-ad | | +--rw destination-mac-address? yang:mac-ad
dress dress
| | +--rw destination-mac-address-mask? yang:mac-ad | | +--rw destination-mac-address-mask? yang:mac-ad
dress dress
| | +--rw source-mac-address? yang:mac-ad | | +--rw source-mac-address? yang:mac-ad
dress dress
| | +--rw source-mac-address-mask? yang:mac-ad | | +--rw source-mac-address-mask? yang:mac-ad
dress dress
| | +--rw ether-type? string | | +--rw ether-type? string
| | +--rw tos? uint8 | | +--rw dscp? inet:dscp
| | +--rw ecn? uint8
| | +--rw length? uint16 | | +--rw length? uint16
| | +--rw ttl? uint8 | | +--rw ttl? uint8
| | +--rw protocol? uint8 | | +--rw protocol? uint8
| | +--rw source-port-range! | | +--rw source-port-range!
| | | +--rw lower-port inet:port-number | | | +--rw lower-port inet:port-number
| | | +--rw upper-port? inet:port-number | | | +--rw upper-port? inet:port-number
| | | +--rw operation? operator
| | +--rw destination-port-range! | | +--rw destination-port-range!
| | | +--rw lower-port inet:port-number | | | +--rw lower-port inet:port-number
| | | +--rw upper-port? inet:port-number | | | +--rw upper-port? inet:port-number
| | | +--rw opearations? operator
| | +--rw ihl? uint8 | | +--rw ihl? uint8
| | +--rw flags? bits | | +--rw flags? bits
| | +--rw offset? uint16 | | +--rw offset? uint16
| | +--rw identification? uint16 | | +--rw identification? uint16
| | +--rw destination-ipv4-network? inet:ipv4-p | | +--rw destination-ipv4-network? inet:ipv4-p
refix refix
| | +--rw source-ipv4-network? inet:ipv4-p | | +--rw source-ipv4-network? inet:ipv4-p
refix refix
| | +--rw next-header? uint8 | | +--rw next-header? uint8
| | +--rw destination-ipv6-network? inet:ipv6-p | | +--rw destination-ipv6-network? inet:ipv6-p
refix refix
| | +--rw source-ipv6-network? inet:ipv6-p | | +--rw source-ipv6-network? inet:ipv6-p
refix refix
| | +--rw flow-label? inet:ipv6-f | | +--rw flow-label?
low-label | | inet:ipv6-flow-label
| +--rw tcp-acl {tcp-acl}? | +--rw tcp-acl {tcp-acl}?
| | +--rw sequence-number? uint32 | | +--rw sequence-number? uint32
| | +--rw acknowledgement-number? uint32 | | +--rw acknowledgement-number? uint32
| | +--rw data-offset? uint8 | | +--rw data-offset? uint8
| | +--rw reserved? uint8 | | +--rw reserved? uint8
| | +--rw flags? uint16 | | +--rw flags? bits
| | +--rw window-size? uint16 | | +--rw window-size? uint16
| | +--rw urgent-pointer? uint16 | | +--rw urgent-pointer? uint16
| | +--rw options? uint32 | | +--rw options? uint32
| +--rw udp-acl {udp-acl}? | +--rw udp-acl {udp-acl}?
| | +--rw length? uint16 | | +--rw length? uint16
| +--rw icmp-acl {icmp-acl}? | +--rw icmp-acl {icmp-acl}?
| | +--rw type? uint8 | | +--rw type? uint8
| | +--rw code? uint8 | | +--rw code? uint8
| | +--rw rest-of-header? uint32 | | +--rw rest-of-header? uint32
| +--rw any-acl! {any-acl}? | +--rw any-acl! {any-acl}?
| +--rw interface? if:interface-ref
+--rw actions +--rw actions
| +--rw (packet-handling)? | +--rw (packet-handling)?
| | +--:(deny) | | +--:(deny)
| | | +--rw deny? empty | | | +--rw deny? empty
| | +--:(permit) | | +--:(permit)
| | +--rw permit? empty | | +--rw permit? empty
| +--rw logging? boolean | +--rw logging? boolean
+--ro ace-oper-data +--ro ace-oper-data
+--ro match-counter? yang:counter64 +--ro match-counter? yang:counter64
skipping to change at page 9, line 32 skipping to change at page 9, line 48
associated with the "acl-name". Each of the entries in the associated with the "acl-name". Each of the entries in the
list("access-list-entries"), indexed by the string "rule-name", has list("access-list-entries"), indexed by the string "rule-name", has
containers defining "matches" and "actions". containers defining "matches" and "actions".
The "matches" define criteria used to identify patterns in "ietf- The "matches" define criteria used to identify patterns in "ietf-
packet-fields". The "actions" define behavior to undertake once a packet-fields". The "actions" define behavior to undertake once a
"match" has been identified. In addition to permit and deny for "match" has been identified. In addition to permit and deny for
actions, a logging option allows for a match to be logged that can be actions, a logging option allows for a match to be logged that can be
used to determine which rule was matched upon. used to determine which rule was matched upon.
<CODE BEGINS> file "ietf-access-control-list@2017-06-16.yang" <CODE BEGINS> file "ietf-access-control-list@2017-09-01.yang"
module ietf-access-control-list { module ietf-access-control-list {
namespace "urn:ietf:params:xml:ns:yang:ietf-access-control-list"; namespace "urn:ietf:params:xml:ns:yang:ietf-access-control-list";
prefix acl; prefix acl;
import ietf-yang-types { import ietf-yang-types {
prefix yang; prefix yang;
} }
import ietf-packet-fields { import ietf-packet-fields {
prefix packet-fields; prefix packet-fields;
} }
import ietf-interfaces {
prefix if;
}
organization organization
"IETF NETMOD (NETCONF Data Modeling Language) "IETF NETMOD (NETCONF Data Modeling Language)
Working Group"; Working Group";
contact contact
"WG Web: http://tools.ietf.org/wg/netmod/ "WG Web: http://tools.ietf.org/wg/netmod/
WG List: netmod@ietf.org WG List: netmod@ietf.org
Editor: Dean Bogdanovic
ivandean@gmail.com
Editor: Mahesh Jethanandani Editor: Mahesh Jethanandani
mjethanandani@gmail.com mjethanandani@gmail.com
Editor: Lisa Huang Editor: Lisa Huang
lyihuang16@gmail.com lyihuang16@gmail.com
Editor: Sonal Agarwal Editor: Sonal Agarwal
agarwaso@cisco.com agarwaso@cisco.com
Editor: Dana Blair Editor: Dana Blair
dblair@cisco.com"; dblair@cisco.com";
description description
"This YANG module defines a component that describing the "This YANG module defines a component that describe the
configuration of Access Control Lists (ACLs). configuration of Access Control Lists (ACLs).
Copyright (c) 2016 IETF Trust and the persons identified as
Copyright (c) 2017 IETF Trust and the persons identified as
the document authors. All rights reserved. the document authors. All rights reserved.
Redistribution and use in source and binary forms, with or Redistribution and use in source and binary forms, with or
without modification, is permitted pursuant to, and subject without modification, is permitted pursuant to, and subject
to the license terms contained in, the Simplified BSD to the license terms contained in, the Simplified BSD
License set forth in Section 4.c of the IETF Trust's Legal License set forth in Section 4.c of the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info). (http://trustee.ietf.org/license-info).
This version of this YANG module is part of RFC XXXX; see This version of this YANG module is part of RFC XXXX; see
the RFC itself for full legal notices."; the RFC itself for full legal notices.";
revision 2017-06-16 { revision 2017-09-01 {
description description
"Added feature and identity statements for different types "Added feature and identity statements for different types
of rule matches. Split the matching rules based on the of rule matches. Split the matching rules based on the
feature statement and added a must statement within feature statement and added a must statement within
each container."; each container.";
reference reference
"RFC XXX: Network Access Control List (ACL) YANG Data Model."; "RFC XXX: Network Access Control List (ACL) YANG Data Model.";
} }
revision 2016-10-12 {
description
"Base model for Network Access Control List (ACL).";
reference
"RFC XXXX: Network Access Control List (ACL)
YANG Data Model";
}
/* /*
* Identities * Identities
*/ */
identity acl-base { identity acl-base {
description description
"Base Access Control List type for all Access Control List type "Base Access Control List type for all Access Control List type
identifiers."; identifiers.";
} }
identity ipv4-acl { identity ipv4-acl {
base acl:acl-base; base acl:acl-base;
description description
"ACL that primarily matches on fields from the IPv4 header "ACL that primarily matches on fields from the IPv4 header
(e.g. IPv4 destination address) and layer 4 headers (e.g. TCP (e.g. IPv4 destination address) and layer 4 headers (e.g. TCP
destination port). An acl of type ipv4-acl does not contain destination port). An acl of type ipv4-acl does not contain
matches on fields in the ethernet header or the IPv6 header."; matches on fields in the ethernet header or the IPv6 header.";
} }
skipping to change at page 13, line 41 skipping to change at page 14, line 8
*/ */
typedef acl-type { typedef acl-type {
type identityref { type identityref {
base acl-base; base acl-base;
} }
description description
"This type is used to refer to an Access Control List "This type is used to refer to an Access Control List
(ACL) type"; (ACL) type";
} }
typedef access-control-list-ref { typedef acl-ref {
type leafref { type leafref {
path "/access-lists/acl/acl-name"; path "/access-lists/acl/acl-name";
} }
description description
"This type is used by data models that need to reference an "This type is used by data models that need to reference an
Access Control List"; Access Control List";
} }
/* /*
* Configuration data nodes * Configuration data nodes
skipping to change at page 14, line 39 skipping to change at page 15, line 6
description description
"Type of access control list. Indicates the primary intended "Type of access control list. Indicates the primary intended
type of match criteria (e.g. ethernet, IPv4, IPv6, mixed, type of match criteria (e.g. ethernet, IPv4, IPv6, mixed,
etc) used in the list instance."; etc) used in the list instance.";
} }
container acl-oper-data { container acl-oper-data {
config false; config false;
description description
"Overall Access Control List operational data"; "Overall Access Control List operational data";
} }
container access-list-entries { container aces {
description description
"The access-list-entries container contains "The access-list-entries container contains
a list of access-list-entries(ACE)."; a list of access-list-entries(ACE).";
list ace { list ace {
key "rule-name"; key "rule-name";
ordered-by user; ordered-by user;
description description
"List of access list entries(ACE)"; "List of access list entries(ACE)";
leaf rule-name { leaf rule-name {
type string; type string;
skipping to change at page 17, line 6 skipping to change at page 17, line 21
"Rule set that defines ICMP headers."; "Rule set that defines ICMP headers.";
} }
container any-acl { container any-acl {
if-feature any-acl; if-feature any-acl;
must "../../../../acl-type = 'any-acl'"; must "../../../../acl-type = 'any-acl'";
presence "Matches any"; presence "Matches any";
description description
"Rule set that allows for a any ACL."; "Rule set that allows for a any ACL.";
} }
leaf interface {
type if:interface-ref;
description
"Interface name that is specified to
match upon.";
}
} }
container actions { container actions {
description description
"Definitions of action criteria for this Access List "Definitions of action criteria for this Access List
Entry."; Entry.";
choice packet-handling { choice packet-handling {
default "deny"; default "deny";
description description
"Packet handling action."; "Packet handling action.";
skipping to change at page 17, line 30 skipping to change at page 18, line 4
"Deny action."; "Deny action.";
} }
} }
case permit { case permit {
leaf permit { leaf permit {
type empty; type empty;
description description
"Permit action."; "Permit action.";
} }
} }
} }
leaf logging { leaf logging {
type boolean; type boolean;
default "false";
description description
"Log the rule on which the match occurred. "Log the rule on which the match occurred.
Setting the value to true enables logging, Setting the value to true enables logging,
whereas setting the value to false disables it."; whereas setting the value to false disables it.";
} }
} }
/* /*
* Operational state data nodes * Operational state data nodes
*/ */
container ace-oper-data { container ace-oper-data {
skipping to change at page 18, line 28 skipping to change at page 18, line 51
get included for any given ACL with the exception of TCP, UDP and 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 ICMP header fields. Those fields can be used in conjunction with any
of the above layer 2 or layer 3 fields. of the above layer 2 or layer 3 fields.
Since the number of match criteria is very large, the base draft does Since the number of match criteria is very large, the base draft does
not include these directly but references them by "uses" to keep the not include these directly but references them by "uses" to keep the
base module simple. In case more match conditions are needed, those base module simple. In case more match conditions are needed, those
can be added by augmenting choices within container "matches" in can be added by augmenting choices within container "matches" in
ietf-access-control-list.yang model. ietf-access-control-list.yang model.
<CODE BEGINS> file "ietf-packet-fields@2017-06-16.yang" <CODE BEGINS> file "ietf-packet-fields@2017-09-01.yang"
module ietf-packet-fields { module ietf-packet-fields {
namespace "urn:ietf:params:xml:ns:yang:ietf-packet-fields"; namespace "urn:ietf:params:xml:ns:yang:ietf-packet-fields";
prefix packet-fields; prefix packet-fields;
import ietf-inet-types { import ietf-inet-types {
prefix inet; prefix inet;
} }
import ietf-yang-types { import ietf-yang-types {
prefix yang; prefix yang;
} }
organization organization
"IETF NETMOD (NETCONF Data Modeling Language) Working "IETF NETMOD (NETCONF Data Modeling Language) Working
Group"; Group";
contact contact
"WG Web: http://tools.ietf.org/wg/netmod/ "WG Web: http://tools.ietf.org/wg/netmod/
WG List: netmod@ietf.org WG List: netmod@ietf.org
Editor: Dean Bogdanovic Editor: Mahesh Jethanandani
ivandean@gmail.com mjethanandani@gmail.com
Editor: Mahesh Jethanandani Editor: Lisa Huang
mahesh@cisco.com lyihuang16@gmail.com
Editor: Lisa Huang Editor: Sonal Agarwal
lyihuang16@gmail.com agarwaso@cisco.com
Editor: Sonal Agarwal Editor: Dana Blair
agarwaso@cisco.com dblair@cisco.com";
Editor: Dana Blair
dblair@cisco.com";
description description
"This YANG module defines groupings that are used by "This YANG module defines groupings that are used by
ietf-access-control-list YANG module. Their usage is not ietf-access-control-list YANG module. Their usage is not
limited to ietf-access-control-list and can be limited to ietf-access-control-list and can be
used anywhere as applicable. used anywhere as applicable.
Copyright (c) 2016 IETF Trust and the persons identified as Copyright (c) 2017 IETF Trust and the persons identified as
the document authors. All rights reserved. the document authors. All rights reserved.
Redistribution and use in source and binary forms, with or Redistribution and use in source and binary forms, with or
without modification, is permitted pursuant to, and subject without modification, is permitted pursuant to, and subject
to the license terms contained in, the Simplified BSD to the license terms contained in, the Simplified BSD
License set forth in Section 4.c of the IETF Trust's Legal License set forth in Section 4.c of the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info). (http://trustee.ietf.org/license-info).
This version of this YANG module is part of RFC XXXX; see This version of this YANG module is part of RFC XXXX; see
the RFC itself for full legal notices."; the RFC itself for full legal notices.";
revision 2017-06-16 { revision 2017-09-01 {
description description
"Added header fields for TCP, UDP, and ICMP."; "Added header fields for TCP, UDP, and ICMP.";
reference reference
"RFC XXX: Network Access Control List (ACL) YANG Data Model."; "RFC XXX: Network Access Control List (ACL) YANG Data Model.";
} }
revision 2016-10-12 { /*
* Typedefs
*/
typedef operator {
type enumeration {
enum lt {
description
"Less than.";
}
enum gt {
description
"Greater than.";
}
enum eq {
description
"Equal to.";
}
enum neq {
description
"Not equal to.";
}
}
description description
"Initial version of packet fields used by "The source and destination port range definitions
ietf-access-control-list"; can be further qualified using an operator. An
reference operator is needed only if lower-port is specified
"RFC XXXX: Network Access Control List (ACL) and upper-port is not specified. The operator
YANG Data Model"; therefore further qualifies lower-port only.";
} }
grouping acl-transport-header-fields { grouping acl-transport-header-fields {
description description
"Transport header fields"; "Transport header fields";
container source-port-range { container source-port-range {
presence "Enables setting source port range"; presence "Enables setting source port range";
description description
"Inclusive range representing source ports to be used. "Inclusive range representing source ports to be used.
When only lower-port is present, it represents a single
port and eq operator is assumed to be default.
When both lower-port and upper-port are specified,
it implies a range inclusive of both values.
If no port is specified, 'any' (wildcard) is assumed.";
When only lower-port is present, it represents a single port.";
leaf lower-port { leaf lower-port {
type inet:port-number; type inet:port-number;
mandatory true; mandatory true;
description description
"Lower boundary for port."; "Lower boundary for port.";
} }
leaf upper-port { leaf upper-port {
type inet:port-number; type inet:port-number;
must ". >= ../lower-port" { must ". >= ../lower-port" {
error-message error-message
"The upper-port must be greater than or equal "The upper-port must be greater than or equal
to lower-port"; to lower-port";
} }
description description
"Upper boundary for port . If existing, the upper port "Upper boundary for port. If it exists, the upper port
must be greater or equal to lower-port."; must be greater or equal to lower-port.";
} }
leaf operation {
type operator;
must "(lower-port and not(upper-port))" {
error-message
"If lower-port is specified, and an operator is also
specified, then upper-port should not be specified.";
description
"If lower-port is specified, and an operator is also
specified, then upper-port should not be specified.";
}
default eq;
description
"Operator to be applied on the lower-port.";
}
} }
container destination-port-range { container destination-port-range {
presence "Enables setting destination port range"; presence "Enables setting destination port range";
description description
"Inclusive range representing destination ports to be used. "Inclusive range representing destination ports to be used.
When only lower-port is present, it represents a single When only lower-port is present, it represents a single
port."; port and eq operator is assumed to be default.
When both lower-port and upper-port are specified,
it implies a range inclusive of both values.
If no port is specified, 'any' (wildcard) is assumed. ";
leaf lower-port { leaf lower-port {
type inet:port-number; type inet:port-number;
mandatory true; mandatory true;
description description
"Lower boundary for port."; "Lower boundary for port.";
} }
leaf upper-port { leaf upper-port {
type inet:port-number; type inet:port-number;
must ". >= ../lower-port" { must ". >= ../lower-port" {
error-message error-message
"The upper-port must be greater than or equal "The upper-port must be greater than or equal
to lower-port"; to lower-port";
} }
description description
"Upper boundary for port. If existing, the upper port must "Upper boundary for port. If existing, the upper port must
be greater or equal to lower-port"; be greater or equal to lower-port";
} }
leaf opearations {
type operator;
must "(lower-port and not(upper-port))" {
error-message
"If lower-port is specified, and an operator is also
specified, then upper-port should not be specified.";
description
"If lower-port is specified, and an operator is also
specified, then upper-port should not be specified.";
}
default eq;
description
"Operator to be applied on the lower-port.";
}
} }
} }
grouping acl-ip-header-fields { grouping acl-ip-header-fields {
description description
"IP header fields common to ipv4 and ipv6"; "IP header fields common to ipv4 and ipv6";
reference reference
"RFC 791."; "RFC 791.";
leaf tos { leaf dscp {
type uint8; type inet:dscp;
description description
"Also known as Traffic Class in IPv6. The Type of Service (TOS) "Differentiated Services Code Point.";
provides an indication of the abstract parameters of the
quality of service desired.";
reference reference
"RFC 719, RFC 2460"; "RFC 2474: Definition of Differentiated services field
(DS field) in the IPv4 and IPv6 headers.";
}
leaf ecn {
type uint8 {
range 0..3;
}
description
"Explicit Congestion Notification.";
reference
"RFC 3168.";
} }
leaf length { leaf length {
type uint16; type uint16;
description description
"In IPv4 header field, this field is known as the Total Length. "In IPv4 header field, this field is known as the Total Length.
Total Length is the length of the datagram, measured in octets, Total Length is the length of the datagram, measured in octets,
including internet header and data. including internet header and data.
In IPv6 header field, this field is known as the Payload In IPv6 header field, this field is known as the Payload
skipping to change at page 26, line 4 skipping to change at page 27, line 47
size of 20 bytes and maximum of 60 bytes, size of 20 bytes and maximum of 60 bytes,
allowing for up to 40 bytes of options in the allowing for up to 40 bytes of options in the
header."; header.";
} }
leaf reserved { leaf reserved {
type uint8; type uint8;
description description
"Reserved for future use."; "Reserved for future use.";
} }
leaf flags { leaf flags {
type uint16; type bits {
bit ns {
position 0;
description
"ECN-nonce concealment protection";
reference "RFC 3540).";
}
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.";
reference "RFC 3168";
}
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.";
}
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
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 description
"Also known as Control Bits. Contains 9 1-bit flags."; "Also known as Control Bits. Contains 9 1-bit flags.";
} }
leaf window-size { leaf window-size {
type uint16; type uint16;
description description
"The size of the receive window, which specifies "The size of the receive window, which specifies
the number of window size units (by default, the number of window size units (by default,
bytes) (beyond the segment identified by the bytes) (beyond the segment identified by the
sequence number in the acknowledgment field) sequence number in the acknowledgment field)
that the sender of this segment is currently that the sender of this segment is currently
willing to receive."; willing to receive.";
} }
leaf urgent-pointer { leaf urgent-pointer {
type uint16; type uint16;
description description
"This field s an offset from the sequence number "This field is an offset from the sequence number
indicating the last urgent data byte."; indicating the last urgent data byte.";
} }
leaf options { leaf options {
type uint32; type uint32;
description description
"The length of this field is determined by the "The length of this field is determined by the
data offset field. Options have up to three data offset field. Options have up to three
fields: Option-Kind (1 byte), Option-Length fields: Option-Kind (1 byte), Option-Length
(1 byte), Option-Data (variable). The Option-Kind (1 byte), Option-Data (variable). The Option-Kind
skipping to change at page 28, line 17 skipping to change at page 32, line 11
11.11.11.1/24. 11.11.11.1/24.
Here is the acl configuration xml for this Access Control List: Here is the acl configuration xml for this Access Control List:
<?xml version='1.0' encoding='UTF-8'?> <?xml version='1.0' encoding='UTF-8'?>
<data xmlns="urn:ietf:params:xml:ns:netconf:base:1.0"> <data xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
<access-lists xmlns="urn:ietf:params:xml:ns:yang: <access-lists xmlns="urn:ietf:params:xml:ns:yang:
ietf-access-control-list"> ietf-access-control-list">
<acl> <acl>
<acl-name>sample-ipv4-acl</acl-name> <acl-name>sample-ipv4-acl</acl-name>
<acl-type>ipv4</acl-type> <acl-type>ipv4-acl</acl-type>
<access-list-entries> <aces>
<ace> <ace>
<rule-name>rule1</rule-name> <rule-name>rule1</rule-name>
<matches> <matches>
<source-ipv4-network> <ipv4-acl>
10.10.10.1/24 <protocol>tcp</protocol>
</source-ipv4-network> <destination-ipv4-network>
<destination-ipv4-network> 11.11.11.1/24
11.11.11.1/24 </destination-ipv4-network>
</destination-ipv4-network> <source-ipv4-network>
10.10.10.1/24
</source-ipv4-network>
</ipv4-acl>
</matches> </matches>
<actions> <actions>
<deny /> <packet-handling>deny</packet-handling>
</actions> </actions>
<protocol>
tcp
</protocol>
</ace> </ace>
</access-list-entries> </aces>
</acl> </acl>
</access-lists> </access-lists>
</data> </data>
The acl and aces can be described in CLI as the following: The acl and aces can be described in CLI as the following:
access-list ipv4 sample-ipv4-acl access-list ipv4 sample-ipv4-acl
deny tcp 10.10.10.1/24 11.11.11.1/24 deny tcp 10.10.10.1/24 11.11.11.1/24
4.4. Port Range Usage Example 4.4. Port Range Usage Example
skipping to change at page 29, line 32 skipping to change at page 33, line 30
than equal to 65535. than equal to 65535.
With the follow XML snippet: With the follow XML snippet:
<source-port-range> <source-port-range>
<lower-port>21</lower-port> <lower-port>21</lower-port>
</source-port-range> </source-port-range>
This represents port 21. This represents port 21.
With the following XML snippet, the configuration is specifying all
ports that are not equal to 21.
<source-port-range>
<lower-port>21</lower-port>
<operations>neq</operations>
</source-port-range>
5. Security Considerations 5. Security Considerations
The YANG module defined in this memo is designed to be accessed via The YANG module defined in this memo is designed to be accessed via
the NETCONF [RFC6241]. The lowest NETCONF layer is the secure the NETCONF [RFC6241]. The lowest NETCONF layer is the secure
transport layer and the mandatory-to-implement secure transport is transport layer and the mandatory-to-implement secure transport is
SSH [RFC6242]. The NETCONF Access Control Model ( NACM [RFC6536]) SSH [RFC6242]. The NETCONF Access Control Model ( NACM [RFC6536])
provides the means to restrict access for particular NETCONF users to provides the means to restrict access for particular NETCONF users to
a pre-configured subset of all available NETCONF protocol operations a pre-configured subset of all available NETCONF protocol operations
and content. and content.
skipping to change at page 30, line 47 skipping to change at page 35, line 6
Alex Clemm, Andy Bierman and Lisa Huang started it by sketching out Alex Clemm, Andy Bierman and Lisa Huang started it by sketching out
an initial IETF draft in several past IETF meetings. That draft an initial IETF draft in several past IETF meetings. That draft
included an ACL YANG model structure and a rich set of match filters, included an ACL YANG model structure and a rich set of match filters,
and acknowledged contributions by Louis Fourie, Dana Blair, Tula and acknowledged contributions by Louis Fourie, Dana Blair, Tula
Kraiser, Patrick Gili, George Serpa, Martin Bjorklund, Kent Watsen, Kraiser, Patrick Gili, George Serpa, Martin Bjorklund, Kent Watsen,
and Phil Shafer. Many people have reviewed the various earlier and Phil Shafer. Many people have reviewed the various earlier
drafts that made the draft went into IETF charter. drafts that made the draft went into IETF charter.
Dean Bogdanovic, Kiran Agrahara Sreenivasa, Lisa Huang, and Dana Dean Bogdanovic, Kiran Agrahara Sreenivasa, Lisa Huang, and Dana
Blair each evaluated the YANG model in previous draft separately and Blair each evaluated the YANG model in previous drafts separately,
then work together, to created a new ACL draft that can be supported and then worked together to created a ACL draft that was supported by
by different vendors. The new draft removes vendor specific different vendors. That draft removed vendor specific features, and
features, and gives examples to allow vendors to extend in their own gave examples to allow vendors to extend in their own proprietary
proprietary ACL. The earlier draft was superseded with the new one ACL. The earlier draft was superseded with this updated draft and
that received more participation from many vendors. received more participation from many vendors.
Authors would like to thank Jason Sterne, Lada Lhotka, Juergen Authors would like to thank Jason Sterne, Lada Lhotka, Juergen
Schoenwalder, and David Bannister for their review of and suggestions Schoenwalder, and David Bannister for their review of and suggestions
to the draft. to the draft.
8. Open Issues 8. Open Issues
o The current model does not support the concept of "containers" o The current model does not support the concept of "containers"
used to contain multiple addresses per rule entry. used to contain multiple addresses per rule entry.
o The current model defines 'any' rule as a presence container,
allowing a user to define any 'any' rule.
o The model defines 'ether-type' node as a string. Ideally, this o The model defines 'ether-type' node as a string. Ideally, this
should be a well defined list of all Ethernet Types assigned by should be a well defined list of all Ethernet Types assigned by
IEEE. IEEE.
o Should this draft include route-policy definition as defined in
draft-ietf-rtgwg-policy-model?
9. References 9. References
9.1. Normative References 9.1. Normative References
[RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688, [RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688,
DOI 10.17487/RFC3688, January 2004, DOI 10.17487/RFC3688, January 2004, <https://www.rfc-
<http://www.rfc-editor.org/info/rfc3688>. editor.org/info/rfc3688>.
[RFC6020] Bjorklund, M., Ed., "YANG - A Data Modeling Language for [RFC6020] Bjorklund, M., Ed., "YANG - A Data Modeling Language for
the Network Configuration Protocol (NETCONF)", RFC 6020, the Network Configuration Protocol (NETCONF)", RFC 6020,
DOI 10.17487/RFC6020, October 2010, DOI 10.17487/RFC6020, October 2010, <https://www.rfc-
<http://www.rfc-editor.org/info/rfc6020>. editor.org/info/rfc6020>.
[RFC6241] Enns, R., Ed., Bjorklund, M., Ed., Schoenwaelder, J., Ed., [RFC6241] Enns, R., Ed., Bjorklund, M., Ed., Schoenwaelder, J., Ed.,
and A. Bierman, Ed., "Network Configuration Protocol and A. Bierman, Ed., "Network Configuration Protocol
(NETCONF)", RFC 6241, DOI 10.17487/RFC6241, June 2011, (NETCONF)", RFC 6241, DOI 10.17487/RFC6241, June 2011,
<http://www.rfc-editor.org/info/rfc6241>. <https://www.rfc-editor.org/info/rfc6241>.
[RFC6242] Wasserman, M., "Using the NETCONF Protocol over Secure [RFC6242] Wasserman, M., "Using the NETCONF Protocol over Secure
Shell (SSH)", RFC 6242, DOI 10.17487/RFC6242, June 2011, Shell (SSH)", RFC 6242, DOI 10.17487/RFC6242, June 2011,
<http://www.rfc-editor.org/info/rfc6242>. <https://www.rfc-editor.org/info/rfc6242>.
[RFC6536] Bierman, A. and M. Bjorklund, "Network Configuration [RFC6536] Bierman, A. and M. Bjorklund, "Network Configuration
Protocol (NETCONF) Access Control Model", RFC 6536, Protocol (NETCONF) Access Control Model", RFC 6536,
DOI 10.17487/RFC6536, March 2012, DOI 10.17487/RFC6536, March 2012, <https://www.rfc-
<http://www.rfc-editor.org/info/rfc6536>. editor.org/info/rfc6536>.
9.2. Informative References 9.2. Informative References
[I-D.ietf-netmod-yang-tree-diagrams] [I-D.ietf-netmod-yang-tree-diagrams]
Bjorklund, M. and L. Berger, "YANG Tree Diagrams", draft- Bjorklund, M. and L. Berger, "YANG Tree Diagrams", draft-
ietf-netmod-yang-tree-diagrams-00 (work in progress), June ietf-netmod-yang-tree-diagrams-01 (work in progress), June
2017. 2017.
[RFC5101] Claise, B., Ed., "Specification of the IP Flow Information [RFC5101] Claise, B., Ed., "Specification of the IP Flow Information
Export (IPFIX) Protocol for the Exchange of IP Traffic Export (IPFIX) Protocol for the Exchange of IP Traffic
Flow Information", RFC 5101, DOI 10.17487/RFC5101, January Flow Information", RFC 5101, DOI 10.17487/RFC5101, January
2008, <http://www.rfc-editor.org/info/rfc5101>. 2008, <https://www.rfc-editor.org/info/rfc5101>.
Appendix A. Extending ACL model examples Appendix A. Extending ACL model examples
A.1. Example of extending existing model for route filtering A.1. Example of extending existing model for route filtering
With proposed modular design, it is easy to extend the model with With proposed modular design, it is easy to extend the model with
other features. Those features can be standard features, like route other features. Those features can be standard features, like route
filters. Route filters match on specific IP addresses or ranges of filters. Route filters match on specific IP addresses or ranges of
prefixes. Much like ACLs, they include some match criteria and prefixes. Much like ACLs, they include some match criteria and
corresponding match action(s). For that reason, it is very simple to corresponding match action(s). For that reason, it is very simple to
extend existing ACL model with route filtering. The combination of a extend existing ACL model with route filtering. The combination of a
route prefix and prefix length along with the type of match route prefix and prefix length along with the type of match
determines how route filters are evaluated against incoming routes. determines how route filters are evaluated against incoming routes.
Different vendors have different match types and in this model we are Different vendors have different match types and in this model we are
using only ones that are common across all vendors participating in using only ones that are common across all vendors participating in
this draft. As in this example, the base ACL model can be extended this draft. As in this example, the base ACL model can be extended
with company proprietary extensions, described in the next section. with company proprietary extensions, described in the next section.
module: example-ext-route-filter module: example-ext-route-filter
augment /ietf-acl:access-lists/ietf-acl:acl/ augment /ietf-acl:access-lists/ietf-acl:acl/ietf-acl:aces/ietf-acl:ac
ietf-acl:access-list-entries/ietf-acl:ace/ietf-acl:matches: e/ietf-acl:matches:
+--rw (route-prefix)? +--rw (route-prefix)?
+--:(range) +--:(range)
+--rw (ipv4-range)? +--rw (ipv4-range)?
| +--:(v4-lower-bound) | +--:(v4-lower-bound)
| | +--rw v4-lower-bound? inet:ipv4-prefix | | +--rw v4-lower-bound? inet:ipv4-prefix
| +--:(v4-upper-bound) | +--:(v4-upper-bound)
| +--rw v4-upper-bound? inet:ipv4-prefix | +--rw v4-upper-bound? inet:ipv4-prefix
+--rw (ipv6-range)? +--rw (ipv6-range)?
+--:(v6-lower-bound) +--:(v6-lower-bound)
| +--rw v6-lower-bound? inet:ipv6-prefix | +--rw v6-lower-bound? inet:ipv6-prefix
+--:(v6-upper-bound) +--:(v6-upper-bound)
+--rw v6-upper-bound? inet:ipv6-prefix +--rw v6-upper-bound? inet:ipv6-prefix
file "example-ext-route-filter@2016-10-12.yang" file "example-ext-route-filter@2017-09-01.yang"
module example-ext-route-filter { module example-ext-route-filter {
namespace "urn:ietf:params:xml:ns:yang:example-ext-route-filter"; namespace "urn:ietf:params:xml:ns:yang:example-ext-route-filter";
prefix example-ext-route-filter; prefix example-ext-route-filter;
import ietf-inet-types { import ietf-inet-types {
prefix "inet"; prefix "inet";
} }
import ietf-access-control-list { import ietf-access-control-list {
prefix "ietf-acl"; prefix "ietf-acl";
} }
organization organization
"Route model group."; "Route model group.";
skipping to change at page 33, line 26 skipping to change at page 37, line 27
"abc@abc.com"; "abc@abc.com";
description " description "
This module describes route filter as a collection of This module describes route filter as a collection of
match prefixes. When specifying a match prefix, you match prefixes. When specifying a match prefix, you
can specify an exact match with a particular route or can specify an exact match with a particular route or
a less precise match. You can configure either a a less precise match. You can configure either a
common action that applies to the entire list or an common action that applies to the entire list or an
action associated with each prefix. action associated with each prefix.
"; ";
revision 2016-10-12 { revision 2017-09-01 {
description description
"Creating Route-Filter extension model based on "Creating Route-Filter extension model based on
ietf-access-control-list model"; ietf-access-control-list model";
reference " "; reference "Example route filter";
} }
augment "/ietf-acl:access-lists/ietf-acl:acl/"
+ "ietf-acl:access-list-entries/ietf-acl:ace/ietf-acl:matches"{ augment "/ietf-acl:access-lists/ietf-acl:acl/" +
"ietf-acl:aces/ietf-acl:ace/ietf-acl:matches" {
description " description "
This module augments the matches container in the ietf-acl This module augments the matches container in the ietf-acl
module with route filter specific actions module with route filter specific actions";
";
choice route-prefix{ choice route-prefix{
description "Define route filter match criteria"; description "Define route filter match criteria";
case range { case range {
description description
"Route falls between the lower prefix/prefix-length "Route falls between the lower prefix/prefix-length
and the upperprefix/prefix-length."; and the upperprefix/prefix-length.";
choice ipv4-range { choice ipv4-range {
description "Defines the IPv4 prefix range"; description "Defines the IPv4 prefix range";
leaf v4-lower-bound { leaf v4-lower-bound {
type inet:ipv4-prefix; type inet:ipv4-prefix;
description description
"Defines the lower IPv4 prefix/prefix length"; "Defines the lower IPv4 prefix/prefix length";
} }
leaf v4-upper-bound { leaf v4-upper-bound {
type inet:ipv4-prefix; type inet:ipv4-prefix;
description description
"Defines the upper IPv4 prefix/prefix length"; "Defines the upper IPv4 prefix/prefix length";
} }
} }
choice ipv6-range { choice ipv6-range {
description "Defines the IPv6 prefix/prefix range"; description "Defines the IPv6 prefix/prefix range";
leaf v6-lower-bound { leaf v6-lower-bound {
skipping to change at page 34, line 50 skipping to change at page 39, line 6
Module "example-newco-acl" is an example of company proprietary model Module "example-newco-acl" is an example of company proprietary model
that augments "ietf-acl" module. It shows how to use 'augment' with that augments "ietf-acl" module. It shows how to use 'augment' with
an XPath expression to add additional match criteria, action an XPath expression to add additional match criteria, action
criteria, and default actions when no ACE matches found, as well how criteria, and default actions when no ACE matches found, as well how
to attach an Access Control List to an interface. All these are to attach an Access Control List to an interface. All these are
company proprietary extensions or system feature extensions. company proprietary extensions or system feature extensions.
"example-newco-acl" is just an example and it is expected from "example-newco-acl" is just an example and it is expected from
vendors to create their own proprietary models. vendors to create their own proprietary models.
The following figure is the tree structure of example-newco-acl. In The following figure is the tree structure of example-newco-acl. In
this example, /ietf-acl:access-lists/ietf-acl:acl/ietf-acl:access- this example, /ietf-acl:access-lists/ietf-acl:acl/ietf-acl:aces/ietf-
list-entries/ ietf-acl:ace/ietf-acl:matches are augmented with two acl:ace/ietf-acl:matches are augmented with two new choices,
new choices, protocol-payload-choice and metadata. The protocol- protocol-payload-choice and metadata. The protocol-payload-choice
payload-choice uses a grouping with an enumeration of all supported uses a grouping with an enumeration of all supported protocol values.
protocol values. Metadata matches apply to fields associated with Metadata matches apply to fields associated with the packet but not
the packet but not in the packet header such as input interface or in the packet header such as input interface or overall packet
overall packet length. In other example, /ietf-acl:access-lists/ length. In other example, /ietf-acl:access-lists/ietf-acl:acl/ietf-
ietf-acl:acl/ietf-acl:access-list-entries/ ietf-acl:ace/ietf- acl:aces/ietf-acl:ace/ietf-acl:actions are augmented with new choice
acl:actions are augmented with new choice of actions. of actions.
module: example-newco-acl module: example-newco-acl
augment /ietf-acl:access-lists/ietf-acl:acl/ augment /ietf-acl:access-lists/ietf-acl:acl/ietf-acl:aces/ietf-acl:ac
ietf-acl:access-list-entries/ietf-acl:ace/ietf-acl:matches: e/ietf-acl:matches:
+--rw vlan-tagged? uint16 +--rw (protocol-payload-choice)?
+--rw mpls-unicast? uint16 | +--:(protocol-payload)
+--rw mpls-multicast? uint16 | +--rw protocol-payload* [value-keyword]
+--rw ipv4? uint16 | +--rw value-keyword enumeration
+--rw ipv6? uint16 +--rw (metadata)?
augment /ietf-acl:access-lists/ietf-acl:acl/ +--:(interface-name)
ietf-acl:access-list-entries/ietf-acl:ace/ietf-acl:matches: +--rw interface-name* [input-interface]
+--rw ipv4-ttl? uint8 +--rw input-interface ietf-if:interface-ref
+--rw ipv4-len? uint16 augment /ietf-acl:access-lists/ietf-acl:acl/ietf-acl:aces/ietf-acl:ac
+--rw ipv4-ihl? uint8 e/ietf-acl:actions:
+--rw ipv4-id? uint16 +--rw (action)?
+--rw ipv4-flags? ipv4-flags-type +--:(count)
+--rw ipv4-offset? uint16 | +--rw count? string
augment /ietf-acl:access-lists/ietf-acl:acl/ +--:(policer)
ietf-acl:access-list-entries/ietf-acl:ace/ietf-acl:matches: | +--rw policer? string
+--rw (protocol-payload-choice)? +--:(hiearchical-policer)
| +--:(protocol-payload) +--rw hierarchitacl-policer? string
| +--rw protocol-payload* [value-keyword]
| +--rw value-keyword enumeration
+--rw (metadata)?
+--:(interface-name)
+--rw interface-name* [input-interface]
+--rw input-interface ietf-if:interface-ref
augment /ietf-acl:access-lists/ietf-acl:acl/
ietf-acl:access-list-entries/ietf-acl:ace/ietf-acl:actions:
+--rw (action)?
+--:(count)
| +--rw count? string
+--:(policer)
| +--rw policer? string
+--:(hiearchical-policer)
+--rw hierarchitacl-policer? string
augment /ietf-acl:access-lists/ietf-acl:acl: augment /ietf-acl:access-lists/ietf-acl:acl:
+--rw default-actions +--rw default-actions
+--rw deny? empty +--rw deny? empty
augment /ietf-if:interfaces/ietf-if:interface: augment /ietf-if:interfaces/ietf-if:interface:
+--rw acl
+--rw acl +--rw acl-name? ietf-acl:acl-ref
+--rw acl-name? ietf-acl:access-control-list-ref +--ro match-counter? yang:counter64
+--ro match-counter? yang:counter64 +--rw (direction)?
+--rw (direction)? +--:(in)
+--:(in) | +--rw in? empty
| +--rw in? empty +--:(out)
+--:(out) +--rw out? empty
+--rw out? empty augment /ietf-acl:access-lists/ietf-acl:acl/ietf-acl:aces/ietf-acl:ac
augment /ietf-acl:access-lists/ietf-acl:acl/ietf-acl:acl-oper-data: e/ietf-acl:ace-oper-data:
+--ro targets +--ro targets
+--ro (interface)? +--ro (interface)?
+--:(interface-name) +--:(interface-name)
+--ro interface-name* ietf-if:interface-ref +--ro interface-name* ietf-if:interface-ref
module example-newco-acl { module example-newco-acl {
yang-version 1.1; yang-version 1.1;
namespace "urn:newco:params:xml:ns:yang:example-newco-acl"; namespace "urn:newco:params:xml:ns:yang:example-newco-acl";
prefix example-newco-acl; prefix example-newco-acl;
import ietf-access-control-list { import ietf-access-control-list {
skipping to change at page 36, line 45 skipping to change at page 41, line 21
import ietf-yang-types { import ietf-yang-types {
prefix yang; prefix yang;
} }
organization organization
"Newco model group."; "Newco model group.";
contact contact
"abc@newco.com"; "abc@newco.com";
description description
"This YANG module augment IETF ACL Yang."; "This YANG module augments IETF ACL Yang.";
revision 2016-10-12{ revision 2017-09-01 {
description description
"Creating NewCo proprietary extensions to ietf-acl model"; "Creating NewCo proprietary extensions to ietf-acl model";
reference reference
"RFC XXXX: Network Access Control List (ACL) "RFC XXXX: Network Access Control List (ACL)
YANG Data Model"; YANG Data Model";
}
typedef known-ether-type {
type enumeration {
enum "ipv4" {
value 2048; // 0x0800
description "Internet Protocol version 4 (IPv4)";
}
enum "vlan-tagged" {
value 33024; // 0x8100
description
"VLAN-tagged frame (IEEE 802.1Q) & Shortest Path
Bridging IEEE 802.1aq[4]";
}
enum "ipv6" {
value 34525; // 0x86DD
description "Internet Protocol Version 6 (IPv6)";
}
enum "mpls-unicast" {
value 34887; // 0x8847
description "MPLS unicast";
}
enum "mpls-multicast" {
value 34888; // 0x8848
description "MPLS multicast";
}
}
description "Listing supported Ethertypes";
}
typedef ipv4-flags-type {
type bits {
bit ipv4-reserved {
position 0;
description "reserved bit";
}
bit ipv4-DF {
position 1;
description "DF bit";
}
bit ipv4-MF {
position 2;
description "MF bit";
}
}
description "IPv4 flag types";
} }
augment "/ietf-acl:access-lists/ietf-acl:acl/" +
"ietf-acl:access-list-entries/ietf-acl:ace/" +
"ietf-acl:matches" {
when "ietf-acl:access-lists/ietf-acl:acl/" +
"ietf-acl:acl-type = 'ace-eth'";
description "additional MAC header matching";
leaf vlan-tagged {
type uint16;
description "Ethernet frame with VLAN tag";
}
leaf mpls-unicast {
type uint16;
description "Ethernet frame with MPLS unicast payload";
}
leaf mpls-multicast {
type uint16;
description "Ethernet frame with MPLS multicast payload";
}
leaf ipv4 {
type uint16;
description "Ethernet frame with IPv4 unicast payload";
}
leaf ipv6 {
type uint16;
description "Ethernet frame with IPv4 unicast payload";
}
}
augment "/ietf-acl:access-lists/ietf-acl:acl/" + augment "/ietf-acl:access-lists/ietf-acl:acl/" +
"ietf-acl:access-list-entries/ietf-acl:ace/" + "ietf-acl:aces/ietf-acl:ace/" +
"ietf-acl:matches" { "ietf-acl:matches" {
when "ietf-acl:access-lists/ietf-acl:acl/" +
"ietf-acl:acl-type = 'ipv4-acl'";
description "additional IP header information";
leaf ipv4-ttl {
type uint8;
description "time to live of a given packet as
defined in RFC791";
}
leaf ipv4-len {
type uint16;
description "total packet length as defined in RFC791";
}
leaf ipv4-ihl {
type uint8 {
range 0..15;
}
description "Internet Header Length in 32 bit words
(see RFC791). Note that while the minimum
value for this field in a packet is 5,
we leave open the possibility here that
the packet has been corrupted.";
}
leaf ipv4-id {
type uint16;
description "Identification as decribed in RFC791";
}
leaf ipv4-flags {
type ipv4-flags-type;
description "IPv4 flags as defined in RFC791";
}
leaf ipv4-offset {
type uint16 {
range 0..8191;
}
description "Matches on the packet fragment offset";
}
}
augment "/ietf-acl:access-lists/ietf-acl:acl/" +
"ietf-acl:access-list-entries/ietf-acl:ace/" +
"ietf-acl:matches" {
description "Newco proprietary simple filter matches"; description "Newco proprietary simple filter matches";
choice protocol-payload-choice { choice protocol-payload-choice {
description "Newo proprietary payload match condition"; description "Newo proprietary payload match condition";
list protocol-payload { list protocol-payload {
key value-keyword; key value-keyword;
ordered-by user; ordered-by user;
description "Match protocol payload"; description "Match protocol payload";
uses match-simple-payload-protocol-value; uses match-simple-payload-protocol-value;
} }
} }
skipping to change at page 40, line 15 skipping to change at page 42, line 10
list interface-name { list interface-name {
key input-interface; key input-interface;
ordered-by user; ordered-by user;
description "Match interface name"; description "Match interface name";
uses metadata; uses metadata;
} }
} }
} }
augment "/ietf-acl:access-lists/ietf-acl:acl/" + augment "/ietf-acl:access-lists/ietf-acl:acl/" +
"ietf-acl:access-list-entries/ietf-acl:ace/" + "ietf-acl:aces/ietf-acl:ace/" +
"ietf-acl:actions" { "ietf-acl:actions" {
description "Newco proprietary simple filter actions"; description "Newco proprietary simple filter actions";
choice action { choice action {
description ""; description "";
case count { case count {
description "Count the packet in the named counter"; description "Count the packet in the named counter";
leaf count { leaf count {
type string; type string;
description ""; description "";
} }
} }
case policer { case policer {
description "Name of policer to use to rate-limit traffic"; description "Name of policer to use to rate-limit traffic";
leaf policer { leaf policer {
type string; type string;
description ""; description "";
} }
} }
case hiearchical-policer { case hiearchical-policer {
description "Name of hierarchical policer to use to description "Name of hierarchical policer to use to
rate-limit traffic"; rate-limit traffic";
leaf hierarchitacl-policer{ leaf hierarchitacl-policer {
type string; type string;
description ""; description "";
} }
} }
} }
} }
augment "/ietf-acl:access-lists/ietf-acl:acl" { augment "/ietf-acl:access-lists/ietf-acl:acl" {
description "Newco proprietary default action"; description "Newco proprietary default action";
container default-actions { container default-actions {
skipping to change at page 41, line 8 skipping to change at page 43, line 4
description "Newco proprietary default action"; description "Newco proprietary default action";
container default-actions { container default-actions {
description description
"Actions that occur if no access-list entry is matched."; "Actions that occur if no access-list entry is matched.";
leaf deny { leaf deny {
type empty; type empty;
description ""; description "";
} }
} }
} }
grouping metadata { grouping metadata {
description description
"Fields associated with a packet which are not in "Fields associated with a packet which are not in
the header."; the header.";
leaf input-interface { leaf input-interface {
type ietf-if:interface-ref { type ietf-if:interface-ref {
require-instance false; require-instance false;
} }
description description
"Packet was received on this interface"; "Packet was received on this interface";
} }
} }
grouping match-simple-payload-protocol-value { grouping match-simple-payload-protocol-value {
skipping to change at page 41, line 36 skipping to change at page 43, line 31
enum icmp { enum icmp {
description "Internet Control Message Protocol"; description "Internet Control Message Protocol";
} }
enum icmp6 { enum icmp6 {
description "Internet Control Message Protocol Version 6"; description "Internet Control Message Protocol Version 6";
} }
enum range { enum range {
description "Range of values"; description "Range of values";
} }
} }
description "(null)"; description "(null)";
} }
} }
augment "/ietf-if:interfaces/ietf-if:interface" { augment "/ietf-if:interfaces/ietf-if:interface" {
description "Apply ACL to interfaces"; description "Apply ACL to interfaces";
container acl{ container acl {
description "ACL related properties."; description "ACL related properties.";
leaf acl-name { leaf acl-name {
type ietf-acl:access-control-list-ref; type ietf-acl:acl-ref;
description "Access Control List name."; description "Access Control List name.";
} }
leaf match-counter { leaf match-counter {
type yang:counter64; type yang:counter64;
config false; config false;
description description
"Total match count for Access Control "Total match count for Access Control
List on this interface"; List on this interface";
} }
choice direction { choice direction {
description "Applying ACL in which traffic direction"; description "Applying ACL in which traffic direction";
leaf in { leaf in {
type empty; type empty;
description "Inbound traffic"; description "Inbound traffic";
} }
leaf out { leaf out {
type empty; type empty;
description "Outbound traffic"; description "Outbound traffic";
} }
} }
} }
} }
augment "/ietf-acl:access-lists/ietf-acl:acl/" + augment "/ietf-acl:access-lists/ietf-acl:acl/" +
"ietf-acl:acl-oper-data" { "ietf-acl:aces/ietf-acl:ace/" +
"ietf-acl:ace-oper-data" {
description description
"This is an example on how to apply acl to a target to collect "This is an example on how to apply acl to a target to collect
operational data"; operational data";
container targets { container targets {
description "To which object is the ACL attached to"; description "To which object is the ACL attached to";
choice interface { choice interface {
description description
"Access Control List was attached to this interface"; "Access Control List was attached to this interface";
leaf-list interface-name{ leaf-list interface-name{
type ietf-if:interface-ref { type ietf-if:interface-ref {
require-instance true; require-instance true;
}
description "Attached to this interface name";
} }
description "Attached to this interface name";
} }
} }
} }
} }
Draft authors expect that different vendors will provide their own Draft authors expect that different vendors will provide their own
yang models as in the example above, which is the augmentation of the yang models as in the example above, which is the augmentation of the
base model base model
A.3. Example to augment model with mixed ACL type A.3. Linux nftables
As vendors (or IETF) add more features to ACL, the model is easily
augmented. One of such augmentations can be to add support for mixed
type of ACLs, where acl-type-base can be augmented like in example
below:
identity mixed-l3-acl {
base "access-control-list:acl-type-base";
description "ACL that contains a mix of entries that
primarily match on fields in IPv4 headers and entries
that primarily match on fields in IPv6 headers.
Matching on layer 4 header fields may also exist in the
list. An acl of type mixed-l3-acl does not contain
matches on fields in the ethernet header.";
}
identity mixed-l2-l3-acl {
base "access-control-list:acl-type-base";
description "ACL that contains a mix of entries that
primarily match on fields in ethernet headers, entries
that primarily match on fields in IPv4 headers,
and entries that primarily match on fields in IPv6
headers. Matching on layer 4 header fields may also
exist in the list.";
}
A.4. Linux nftables
As Linux platform is becoming more popular as networking platform, As Linux platform is becoming more popular as networking platform,
the Linux data model is changing. Previously ACLs in Linux were the Linux data model is changing. Previously ACLs in Linux were
highly protocol specific and different utilities were used (iptables, highly protocol specific and different utilities were used (iptables,
ip6tables, arptables, ebtables), so each one had separate data model. ip6tables, arptables, ebtables), so each one had separate data model.
Recently, this has changed and a single utility, nftables, has been Recently, this has changed and a single utility, nftables, has been
developed. With a single application, it has a single data model for developed. With a single application, it has a single data model for
filewall filters and it follows very similarly to the ietf-access- filewall filters and it follows very similarly to the ietf-access-
control list module proposed in this draft. The nftables support control list module proposed in this draft. The nftables support
input and output ACEs and each ACE can be defined with match and input and output ACEs and each ACE can be defined with match and
skipping to change at page 44, line 18 skipping to change at page 45, line 32
} }
} }
We can see that there are many similarities between Linux nftables We can see that there are many similarities between Linux nftables
and IETF ACL YANG data models and its extension models. It should be and IETF ACL YANG data models and its extension models. It should be
fairly easy to do translation between ACL YANG model described in fairly easy to do translation between ACL YANG model described in
this draft and Linux nftables. this draft and Linux nftables.
Authors' Addresses Authors' Addresses
Dean Bogdanovic
Volta Networks
Email: ivandean@gmail.com
Mahesh Jethanandani Mahesh Jethanandani
Cisco Systems, Inc Cisco Systems, Inc
Email: mjethanandani@gmail.com Email: mjethanandani@gmail.com
Lisa Huang Lisa Huang
General Electric General Electric
Email: lyihuang16@gmail.com Email: lyihuang16@gmail.com
Sonal Agarwal Sonal Agarwal
Cisco Systems, Inc. Cisco Systems, Inc.
Email: agarwaso@cisco.com Email: agarwaso@cisco.com
Dana Blair
Dana
Cisco Systems, INc Cisco Systems, INc
Email: dblair@cisco.com Email: dblair@cisco.com
 End of changes. 125 change blocks. 
407 lines changed or deleted 394 lines changed or added

This html diff was produced by rfcdiff 1.45. The latest version is available from http://tools.ietf.org/tools/rfcdiff/