draft-ietf-netmod-acl-model-17.txt   draft-ietf-netmod-acl-model-18.txt 
NETMOD WG M. Jethanandani NETMOD WG M. Jethanandani
Internet-Draft Internet-Draft
Intended status: Standards Track L. Huang Intended status: Standards Track L. Huang
Expires: September 4, 2018 General Electric Expires: September 16, 2018 General Electric
S. Agarwal S. Agarwal
D. Blair D. Blair
Cisco Systems, Inc. Cisco Systems, Inc.
March 3, 2018 March 15, 2018
Network Access Control List (ACL) YANG Data Model Network Access Control List (ACL) YANG Data Model
draft-ietf-netmod-acl-model-17 draft-ietf-netmod-acl-model-18
Abstract Abstract
This document defines a data model for Access Control List (ACL). This document defines a data model for Access Control List (ACL). An
ACL is a ordered-by-user set of rules, used to configure the ACL is a user-ordered set of rules, used to configure the forwarding
forwarding behavior in device. Each rule is used to find a match on behavior in device. Each rule is used to find a match on a packet,
a packet, and define actions that will be performed on the packet. and define actions that will be performed on the packet.
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 https://datatracker.ietf.org/drafts/current/. Drafts is at https://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 September 4, 2018. This Internet-Draft will expire on September 16, 2018.
Copyright Notice Copyright Notice
Copyright (c) 2018 IETF Trust and the persons identified as the Copyright (c) 2018 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
(https://trustee.ietf.org/license-info) in effect on the date of (https://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 13 skipping to change at page 2, line 13
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License. described in the Simplified BSD License.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
1.1. Definitions and Acronyms . . . . . . . . . . . . . . . . 4 1.1. Definitions and Acronyms . . . . . . . . . . . . . . . . 4
1.2. Terminology . . . . . . . . . . . . . . . . . . . . . . . 4 1.2. Terminology . . . . . . . . . . . . . . . . . . . . . . . 4
1.3. Tree Diagram . . . . . . . . . . . . . . . . . . . . . . 4
2. Problem Statement . . . . . . . . . . . . . . . . . . . . . . 4 2. Problem Statement . . . . . . . . . . . . . . . . . . . . . . 4
3. Understanding ACL's Filters and Actions . . . . . . . . . . . 4 3. Understanding ACL's Filters and Actions . . . . . . . . . . . 5
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 . . . . . . . . . . . . . . . . 24 4.2. IETF Packet Fields module . . . . . . . . . . . . . . . . 24
4.3. An ACL Example . . . . . . . . . . . . . . . . . . . . . 36 4.3. An ACL Example . . . . . . . . . . . . . . . . . . . . . 36
4.4. Port Range Usage Example . . . . . . . . . . . . . . . . 37 4.4. Port Range Usage and Other Examples . . . . . . . . . . . 37
5. Security Considerations . . . . . . . . . . . . . . . . . . . 40 5. Security Considerations . . . . . . . . . . . . . . . . . . . 41
6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 41 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 42
6.1. URI Registration . . . . . . . . . . . . . . . . . . . . 41 6.1. URI Registration . . . . . . . . . . . . . . . . . . . . 42
6.2. YANG Module Name Registration . . . . . . . . . . . . . . 41 6.2. YANG Module Name Registration . . . . . . . . . . . . . . 42
7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 42 7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 43
8. References . . . . . . . . . . . . . . . . . . . . . . . . . 42 8. References . . . . . . . . . . . . . . . . . . . . . . . . . 43
8.1. Normative References . . . . . . . . . . . . . . . . . . 42 8.1. Normative References . . . . . . . . . . . . . . . . . . 43
8.2. Informative References . . . . . . . . . . . . . . . . . 44 8.2. Informative References . . . . . . . . . . . . . . . . . 45
Appendix A. Extending ACL model examples . . . . . . . . . . . . 44 Appendix A. Extending ACL model examples . . . . . . . . . . . . 46
A.1. A company proprietary module example . . . . . . . . . . 44 A.1. A company proprietary module example . . . . . . . . . . 46
A.2. Linux nftables . . . . . . . . . . . . . . . . . . . . . 48 A.2. Linux nftables . . . . . . . . . . . . . . . . . . . . . 49
A.3. Ethertypes . . . . . . . . . . . . . . . . . . . . . . . 49 A.3. Ethertypes . . . . . . . . . . . . . . . . . . . . . . . 50
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 57 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 58
1. Introduction 1. Introduction
Access Control List (ACL) is one of the basic elements used to Access Control List (ACL) is one of the basic elements used to
configure device forwarding behavior. It is used in many networking configure device forwarding behavior. It is used in many networking
technologies such as Policy Based Routing, Firewalls etc. technologies such as Policy Based Routing, Firewalls etc.
An ACL is an ordered-by-user set of rules that is used to filter An ACL is an user-ordered set of rules, that is used to filter
traffic on a networking device. Each rule is represented by an traffic on a networking device. Each rule is represented by an
Access Control Entry (ACE). Access Control 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 allows for definition of packet headers and
and can have metadata match criteria as well. metadata, all of which must be true for the match to occur.
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 (CoS) or port numbers.
o In case vendor supports it, metadata matches apply to fields o In case a 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 capabilities of list of potential actions is unbounded depending on the capabilities
the networked devices. of the networking 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
using the match criteria in the ACE's and taking appropriate using the match criteria in the ACE's and taking appropriate
skipping to change at page 3, line 45 skipping to change at page 3, line 45
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 both in this o "XXXX" --> the assigned RFC value for this draft both in this
draft and in the YANG models under the revision statement. draft and in the YANG models under the revision statement.
o Revision date in model, in the format 2018-03-03 needs to get o Revision date in model, in the format 2018-03-15 needs to get
updated with the date the draft gets approved. The date also updated with the date the draft gets approved. The date also
needs to get reflected on the line with <CODE BEGINS>. needs to get reflected on the line with <CODE BEGINS>.
o Replace "I-D.ietf-netmod-yang-tree-diagrams" with the assigned RFC o Replace "I-D.ietf-netmod-yang-tree-diagrams" with the assigned RFC
number. number.
1.1. Definitions and Acronyms 1.1. Definitions and Acronyms
ACE: Access Control Entry ACE: Access Control Entry
ACL: Access Control List ACL: Access Control List
CoS: Class of Service
DSCP: Differentiated Services Code Point DSCP: Differentiated Services Code Point
ICMP: Internet Control Message Protocol ICMP: Internet Control Message Protocol
IP: Internet Protocol IP: Internet Protocol
IPv4: Internet Protocol version 4 IPv4: Internet Protocol version 4
IPv6: Internet Protocol version 6 IPv6: Internet Protocol version 6
skipping to change at page 4, line 35 skipping to change at page 4, line 37
UDP: User Datagram Protocol UDP: User Datagram Protocol
1.2. Terminology 1.2. Terminology
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
"OPTIONAL" in this document are to be interpreted as described in BCP "OPTIONAL" in this document are to be interpreted as described in BCP
14 [RFC2119] [RFC8174] when, and only when, they appear in all 14 [RFC2119] [RFC8174] when, and only when, they appear in all
capitals, as shown here. 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
[I-D.ietf-netmod-yang-tree-diagrams].
2. Problem Statement 2. Problem Statement
This document defines a YANG [RFC7950] data model for the This document defines a YANG [RFC7950] data model for the
configuration of ACLs. It is very important that model can be used configuration of ACLs. It is very important that model can be used
easily by applications/attachments. easily by applications/attachments.
ACL implementations in every device may vary greatly in terms of the ACL implementations in every device may vary greatly in terms of the
filter constructs and actions that they support. Therefore this filter constructs and actions that they support. Therefore this
draft proposes a model that can be augmented by standard extensions draft proposes a model that can be augmented by standard extensions
and vendor proprietary models. and vendor proprietary models.
3. Understanding ACL's Filters and Actions 3. Understanding ACL's Filters and Actions
Although different vendors have different ACL data models, there is a Although different vendors have different ACL data models, there is a
common understanding of what Access Control List (ACL) is. A network common understanding of what Access Control List (ACL) is. A network
system usually have a list of ACLs, and each ACL contains an ordered 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 list of rules, also known as Access Control Entries (ACE). Each ACE
has a group of match criteria and a group of action criteria. The has a group of match criteria and a group of action criteria. The
match criteria consist of packet header matching. It as also match criteria allows for definition of packet headers or metadata,
possible for ACE to match on metadata, if supported by the vendor. if supported by the vendor. Packet header matching applies to fields
Packet header matching applies to fields visible in the packet such visible in the packet such as address or CoS or port numbers.
as address or class of service or port numbers. Metadata matching Metadata matching applies to fields associated with the packet, but
applies to fields associated with the packet, but not in the packet not in the packet header such as input interface, packet length, or
header such as input interface, packet length, or source or source or destination prefix length. The actions can be any sort of
destination prefix length. The actions can be any sort of operation operation from logging to rate limiting or dropping to simply
from logging to rate limiting or dropping to simply forwarding. forwarding. Actions on the first matching ACE are applied with no
Actions on the first matching ACE are applied with no processing of processing of subsequent ACEs.
subsequent ACEs.
The model also includes a container to hold overall operational state The model also includes a container to hold overall operational state
for each ACL and operational state for each ACE. One ACL can be for each ACL and operational state for each ACE. One ACL can be
applied to multiple targets within the device, such as interfaces of applied to multiple targets within the device, such as interface of a
a networked device, applications or features running in the device, networking device, applications or features running in the device,
etc. When applied to interfaces of a networked device, the ACL is etc. When applied to interfaces of a networked device, distinct ACLs
applied in a direction which indicates if it should be applied to are defined for the ingress (input) or egress (output) interface.
packet entering (input) or leaving the device (output). An example
in the appendix shows how to express it in YANG model.
This draft tries to address the commonalities between all vendors and This draft tries to address the commonalities between all vendors and
create a common model, which can be augmented with proprietary create a common model, which can be augmented with proprietary
models. The base model is simple and with this design we hope to models. The base model is simple in design, and we hope to achieve
achieve enough flexibility for each vendor to extend the base model. enough flexibility for each vendor to extend the base model.
The use of feature statements in the model allows vendors to The use of feature statements in the model allows vendors to
advertise match rules they are capable and willing to support. There advertise match rules they are capable and willing to support. There
are two sets of feature statements a device needs to advertise. The are two sets of feature statements a device needs to advertise. The
first set of feature statements specify the capability of the device. first set of feature statements specify the capability of the device.
These include features such as "Device can support ethernet headers" These include features such as "Device can support ethernet headers"
or "Device can support of IPv4 headers". The second set of feature or "Device can support of IPv4 headers". The second set of feature
statements specify the combinations of headers the device is willing statements specify the combinations of headers the device is willing
to support. These include features such as "Plain IPv6 ACL to support. These include features such as "Plain IPv6 ACL
supported" or "Ethernet, IPv4 and IPv6 ACL combinations supported". supported" or "Ethernet, IPv4 and IPv6 ACL combinations supported".
3.1. ACL Modules 3.1. ACL Modules
There are two YANG modules in the model. The first module, "ietf- There are two YANG modules in the model. The first module, "ietf-
access-control-list", defines generic ACL aspects which are common to access-control-list", defines generic ACL aspects which are common to
all ACLs regardless of their type or vendor. In effect, the module all ACLs regardless of their type or vendor. In effect, the module
can be viewed as providing a generic ACL "superclass". It imports can be viewed as providing a generic ACL "superclass". It imports
the second module, "ietf-packet-fields". The match container in the second module, "ietf-packet-fields". The match container in
"ietf-access-control-list" uses groupings in "ietf-packet-fields" to "ietf-access-control-list" uses groupings in "ietf-packet-fields" to
specify match fields such as port numbers or protocol. The specify match fields such as port numbers or protocol. The
combination of if-feature checks and must statements allow for the combination of 'if-feature' checks and 'must' statements allow for
selection of relevant match fields that a user can define rules for. the selection of relevant match fields that a user can define rules
for.
If there is a need to define new "matches" choice, such as IPFIX If there is a need to define a new "matches" choice, such as IPFIX
[RFC7011], the container "matches" can be augmented. [RFC7011], the container "matches" can be augmented.
For a reference to the annotations used in the diagram below, see
YANG Tree Diagrams [I-D.ietf-netmod-yang-tree-diagrams].
module: ietf-access-control-list module: ietf-access-control-list
+--rw access-lists +--rw acls
+--rw acl* [name] +--rw acl* [name]
| +--rw name string | +--rw name string
| +--rw type? acl-type | +--rw type? acl-type
| +--rw aces | +--rw aces
| +--rw ace* [name] | +--rw ace* [name]
| +--rw name string | +--rw name string
| +--rw matches | +--rw matches
| | +--rw (l2)? | | +--rw (l2)?
| | | +--:(eth) | | | +--:(eth)
| | | +--rw eth {match-on-eth}? | | | +--rw eth {match-on-eth}?
skipping to change at page 9, line 10 skipping to change at page 9, line 11
| | +--rw logging? identityref | | +--rw logging? identityref
| +--ro statistics {acl-aggregate-stats}? | +--ro statistics {acl-aggregate-stats}?
| +--ro matched-packets? yang:counter64 | +--ro matched-packets? yang:counter64
| +--ro matched-octets? yang:counter64 | +--ro matched-octets? yang:counter64
+--rw attachment-points +--rw attachment-points
+--rw interface* [interface-id] {interface-attachment}? +--rw interface* [interface-id] {interface-attachment}?
+--rw interface-id if:interface-ref +--rw interface-id if:interface-ref
+--rw ingress +--rw ingress
| +--rw acl-sets | +--rw acl-sets
| +--rw acl-set* [name] | +--rw acl-set* [name]
| +--rw name -> /access-lists/acl/name | +--rw name -> /acls/acl/name
| +--ro ace-statistics* [name] {interface-stats}? | +--ro ace-statistics* [name] {interface-stats}?
| +--ro name | +--ro name
| | -> /access-lists/acl/aces/ace/name | | -> /acls/acl/aces/ace/name
| +--ro matched-packets? yang:counter64 | +--ro matched-packets? yang:counter64
| +--ro matched-octets? yang:counter64 | +--ro matched-octets? yang:counter64
+--rw egress +--rw egress
+--rw acl-sets +--rw acl-sets
+--rw acl-set* [name] +--rw acl-set* [name]
+--rw name -> /access-lists/acl/name +--rw name -> /acls/acl/name
+--ro ace-statistics* [name] {interface-stats}? +--ro ace-statistics* [name] {interface-stats}?
+--ro name +--ro name
| -> /access-lists/acl/aces/ace/name | -> /acls/acl/aces/ace/name
+--ro matched-packets? yang:counter64 +--ro matched-packets? yang:counter64
+--ro matched-octets? yang:counter64 +--ro matched-octets? yang:counter64
4. ACL YANG Models 4. ACL YANG Models
4.1. IETF Access Control List module 4.1. IETF Access Control List module
"ietf-access-control-list" is the standard top level module for "ietf-access-control-list" module defines the "acls" container that
access lists. The "access-lists" container stores a list of "acl". has a list of "acl". Each "acl" has information identifying the
Each "acl" has information identifying the access list by a name access list by a name ("name") and a list ("aces") of rules
("name") and a list ("aces") of rules associated with the "name". associated with the "name". Each of the entries in the list
Each of the entries in the list ("aces"), indexed by the string ("aces"), indexed by the string "name", has containers defining
"name", has containers defining "matches" and "actions". "matches" and "actions".
The model defines several ACL types and actions in the form of The model defines several ACL types and actions in the form of
identities and features. Features are used by implementors to select identities and features. Features are used by implementors to select
the ACL types the system can support and identities are used to the ACL types the system can support and identities are used to
validate the types that have been selected. These types are validate the types that have been selected. These types are
implicitly inherited by the "ace", thus safeguarding against implicitly inherited by the "ace", thus safeguarding against
misconfiguration of "ace" types in an "acl". misconfiguration of "ace" types in an "acl".
The "matches" define criteria used to identify patterns in "ietf- The "matches" define criteria used to identify patterns in "ietf-
packet-fields". The choice statements within the match container packet-fields". The choice statements within the match container
allow for selection of one header within each of "l2", "l3", or "l4" allow for selection of one header within each of "l2", "l3", or "l4"
headers. The "actions" define behavior to undertake once a "match" headers. The "actions" define behavior to undertake once a "match"
has been identified. In addition to permit and deny for actions, a has been identified. In addition to permit and deny for actions, a
logging option allows for a match to be logged that can be used to logging option allows for a match to be logged that can later be used
determine which rule was matched upon. The model also defines the to determine which rule was matched upon. The model also defines the
ability for ACL's to be attached to a particular interface. ability for ACLs to be attached to a particular interface.
Statistics in the ACL can be collected for an "ace" or for an Statistics in the ACL can be collected for an "ace" or for an
"interface". The feature statements defined for statistics can be "interface". The feature statements defined for statistics can be
used to determine whether statistics are being collected per "ace", used to determine whether statistics are being collected per "ace",
or per "interface". or per "interface".
This module imports definitions from Common YANG Data Types This module imports definitions from Common YANG Data Types
[RFC6991], and A YANG Data Model for Interface Management [RFC6991], and A YANG Data Model for Interface Management
[I-D.ietf-netmod-rfc7223bis]. [I-D.ietf-netmod-rfc7223bis].
<CODE BEGINS> file "ietf-access-control-list@2018-03-03.yang" <CODE BEGINS> file "ietf-access-control-list@2018-03-15.yang"
module ietf-access-control-list { module ietf-access-control-list {
yang-version 1.1; yang-version 1.1;
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;
reference reference
"RFC 6991 - Common YANG Data Types."; "RFC 6991 - Common YANG Data Types.";
skipping to change at page 10, line 41 skipping to change at page 10, line 43
} }
import ietf-interfaces { import ietf-interfaces {
prefix if; prefix if;
reference reference
"I-D.draft-ietf-netmod-rfc7223bis - A YANG Data Model for "I-D.draft-ietf-netmod-rfc7223bis - A YANG Data Model for
Interface Management."; Interface Management.";
} }
organization organization
"IETF NETMOD (NETCONF Data Modeling Language) "IETF NETMOD (Network 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: 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
sagarwal12@gmail.com sagarwal12@gmail.com
Editor: Dana Blair Editor: Dana Blair
dblair@cisco.com"; dblair@cisco.com";
description description
"This YANG module defines a component that describe the "This YANG module defines a component that describe the
configuration of Access Control Lists (ACLs). configuration of Access Control Lists (ACLs).
skipping to change at page 11, line 24 skipping to change at page 11, line 28
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 2018-03-03 { revision 2018-03-15 {
description description
"Initial version."; "Initial version.";
reference reference
"RFC XXX: Network Access Control List (ACL) YANG Data Model."; "RFC XXX: Network Access Control List (ACL) YANG Data Model.";
} }
/* /*
* Identities * Identities
*/ */
skipping to change at page 12, line 46 skipping to change at page 12, line 49
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-type { identity ipv4-acl-type {
base acl:acl-base; base acl:acl-base;
if-feature "ipv4"; if-feature "ipv4";
description description
"ACL that primarily matches on fields from the IPv4 header "An ACL that 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 does not contain destination port). An acl of type ipv4 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.";
} }
identity ipv6-acl-type { identity ipv6-acl-type {
base acl:acl-base; base acl:acl-base;
if-feature "ipv6"; if-feature "ipv6";
description description
"ACL that primarily matches on fields from the IPv6 header "An ACL that matches on fields from the IPv6 header
(e.g. IPv6 destination address) and layer 4 headers (e.g. TCP (e.g. IPv6 destination address) and layer 4 headers (e.g. TCP
destination port). An acl of type ipv6 does not contain destination port). An acl of type ipv6 does not contain
matches on fields in the ethernet header or the IPv4 header."; matches on fields in the ethernet header or the IPv4 header.";
} }
identity eth-acl-type { identity eth-acl-type {
base acl:acl-base; base acl:acl-base;
if-feature "eth"; if-feature "eth";
description description
"ACL that primarily matches on fields in the ethernet header, "An ACL that matches on fields in the ethernet header,
like 10/100/1000baseT or WiFi Access Control List. An acl of like 10/100/1000baseT or WiFi Access Control List. An acl of
type ethernet does not contain matches on fields in the IPv4 type ethernet does not contain matches on fields in the IPv4
header, IPv6 header or layer 4 headers."; header, IPv6 header or layer 4 headers.";
} }
identity mixed-eth-ipv4-acl-type { identity mixed-eth-ipv4-acl-type {
base "acl:eth-acl-type"; base "acl:eth-acl-type";
base "acl:ipv4-acl-type"; base "acl:ipv4-acl-type";
if-feature "mixed-eth-ipv4"; if-feature "mixed-eth-ipv4";
description description
"ACL that contains a mix of entries that "An ACL that contains a mix of entries that
primarily match on fields in ethernet headers, match on fields in ethernet headers,
entries that primarily match on IPv4 headers. entries that match on IPv4 headers.
Matching on layer 4 header fields may also exist in the Matching on layer 4 header fields may also exist in the
list."; list.";
} }
identity mixed-eth-ipv6-acl-type { identity mixed-eth-ipv6-acl-type {
base "acl:eth-acl-type"; base "acl:eth-acl-type";
base "acl:ipv6-acl-type"; base "acl:ipv6-acl-type";
if-feature "mixed-eth-ipv6"; if-feature "mixed-eth-ipv6";
description description
"ACL that contains a mix of entries that "ACL that contains a mix of entries that
primarily match on fields in ethernet headers, entries match on fields in ethernet headers, entries
that primarily match on fields in IPv6 headers. Matching on that match on fields in IPv6 headers. Matching on
layer 4 header fields may also exist in the list."; layer 4 header fields may also exist in the list.";
} }
identity mixed-eth-ipv4-ipv6-acl-type { identity mixed-eth-ipv4-ipv6-acl-type {
base "acl:eth-acl-type"; base "acl:eth-acl-type";
base "acl:ipv4-acl-type"; base "acl:ipv4-acl-type";
base "acl:ipv6-acl-type"; base "acl:ipv6-acl-type";
if-feature "mixed-eth-ipv4-ipv6"; if-feature "mixed-eth-ipv4-ipv6";
description description
"ACL that contains a mix of entries that "ACL that contains a mix of entries that
primarily match on fields in ethernet headers, entries match on fields in ethernet headers, entries
that primarily match on fields in IPv4 headers, and entries that match on fields in IPv4 headers, and entries
that primarily match on fields in IPv6 headers. Matching on that match on fields in IPv6 headers. Matching on
layer 4 header fields may also exist in the list."; layer 4 header fields may also exist in the list.";
} }
/* /*
* Features * Features
*/ */
/* /*
* Features supported by device * Features supported by device
*/ */
feature match-on-eth { feature match-on-eth {
description description
"Device can support matching on ethernet headers."; "The device can support matching on ethernet headers.";
} }
feature match-on-ipv4 { feature match-on-ipv4 {
description description
"Device can support matching on IPv4 headers."; "The device can support matching on IPv4 headers.";
} }
feature match-on-ipv6 { feature match-on-ipv6 {
description description
"Device can support matching on IPv6 headers."; "The device can support matching on IPv6 headers.";
} }
feature match-on-tcp { feature match-on-tcp {
description description
"Device can support TCP headers."; "The device can support TCP headers.";
} }
feature match-on-udp { feature match-on-udp {
description description
"Device can support UDP header."; "The device can support UDP header.";
} }
feature match-on-icmp { feature match-on-icmp {
description description
"Device can support ICMP header."; "The device can support ICMP header.";
} }
/* /*
* Header classifications combinations supported by * Header classifications combinations supported by
* device * device
*/ */
feature eth { feature eth {
if-feature "match-on-eth"; if-feature "match-on-eth";
description description
"Plain Ethernet ACL supported"; "Plain Ethernet ACL supported";
} }
skipping to change at page 17, line 31 skipping to change at page 17, line 33
An implementation that provides counters per entry per An implementation that provides counters per entry per
interface is not required to also provide an aggregate count, interface is not required to also provide an aggregate count,
e.g., per entry -- the user is expected to be able implement e.g., per entry -- the user is expected to be able implement
the required aggregation if such a count is needed."; the required aggregation if such a count is needed.";
} }
} }
/* /*
* Configuration data nodes * Configuration data nodes
*/ */
container access-lists { container acls {
description description
"This is a top level container for Access Control Lists. "This is a top level container for Access Control Lists.
It can have one or more Access Control Lists."; It can have one or more acl nodes.";
list acl { list acl {
key "name"; key "name";
description description
"An Access Control List(ACL) is an ordered list of "An Access Control List (ACL) is an ordered list of
Access List Entries (ACE). Each Access Control Entry has a Access Control Entries (ACE). Each ACE has a
list of match criteria and a list of actions. list of match criteria and a list of actions.
Since there are several kinds of Access Control Lists Since there are several kinds of Access Control Lists
implemented with different attributes for implemented with different attributes for
different vendors, this model accommodates customizing different vendors, this model accommodates customizing
Access Control Lists for each kind and for each vendor."; Access Control Lists for each kind and, for each vendor.";
leaf name { leaf name {
type string { type string {
length "1..64"; length "1..64";
} }
description description
"The name of access-list. A device MAY restrict the length "The name of access list. A device MAY restrict the length
and value of this name, possibly space and special and value of this name, possibly space and special
characters are not allowed."; characters are not allowed.";
} }
leaf type { leaf type {
type acl-type; type acl-type;
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 aces { container aces {
description description
"The access-list-entries container contains "The aces container contains one or more ace nodes.";
a list of access-list-entries(ACE).";
list ace { list ace {
key "name"; key "name";
ordered-by user; ordered-by user;
description description
"List of access list entries(ACE)"; "List of Access Control Entries (ACEs)";
leaf name { leaf name {
type string { type string {
length "1..64"; length "1..64";
} }
description description
"A unique name identifying this Access List "A unique name identifying this Access Control
Entry(ACE)."; Entry (ACE).";
} }
container matches { container matches {
description description
"The rules in this set determine what fields will be "The rules in this set determine what fields will be
matched upon before any action is taken on them. matched upon before any action is taken on them.
The rules are selected based on the feature set The rules are selected based on the feature set
defined by the server and the acl-type defined. defined by the server and the acl-type defined.
If no matches are defined in a particular container, If no matches are defined in a particular container,
then any packet will match that container. If no then any packet will match that container. If no
matches are specified at all in an ACE, then any matches are specified at all in an ACE, then any
packet will match the ACE."; packet will match the ACE.";
choice l2 { choice l2 {
container eth { container eth {
when "derived-from-or-self(../../../../type, " + when "derived-from-or-self(/acls/acl/type, " +
"'acl:eth-acl-type')"; "'acl:eth-acl-type')";
if-feature match-on-eth; if-feature match-on-eth;
uses pf:acl-eth-header-fields; uses pf:acl-eth-header-fields;
description description
"Rule set that matches ethernet headers."; "Rule set that matches ethernet headers.";
} }
description description
"Match layer 2 headers, for example ethernet "Match layer 2 headers, for example ethernet
header fields."; header fields.";
} }
choice l3 { choice l3 {
container ipv4 { container ipv4 {
when "derived-from-or-self(../../../../type, " + when "derived-from-or-self(/acls/acl/type, " +
"'acl:ipv4-acl-type')"; "'acl:ipv4-acl-type')";
if-feature match-on-ipv4; if-feature match-on-ipv4;
uses pf:acl-ip-header-fields; uses pf:acl-ip-header-fields;
uses pf:acl-ipv4-header-fields; uses pf:acl-ipv4-header-fields;
description description
"Rule set that matches IPv4 headers."; "Rule set that matches IPv4 headers.";
} }
container ipv6 { container ipv6 {
when "derived-from-or-self(../../../../type, " + when "derived-from-or-self(/acls/acl/type, " +
"'acl:ipv6-acl-type')"; "'acl:ipv6-acl-type')";
if-feature match-on-ipv6; if-feature match-on-ipv6;
uses pf:acl-ip-header-fields; uses pf:acl-ip-header-fields;
uses pf:acl-ipv6-header-fields; uses pf:acl-ipv6-header-fields;
description description
"Rule set that matches IPv6 headers."; "Rule set that matches IPv6 headers.";
} }
description description
"Choice of either ipv4 or ipv6 headers"; "Choice of either ipv4 or ipv6 headers";
} }
skipping to change at page 19, line 46 skipping to change at page 19, line 47
container source-port { container source-port {
choice source-port { choice source-port {
case range-or-operator { case range-or-operator {
uses pf:port-range-or-operator; uses pf:port-range-or-operator;
description description
"Source port definition from range or "Source port definition from range or
operator."; operator.";
} }
description description
"Choice of source port definition using "Choice of source port definition using
range/operator or referring to a group of range/operator or a choice to support future
source ports"; 'case' statements, such as one enabling a
group of source ports to be referenced.";
} }
description description
"Source port definition."; "Source port definition.";
} }
container destination-port { container destination-port {
choice destination-port { choice destination-port {
case range-or-operator { case range-or-operator {
uses pf:port-range-or-operator; uses pf:port-range-or-operator;
description description
"Destination port definition from range or "Destination port definition from range or
operator."; operator.";
} }
description description
"Choice of destination port definition using "Choice of destination port definition using
range/operator or referring to a group of range/operator or a choice to support future
destination ports."; 'case' statements, such as one enabling a
group of destination ports to be referenced.";
} }
description description
"Destination port definition."; "Destination port definition.";
} }
description description
"Rule set that matches TCP headers."; "Rule set that matches TCP headers.";
} }
container udp { container udp {
if-feature match-on-udp; if-feature match-on-udp;
skipping to change at page 20, line 37 skipping to change at page 20, line 40
container source-port { container source-port {
choice source-port { choice source-port {
case range-or-operator { case range-or-operator {
uses pf:port-range-or-operator; uses pf:port-range-or-operator;
description description
"Source port definition from range or "Source port definition from range or
operator."; operator.";
} }
description description
"Choice of source port definition using "Choice of source port definition using
range/operator or referring to a group of range/operator or a choice to support future
source ports."; 'case' statements, such as one enabling a
group of source ports to be referenced.";
} }
description description
"Source port definition."; "Source port definition.";
} }
container destination-port { container destination-port {
choice destination-port { choice destination-port {
case range-or-operator { case range-or-operator {
uses pf:port-range-or-operator; uses pf:port-range-or-operator;
description description
"Destination port definition from range or "Destination port definition from range or
operator."; operator.";
} }
description description
"Choice of destination port definition using "Choice of destination port definition using
range/operator or referring to a group of range/operator or a choice to support future
destination ports."; 'case' statements, such as one enabling a
group of destination ports to be referenced.";
} }
description description
"Destination port definition."; "Destination port definition.";
} }
description description
"Rule set that matches UDP headers."; "Rule set that matches UDP headers.";
} }
container icmp { container icmp {
if-feature match-on-icmp; if-feature match-on-icmp;
skipping to change at page 23, line 5 skipping to change at page 23, line 10
interface"; interface";
list acl-set { list acl-set {
key "name"; key "name";
ordered-by user; ordered-by user;
description description
"List of ingress ACLs on the interface"; "List of ingress ACLs on the interface";
leaf name { leaf name {
type leafref { type leafref {
path "/access-lists/acl/name"; path "/acls/acl/name";
} }
description description
"Reference to the ACL name applied on ingress"; "Reference to the ACL name applied on ingress";
} }
list ace-statistics { list ace-statistics {
if-feature "interface-stats"; if-feature "interface-stats";
key "name"; key "name";
config false; config false;
description description
"List of access list entries(ACE)"; "List of Access Control Entries (ACEs)";
leaf name { leaf name {
type leafref { type leafref {
path "/access-lists/acl/aces/ace/name"; path "/acls/acl/aces/ace/name";
} }
description description
"The ace name"; "The ace name";
} }
uses acl-counters; uses acl-counters;
} }
} }
} }
} }
skipping to change at page 23, line 45 skipping to change at page 23, line 50
leaf interface-id { leaf interface-id {
type if:interface-ref; type if:interface-ref;
description description
"Reference to the interface id list key"; "Reference to the interface id list key";
} }
container ingress { container ingress {
uses interface-acl; uses interface-acl;
description description
"The ACL's applied to ingress interface"; "The ACLs applied to ingress interface";
} }
container egress { container egress {
uses interface-acl; uses interface-acl;
description description
"The ACL's applied to egress interface"; "The ACLs applied to egress interface";
} }
} }
} }
} }
} }
<CODE ENDS> <CODE ENDS>
4.2. IETF Packet Fields module 4.2. IETF Packet Fields module
The packet fields module defines the necessary groups for matching on The packet fields module defines the necessary groups for matching on
skipping to change at page 24, line 22 skipping to change at page 24, line 26
4.2. IETF Packet Fields module 4.2. IETF Packet Fields module
The packet fields module defines the necessary groups for matching on The packet fields module defines the necessary groups for matching on
fields in the packet including ethernet, ipv4, ipv6, and transport fields in the packet including ethernet, ipv4, ipv6, and transport
layer fields. The "type" node determines which of these fields get layer fields. The "type" node determines which of these fields get
included for any given ACL with the exception of TCP, UDP and ICMP 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 header fields. Those fields can be used in conjunction with any of
the above layer 2 or layer 3 fields. 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' statement to
base module simple. In case more match conditions are needed, those keep the base module simple. In case more match conditions are
can be added by augmenting choices within container "matches" in needed, those can be added by augmenting choices within container
ietf-access-control-list.yang model. "matches" in ietf-access-control-list.yang model.
This module imports definitions from Common YANG Data Types [RFC6991] This module imports definitions from Common YANG Data Types [RFC6991]
and references IP [RFC0791], ICMP [RFC0792], Definition of the and references IP [RFC0791], ICMP [RFC0792], Definition of the
Differentiated Services Field in the IPv4 and IPv6 Headers [RFC2474], Differentiated Services Field in the IPv4 and IPv6 Headers [RFC2474],
The Addition of Explicit Congestion Notification (ECN) to IP The Addition of Explicit Congestion Notification (ECN) to IP
[RFC3168], , IPv6 Scoped Address Architecture [RFC4007], IPv6 [RFC3168], , IPv6 Scoped Address Architecture [RFC4007], IPv6
Addressing Architecture [RFC4291], A Recommendation for IPv6 Address Addressing Architecture [RFC4291], A Recommendation for IPv6 Address
Text Representation [RFC5952], IPv6 [RFC8200]. Text Representation [RFC5952], IPv6 [RFC8200].
<CODE BEGINS> file "ietf-packet-fields@2018-03-03.yang" <CODE BEGINS> file "ietf-packet-fields@2018-03-15.yang"
module ietf-packet-fields { module ietf-packet-fields {
yang-version 1.1; yang-version 1.1;
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;
reference reference
"RFC 6991 - Common YANG Data Types."; "RFC 6991 - Common YANG Data Types.";
skipping to change at page 24, line 47 skipping to change at page 25, line 4
module ietf-packet-fields { module ietf-packet-fields {
yang-version 1.1; yang-version 1.1;
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;
reference reference
"RFC 6991 - Common YANG Data Types."; "RFC 6991 - Common YANG Data Types.";
} }
import ietf-yang-types { import ietf-yang-types {
prefix yang; prefix yang;
reference reference
"RFC 6991 - Common YANG Data Types."; "RFC 6991 - Common YANG Data Types.";
} }
import ietf-ethertypes { import ietf-ethertypes {
prefix eth; prefix eth;
reference reference
"RFC XXXX - Network ACL YANG Model."; "RFC XXXX - Network ACL YANG Model.";
} }
organization organization
"IETF NETMOD (NETCONF Data Modeling Language) Working "IETF NETMOD (Network 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: Mahesh Jethanandani Editor: Mahesh Jethanandani
mjethanandani@gmail.com mjethanandani@gmail.com
Editor: Lisa Huang Editor: Lisa Huang
lyihuang16@gmail.com lyihuang16@gmail.com
skipping to change at page 25, line 45 skipping to change at page 25, line 51
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 2018-03-03 { revision 2018-03-15 {
description description
"Initial version."; "Initial version.";
reference reference
"RFC XXX: Network Access Control List (ACL) YANG Data Model."; "RFC XXX: Network Access Control List (ACL) YANG Data Model.";
} }
/* /*
* Typedefs * Typedefs
*/ */
typedef operator { typedef operator {
type enumeration { type enumeration {
enum lte { enum lte {
description description
"Less than or equal."; "Less than or equal.";
} }
enum gte { enum gte {
skipping to change at page 27, line 38 skipping to change at page 27, line 45
} }
description description
"Grouping for port definitions in the form of a "Grouping for port definitions in the form of a
choice statement."; choice statement.";
} }
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: Internet Protocol.";
leaf dscp { leaf dscp {
type inet:dscp; type inet:dscp;
description description
"Differentiated Services Code Point."; "Differentiated Services Code Point.";
reference reference
"RFC 2474: Definition of Differentiated services field "RFC 2474: Definition of Differentiated services field
(DS field) in the IPv4 and IPv6 headers."; (DS field) in the IPv4 and IPv6 headers.";
} }
skipping to change at page 28, line 4 skipping to change at page 28, line 10
description description
"Differentiated Services Code Point."; "Differentiated Services Code Point.";
reference reference
"RFC 2474: Definition of Differentiated services field "RFC 2474: Definition of Differentiated services field
(DS field) in the IPv4 and IPv6 headers."; (DS field) in the IPv4 and IPv6 headers.";
} }
leaf ecn { leaf ecn {
type uint8 { type uint8 {
range 0..3; range 0..3;
} }
description description
"Explicit Congestion Notification."; "Explicit Congestion Notification.";
reference reference
"RFC 3168."; "RFC 3168: Explicit Congestion Notification.";
} }
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
Length, the length of the IPv6 payload, i.e. the rest of Length, the length of the IPv6 payload, i.e. the rest of
the packet following the IPv6 header, in octets."; the packet following the IPv6 header, in octets.";
reference reference
"RFC 791, RFC 2460"; "RFC 791: Internet Protocol,
RFC 8200: IPv6.";
} }
leaf ttl { leaf ttl {
type uint8; type uint8;
description description
"This field indicates the maximum time the datagram is allowed "This field indicates the maximum time the datagram is allowed
to remain in the internet system. If this field contains the to remain in the internet system. If this field contains the
value zero, then the datagram must be destroyed. value zero, then the datagram must be dropped.
In IPv6, this field is known as the Hop Limit."; In IPv6, this field is known as the Hop Limit.";
reference "RFC 791, RFC 2460"; reference
"RFC 791: Internet Protocol,
RFC 8200: IPv6.";
} }
leaf protocol { leaf protocol {
type uint8; type uint8;
description description
"Internet Protocol number. Refers to the protocol of the "Internet Protocol number. Refers to the protocol of the
payload. In IPv6, this field is known as 'next-header."; payload. In IPv6, this field is known as 'next-header.";
reference "RFC 791, RFC 2460."; reference
"RFC 791: Internet Protocol,
RFC 8200: IPv6.";
} }
} }
grouping acl-ipv4-header-fields { grouping acl-ipv4-header-fields {
description description
"Fields in IPv4 header."; "Fields in IPv4 header.";
leaf ihl { leaf ihl {
type uint8 { type uint8 {
range "5..60"; range "5..60";
skipping to change at page 33, line 4 skipping to change at page 33, line 16
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 bits { type bits {
bit cwr { bit cwr {
position 1; position 1;
description description
"Congestion Window Reduced (CWR) flag is set by "Congestion Window Reduced (CWR) flag is set by
the sending host to indicate that it received the sending host to indicate that it received
a TCP segment with the ECE flag set and had a TCP segment with the ECE flag set and had
responded in congestion control mechanism."; responded in congestion control mechanism.";
reference "RFC 3168"; reference
"RFC 3168: Explicit Congestion Notification.";
} }
bit ece { bit ece {
position 2; position 2;
description description
"ECN-Echo has a dual role, depending on the value "ECN-Echo has a dual role, depending on the value
of the SYN flag. It indicates: of the SYN flag. It indicates:
If the SYN flag is set (1), that the TCP peer is ECN If the SYN flag is set (1), that the TCP peer is ECN
capable. If the SYN flag is clear (0), that a packet capable. If the SYN flag is clear (0), that a packet
with Congestion Experienced flag set (ECN=11) in IP with Congestion Experienced flag set (ECN=11) in IP
header was received during normal transmission header was received during normal transmission
(added to header by RFC 3168). This serves as an (added to header by RFC 3168). This serves as an
indication of network congestion (or impending indication of network congestion (or impending
congestion) to the TCP sender."; congestion) to the TCP sender.";
reference
"RFC 3168: Explicit Congestion Notification.";
} }
bit urg { bit urg {
position 3; position 3;
description description
"Indicates that the Urgent pointer field is significant."; "Indicates that the Urgent pointer field is significant.";
} }
bit ack { bit ack {
position 4; position 4;
description description
"Indicates that the Acknowledgment field is significant. "Indicates that the Acknowledgment field is significant.
skipping to change at page 34, line 20 skipping to change at page 34, line 36
and others when it is clear."; and others when it is clear.";
} }
bit fin { bit fin {
position 8; position 8;
description description
"Last package from sender."; "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.";
reference
"RFC 793: TCP.";
} }
leaf window-size { leaf window-size {
type uint16; type uint16;
units "bytes";
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 beyond the segment
bytes) (beyond the segment identified by the identified by the sequence number in the acknowledgment
sequence number in the acknowledgment field) 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 is 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.";
} }
skipping to change at page 35, line 45 skipping to change at page 36, line 16
grouping acl-icmp-header-fields { grouping acl-icmp-header-fields {
description description
"Collection of ICMP header fields that can be "Collection of ICMP header fields that can be
used to setup a match filter."; used to setup a match filter.";
leaf type { leaf type {
type uint8; type uint8;
description description
"Also known as Control messages."; "Also known as Control messages.";
reference "RFC 792"; reference
"RFC 792: ICMP.";
} }
leaf code { leaf code {
type uint8; type uint8;
description description
"ICMP subtype. Also known as Control messages."; "ICMP subtype. Also known as Control messages.";
} }
leaf rest-of-header { leaf rest-of-header {
type uint32; type uint32;
description description
"Four-bytes field, contents vary based on the "Four-bytes field, contents vary based on the
ICMP type and code."; ICMP type and code.";
} }
} }
} }
skipping to change at page 36, line 25 skipping to change at page 37, line 5
<CODE ENDS> <CODE ENDS>
4.3. An ACL Example 4.3. An ACL Example
Requirement: Deny tcp traffic from 192.0.2.0/24, destined to Requirement: Deny tcp traffic from 192.0.2.0/24, destined to
198.51.100.0/24. 198.51.100.0/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"?> [note: '\' line wrapping for formatting only]
<config xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
<access-lists xmlns="urn:ietf:params:xml:ns:yang:ietf-access-control-list"> <?xml version="1.0" encoding="UTF-8"?>
<acl> <config xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
<name>sample-ipv4-acl</name> <acls
<type>ipv4-acl-type</type> xmlns="urn:ietf:params:xml:ns:yang:ietf-access-control-list">
<aces> <acl>
<ace> <name>sample-ipv4-acl</name>
<name>rule1</name> <type>ipv4-acl-type</type>
<matches> <aces>
<ipv4> <ace>
<protocol>6</protocol> <name>rule1</name>
<destination-ipv4-network>192.0.2.0/24</destination-ipv4-network> <matches>
<source-ipv4-network>198.51.100.0/24</source-ipv4-network> <ipv4>
</ipv4> <protocol>6</protocol>
</matches> <destination-ipv4-network>198.51.100.0/24</destination\
<actions> -ipv4-network>
<forwarding>drop</forwarding> <source-ipv4-network>192.0.2.0/24</source-ipv4-network\
</actions> >
</ace> </ipv4>
</aces> </matches>
</acl> <actions>
</access-lists> <forwarding>drop</forwarding>
</config> </actions>
</ace>
</aces>
</acl>
</acls>
</config>
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 acl ipv4 sample-ipv4-acl
deny tcp 192.0.2.0/24 198.51.100.0/24 deny tcp 192.0.2.0/24 198.51.100.0/24
4.4. Port Range Usage Example 4.4. Port Range Usage and Other Examples
When a lower-port and an upper-port are both present, it represents a When a lower-port and an upper-port are both present, it represents a
range between lower-port and upper-port with both the lower-port and range between lower-port and upper-port with both the lower-port and
upper-port are included. When only a lower-port presents, it upper-port included. When only a port is present, it represents a
represents a single port. port, with the operator specifying the range.
With the follow XML example: The following XML example represents a configuration where traffic to
source ports 16384, 16385, 16386, and 16387 is dropped.
<?xml version="1.0" encoding="UTF-8"?> [note: '\' line wrapping for formatting only]
<config xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
<access-lists 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>
<source-port>
<lower-port>16384</lower-port>
<upper-port>16387</upper-port>
</source-port>
</tcp>
</matches>
<actions>
<forwarding>drop</forwarding>
</actions>
</ace>
</aces>
</acl>
</access-lists>
</config>
This represents source ports 16384, 16385, 16386, and 16387. <?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-port-acl</name>
<type>ipv4-acl-type</type>
<aces>
<ace>
<name>rule1</name>
<matches>
<tcp>
<source-port>
<lower-port>16384</lower-port>
<upper-port>16387</upper-port>
</source-port>
</tcp>
</matches>
<actions>
<forwarding>drop</forwarding>
</actions>
</ace>
</aces>
</acl>
</acls>
</config>
With the follow XML example: The following XML example represents a configuration where all ping
echo requests are dropped.
<?xml version="1.0" encoding="UTF-8"?> [note: '\' line wrapping for formatting only]
<config xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
<access-lists 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>
<source-port>
<lower-port>16384</lower-port>
<upper-port>65535</upper-port>
</source-port>
</tcp>
</matches>
<actions>
<forwarding>drop</forwarding>
</actions>
</ace>
</aces>
</acl>
</access-lists>
</config>
This represents source ports greater than or equal to 16384 and less <?xml version="1.0" encoding="UTF-8"?>
than equal to 65535. <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-icmp-acl</name>
<aces>
<ace>
<name>rule1</name>
<matches>
<icmp>
<type>8</type>
<code>0</code>
</icmp>
</matches>
<actions>
<forwarding>drop</forwarding>
</actions>
</ace>
</aces>
</acl>
</acls>
</config>
With the follow XML example: The following XML example represents a configuration of a single
port, port 21 that accepts traffic.
<?xml version="1.0" encoding="UTF-8"?> [note: '\' line wrapping for formatting only]
<config xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
<access-lists 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>
<source-port>
<operator>eq</operator>
<port>21</port>
</source-port>
</tcp>
</matches>
<actions>
<forwarding>drop</forwarding>
</actions>
</ace>
</aces>
</acl>
</access-lists>
</config>
This represents port 21. <?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>
<source-port>
<operator>eq</operator>
<port>21</port>
</source-port>
</tcp>
</matches>
<actions>
<forwarding>accept</forwarding>
</actions>
</ace>
</aces>
</acl>
</acls>
</config>
With the following XML example, the configuration is specifying all The following XML example represents a configuration specifying all
ports that are not equal to 21. ports that are not equal to 21, that will drop packets destined for
those ports.
<?xml version="1.0" encoding="UTF-8"?> [note: '\' line wrapping for formatting only]
<config xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
<access-lists xmlns="urn:ietf:params:xml:ns:yang:ietf-access-control-list"> <?xml version="1.0" encoding="UTF-8"?>
<acl> <config xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
<name>sample-ipv4-acl</name> <acls
<type>ipv4-acl-type</type> xmlns="urn:ietf:params:xml:ns:yang:ietf-access-control-list">
<aces> <acl>
<ace> <name>sample-ipv4-acl</name>
<name>rule1</name> <type>ipv4-acl-type</type>
<matches> <aces>
<tcp> <ace>
<source-port> <name>rule1</name>
<operator>neq</operator> <matches>
<port>21</port> <tcp>
</source-port> <source-port>
</tcp> <operator>neq</operator>
</matches> <port>21</port>
<actions> </source-port>
<forwarding>drop</forwarding> </tcp>
</actions> </matches>
</ace> <actions>
</aces> <forwarding>drop</forwarding>
</acl> </actions>
</access-lists> </ace>
</config> </aces>
</acl>
</acls>
</config>
5. Security Considerations 5. Security Considerations
The YANG module specified in this document defines a schema for data The YANG module specified in this document defines a schema for data
that is designed to be accessed via network management protocol such that is designed to be accessed via network management protocol such
as NETCONF [RFC6241] or RESTCONF [RFC8040]. The lowest NETCONF layer as NETCONF [RFC6241] or RESTCONF [RFC8040]. The lowest NETCONF layer
is the secure transport layer and the mandatory-to-implement secure is the secure transport layer and the mandatory-to-implement secure
transport is SSH [RFC6242]. The lowest RESTCONF layer is HTTPS, and transport is SSH [RFC6242]. The lowest RESTCONF layer is HTTPS, and
the mandatory-to-implement secure transport is TLS [RFC5246]. the mandatory-to-implement secure transport is TLS [RFC5246].
skipping to change at page 41, line 8 skipping to change at page 42, line 10
There are a number of data nodes defined in the YANG module which are There are a number of data nodes defined in the YANG module which are
writable/creatable/deletable (i.e., config true, which is the writable/creatable/deletable (i.e., config true, which is the
default). These data nodes may be considered sensitive or vulnerable default). These data nodes may be considered sensitive or vulnerable
in some network environments. Write operations (e.g., <edit-config>) in some network environments. Write operations (e.g., <edit-config>)
to these data nodes without proper protection can have a negative to these data nodes without proper protection can have a negative
effect on network operations. effect on network operations.
These are the subtrees and data nodes and their sensitivity/ These are the subtrees and data nodes and their sensitivity/
vulnerability: vulnerability:
/access-lists/acl/aces: This list specifies all the configured /acls/acl/aces: This list specifies all the configured access
access control entries on the device. Unauthorized write access control entries on the device. Unauthorized write access to this
to this list can allow intruders to access and control the system. list can allow intruders to access and control the system.
Unauthorized read access to this list can allow intruders to spoof Unauthorized read access to this list can allow intruders to spoof
packets with authorized addresses thereby compromising the system. packets with authorized addresses thereby compromising the system.
6. IANA Considerations 6. IANA Considerations
This document registers three URIs and three YANG module. This document registers three URIs and three YANG modules.
6.1. URI Registration 6.1. URI Registration
This document registers three URI in the IETF XML registry [RFC3688]. This document registers three URIs in the IETF XML registry
Following the format in RFC 3688, the following registration is [RFC3688]. Following the format in RFC 3688, the following
requested to be made: 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-access-control-list
URI: urn:ietf:params:xml:ns:yang:ietf-packet-fields URI: urn:ietf:params:xml:ns:yang:ietf-packet-fields
URI: urn:ietf:params:xml:ns:yang:ietf-ethertypes URI: urn:ietf:params:xml:ns:yang:ietf-ethertypes
Registrant Contact: The IESG. Registrant Contact: The IESG.
XML: N/A, the requested URI is an XML namespace. XML: N/A, the requested URI is an XML namespace.
6.2. YANG Module Name Registration 6.2. YANG Module Name Registration
skipping to change at page 45, line 7 skipping to change at page 46, line 23
A.1. A company proprietary module example A.1. A company proprietary module example
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 are found. All criteria, and default actions when no ACE matches are found. All
these are company proprietary extensions or system feature these are company proprietary extensions or system feature
extensions. "example-newco-acl" is just an example and it is extensions. "example-newco-acl" is just an example and it is
expected that vendors will create their own proprietary models. expected that vendors will create their own proprietary models.
[note: '\' line wrapping for formatting only]
module example-newco-acl { module example-newco-acl {
yang-version 1.1; yang-version 1.1;
namespace "http://example.com/ns/example-newco-acl"; namespace "http://example.com/ns/example-newco-acl";
prefix example-newco-acl; prefix example-newco-acl;
import ietf-access-control-list { import ietf-access-control-list {
prefix "acl"; prefix "acl";
} }
organization organization
"Newco model group."; "Newco model group.";
contact contact
"abc@newco.com"; "abc@newco.com";
description description
"This YANG module augments IETF ACL Yang."; "This YANG module augments IETF ACL Yang.";
revision 2018-03-03 { revision 2018-03-15 {
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";
} }
augment "/acl:acls/acl:acl/" +
augment "/acl:access-lists/acl:acl/" +
"acl:aces/acl:ace/" + "acl:aces/acl:ace/" +
"acl:matches" { "acl:matches" {
description "Newco proprietary simple filter matches"; description "Newco proprietary simple filter matches";
choice protocol-payload-choice { choice protocol-payload-choice {
description "Newco proprietary payload match condition"; description "Newco 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 46, line 11 skipping to change at page 47, line 27
choice metadata { choice metadata {
description "Newco proprietary interface match condition"; description "Newco proprietary interface match condition";
leaf packet-length { leaf packet-length {
type uint16; type uint16;
description "Match on packet length"; description "Match on packet length";
} }
} }
} }
augment "/acl:access-lists/acl:acl/" + augment "/acl:acls/acl:acl/" +
"acl:aces/acl:ace/" + "acl:aces/acl:ace/" +
"acl:actions" { "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 uint32; type uint32;
description "Count"; description "Count";
skipping to change at page 46, line 36 skipping to change at page 48, line 4
leaf policer { leaf policer {
type string; type string;
description "Name of the policer"; description "Name of the policer";
} }
} }
case hiearchical-policer { case hiearchical-policer {
leaf hierarchitacl-policer { leaf hierarchitacl-policer {
type string; type string;
description description
"Name of the hierarchical policer."; "Name of the hierarchical policer.";
} }
description description
"Name of hierarchical policer to use to "Name of hierarchical policer to use to
rate-limit traffic"; rate-limit traffic";
} }
} }
} }
augment "/acl:access-lists/acl:acl" + augment "/acl:acls/acl:acl" +
"/acl:aces/acl:ace/" + "/acl:aces/acl:ace/" +
"acl:actions" { "acl:actions" {
leaf default-action { leaf default-action {
type identityref { type identityref {
base acl:forwarding-action; base acl:forwarding-action;
} }
default acl:drop; default acl:drop;
description description
"Actions that occur if no ace is matched."; "Actions that occur if no ace is matched.";
} }
skipping to change at page 47, line 19 skipping to change at page 48, line 36
} }
grouping match-simple-payload-protocol-value { grouping match-simple-payload-protocol-value {
description "Newco proprietary payload"; description "Newco proprietary payload";
leaf value-keyword { leaf value-keyword {
type enumeration { type enumeration {
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)";
} }
} }
} }
The following figure is the tree structure of example-newco-acl. In The following figure is the tree diagram of example-newco-acl. In
this example, /ietf-acl:access-lists/ietf-acl:acl/ietf-acl:aces/ietf- this example, /ietf-acl:acls/ietf-acl:acl/ietf-acl:aces/ietf-acl:ace/
acl:ace/ietf-acl:matches are augmented with two new choices, ietf-acl:matches are augmented with two new choices, protocol-
protocol-payload-choice and metadata. The protocol-payload-choice payload-choice and metadata. The protocol-payload-choice uses a
uses a grouping with an enumeration of all supported protocol values. grouping with an enumeration of all supported protocol values.
Metadata matches apply to fields associated with the packet but not Metadata matches apply to fields associated with the packet but not
in the packet header such as overall packet length. In other in the packet header such as overall packet length. In another
example, /ietf-acl:access-lists/ietf-acl:acl/ietf-acl:aces/ietf- example, /ietf-acl:acls/ietf-acl:acl/ietf-acl:aces/ietf-acl:ace/ietf-
acl:ace/ietf-acl:actions are augmented with new choice of actions. acl:actions are augmented with a new choice of actions.
[note: '\' line wrapping for formatting only]
module: example-newco-acl module: example-newco-acl
augment /acl:access-lists/acl:acl/acl:aces/acl:ace/acl:matches: augment /acl:acls/acl:acl/acl:aces/acl:ace/acl:matches:
+--rw (protocol-payload-choice)? +--rw (protocol-payload-choice)?
| +--:(protocol-payload) | +--:(protocol-payload)
| +--rw protocol-payload* [value-keyword] | +--rw protocol-payload* [value-keyword]
| +--rw value-keyword enumeration | +--rw value-keyword enumeration
+--rw (metadata)? +--rw (metadata)?
+--:(packet-length) +--:(packet-length)
+--rw packet-length? uint16 +--rw packet-length? uint16
augment /acl:access-lists/acl:acl/acl:aces/acl:ace/acl:actions: augment /acl:acls/acl:acl/acl:aces/acl:ace/acl:actions:
+--rw (action)? +--rw (action)?
+--:(count) +--:(count)
| +--rw count? uint32 | +--rw count? uint32
+--:(policer) +--:(policer)
| +--rw policer? string | +--rw policer? string
+--:(hiearchical-policer) +--:(hiearchical-policer)
+--rw hierarchitacl-policer? string +--rw hierarchitacl-policer? string
augment /acl:access-lists/acl:acl/acl:aces/acl:ace/acl:actions: augment /acl:acls/acl:acl/acl:aces/acl:ace/acl:actions:
+--rw default-action? identityref +--rw default-action? identityref
A.2. Linux nftables A.2. 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
skipping to change at page 49, line 24 skipping to change at page 50, line 31
this draft and Linux nftables. this draft and Linux nftables.
A.3. Ethertypes A.3. Ethertypes
The ACL module is dependent on the definition of ethertypes. IEEE The ACL module is dependent on the definition of ethertypes. IEEE
owns the allocation of those ethertypes. This model is being owns the allocation of those ethertypes. This model is being
included here to enable definition of those types till such time that 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 IEEE takes up the task of publication of the model that defines those
ethertypes. At that time, this model can be deprecated. ethertypes. At that time, this model can be deprecated.
<CODE BEGINS> file "ietf-ethertypes@2018-03-03.yang" <CODE BEGINS> file "ietf-ethertypes@2018-03-15.yang"
module ietf-ethertypes { module ietf-ethertypes {
namespace "urn:ietf:params:xml:ns:yang:ietf-ethertypes"; namespace "urn:ietf:params:xml:ns:yang:ietf-ethertypes";
prefix ethertypes; prefix ethertypes;
organization organization
"IETF NETMOD (NETCONF Data Modeling Language)"; "IETF NETMOD (NETCONF Data Modeling Language)";
contact contact
"WG Web: <http://tools.ietf.org/wg/netmod/> "WG Web: <http://tools.ietf.org/wg/netmod/>
skipping to change at page 49, line 49 skipping to change at page 51, line 8
description description
"This module contains the common definitions for the "This module contains the common definitions for the
Ethertype used by different modules. It is a Ethertype used by different modules. It is a
placeholder module, till such time that IEEE placeholder module, till such time that IEEE
starts a project to define these Ethertypes starts a project to define these Ethertypes
and publishes a standard. and publishes a standard.
At that time this module can be deprecated."; At that time this module can be deprecated.";
revision 2018-03-03 { revision 2018-03-15 {
description description
"Initial revision."; "Initial revision.";
reference reference
"RFC XXXX: IETF Ethertype YANG Data Module."; "RFC XXXX: IETF Ethertype YANG Data Module.";
} }
typedef ethertype { typedef ethertype {
type union { type union {
type uint16; type uint16;
type enumeration { type enumeration {
enum ipv4 { enum ipv4 {
value 2048; value 2048;
skipping to change at page 50, line 19 skipping to change at page 51, line 25
typedef ethertype { typedef ethertype {
type union { type union {
type uint16; type uint16;
type enumeration { type enumeration {
enum ipv4 { enum ipv4 {
value 2048; value 2048;
description description
"Internet Protocol version 4 (IPv4) with a "Internet Protocol version 4 (IPv4) with a
hex value of 0x0800."; hex value of 0x0800.";
reference reference
"RFC 791, Internet Protocol."; "RFC 791: Internet Protocol.";
} }
enum arp { enum arp {
value 2054; value 2054;
description description
"Address Resolution Protocol (ARP) with a "Address Resolution Protocol (ARP) with a
hex value of 0x0806."; hex value of 0x0806.";
reference reference
"RFC 826 An Ethernet Address Resolution Protocol."; "RFC 826: An Ethernet Address Resolution Protocol.";
} }
enum wlan { enum wlan {
value 2114; value 2114;
description description
"Wake-on-LAN. Hex value of 0x0842."; "Wake-on-LAN. Hex value of 0x0842.";
} }
enum trill { enum trill {
value 8947; value 8947;
description description
"Transparent Interconnection of Lots of Links. "Transparent Interconnection of Lots of Links.
skipping to change at page 51, line 13 skipping to change at page 52, line 20
value 24579; value 24579;
description description
"DECnet Phase IV. Hex value of 0x6003."; "DECnet Phase IV. Hex value of 0x6003.";
} }
enum rarp { enum rarp {
value 32821; value 32821;
description description
"Reverse Address Resolution Protocol. "Reverse Address Resolution Protocol.
Hex value 0x8035."; Hex value 0x8035.";
reference reference
"RFC 903. A Reverse Address Resolution Protocol."; "RFC 903. A Reverse Address Resolution Protocol.";
} }
enum appletalk { enum appletalk {
value 32923; value 32923;
description description
"Appletalk (Ethertalk). Hex value 0x809B."; "Appletalk (Ethertalk). Hex value 0x809B.";
} }
enum aarp { enum aarp {
value 33011; value 33011;
description description
"Appletalk Address Resolution Protocol. Hex value "Appletalk Address Resolution Protocol. Hex value
of 0x80F3."; of 0x80F3.";
} }
enum vlan { enum vlan {
value 33024; value 33024;
description description
"VLAN-tagged frame (802.1Q) and Shortest Path "VLAN-tagged frame (802.1Q) and Shortest Path
Bridging IEEE 802.1aq with NNI compatibility. Bridging IEEE 802.1aq with NNI compatibility.
Hex value 0x8100."; Hex value 0x8100.";
reference reference
"802.1Q."; "802.1Q.";
} }
enum ipx { enum ipx {
value 33079; value 33079;
description description
"Internetwork Packet Exchange (IPX). Hex value "Internetwork Packet Exchange (IPX). Hex value
of 0x8137."; of 0x8137.";
} }
enum qnx { enum qnx {
value 33284; value 33284;
description description
skipping to change at page 51, line 46 skipping to change at page 53, line 4
enum ipx { enum ipx {
value 33079; value 33079;
description description
"Internetwork Packet Exchange (IPX). Hex value "Internetwork Packet Exchange (IPX). Hex value
of 0x8137."; of 0x8137.";
} }
enum qnx { enum qnx {
value 33284; value 33284;
description description
"QNX Qnet. Hex value of 0x8204."; "QNX Qnet. Hex value of 0x8204.";
} }
enum ipv6 { enum ipv6 {
value 34525; value 34525;
description description
"Internet Protocol Version 6 (IPv6). Hex value "Internet Protocol Version 6 (IPv6). Hex value
of 0x86DD."; of 0x86DD.";
reference reference
"RFC 8200, 8201."; "RFC 8200: IPv6
RFC 8201: Path MTU Discovery for IPv6.";
} }
enum efc { enum efc {
value 34824; value 34824;
description description
"Ethernet flow control using pause frames. "Ethernet flow control using pause frames.
Hex value of 0x8808"; Hex value of 0x8808";
reference reference
"IEEE Std. 802.1Qbb."; "IEEE Std. 802.1Qbb.";
} }
enum esp { enum esp {
skipping to change at page 52, line 34 skipping to change at page 53, line 41
value 34841; value 34841;
description description
"CobraNet. Hex value of 0x"; "CobraNet. Hex value of 0x";
} }
enum mpls-unicast { enum mpls-unicast {
value 34887; value 34887;
description description
"MultiProtocol Label Switch (MPLS) unicast traffic. "MultiProtocol Label Switch (MPLS) unicast traffic.
Hex value of 0x8847."; Hex value of 0x8847.";
reference reference
"RFC 3031."; "RFC 3031: MPLS Architecture.";
} }
enum mpls-multicast { enum mpls-multicast {
value 34888; value 34888;
description description
"MultiProtocol Label Switch (MPLS) multicast traffic. "MultiProtocol Label Switch (MPLS) multicast traffic.
Hex value of 0x8848."; Hex value of 0x8848.";
reference reference
"RFC 3031."; "RFC 3031: MPLS Architecture.";
} }
enum pppoe-discovery { enum pppoe-discovery {
value 34915; value 34915;
description description
"Point-to-Point Protocol over Ethernet. Used during "Point-to-Point Protocol over Ethernet. Used during
the discovery process. Hex value of 0x8863."; the discovery process. Hex value of 0x8863.";
reference reference
"RFC 2516."; "RFC 2516: A method for Transmitting PPPoE.";
} }
enum pppoe-session { enum pppoe-session {
value 34916; value 34916;
description description
"Point-to-Point Protocol over Ethernet. Used during "Point-to-Point Protocol over Ethernet. Used during
session stage. Hex value of 0x8864."; session stage. Hex value of 0x8864.";
reference reference
"RFC 2516."; "RFC 2516: A method for Transmitting PPPoE.";
} }
enum intel-ans { enum intel-ans {
value 34925; value 34925;
description description
"Intel Advanced Networking Services. Hex value of "Intel Advanced Networking Services. Hex value of
0x886D."; 0x886D.";
} }
enum jumbo-frames { enum jumbo-frames {
value 34928; value 34928;
description description
skipping to change at page 56, line 44 skipping to change at page 57, line 50
value 35119; value 35119;
description description
"High-availability Seamless Redundancy (HSR). Hex "High-availability Seamless Redundancy (HSR). Hex
value of 0x892F."; value of 0x892F.";
reference reference
"IEC 62439-3:2016."; "IEC 62439-3:2016.";
} }
} }
} }
description description
"The uint16 type placeholder type is defined to enable "The uint16 type placeholder is defined to enable
users to manage their own ethertypes not users to manage their own ethertypes not
covered by the module. Otherwise the module contains covered by the module. Otherwise the module contains
enum definitions for the more commonly used ethertypes."; enum definitions for the more commonly used ethertypes.";
} }
} }
<CODE ENDS> <CODE ENDS>
Authors' Addresses Authors' Addresses
 End of changes. 136 change blocks. 
317 lines changed or deleted 351 lines changed or added

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