draft-ietf-netmod-acl-model-19.txt   draft-ietf-netmod-acl-model-20.txt 
NETMOD WG M. Jethanandani NETMOD WG M. Jethanandani
Internet-Draft Internet-Draft VMware
Intended status: Standards Track L. Huang Intended status: Standards Track S. Agarwal
Expires: October 29, 2018 General Electric Expires: April 4, 2019 Cisco Systems, Inc.
S. Agarwal L. Huang
D. Blair D. Blair
Cisco Systems, Inc. October 1, 2018
April 27, 2018
Network Access Control List (ACL) YANG Data Model Network Access Control List (ACL) YANG Data Model
draft-ietf-netmod-acl-model-19 draft-ietf-netmod-acl-model-20
Abstract Abstract
This document defines a data model for Access Control List (ACL). An This document defines a data model for Access Control List (ACL). An
ACL is a user-ordered set of rules, used to configure the forwarding ACL is a user-ordered set of rules, used to configure the forwarding
behavior in device. Each rule is used to find a match on a packet, behavior in device. Each rule is used to find a match on 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
skipping to change at page 1, line 37 skipping to change at page 1, line 37
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 October 29, 2018. This Internet-Draft will expire on April 4, 2019.
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 20 skipping to change at page 2, line 20
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 1.3. Tree Diagram . . . . . . . . . . . . . . . . . . . . . . 4
2. Problem Statement . . . . . . . . . . . . . . . . . . . . . . 4 2. Problem Statement . . . . . . . . . . . . . . . . . . . . . . 4
3. Understanding ACL's Filters and Actions . . . . . . . . . . . 5 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. ACL Examples . . . . . . . . . . . . . . . . . . . . . . 37
4.4. Port Range Usage and Other Examples . . . . . . . . . . . 38 4.4. Port Range Usage and Other Examples . . . . . . . . . . . 39
5. Security Considerations . . . . . . . . . . . . . . . . . . . 42 5. Security Considerations . . . . . . . . . . . . . . . . . . . 43
6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 43 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 44
6.1. URI Registration . . . . . . . . . . . . . . . . . . . . 43 6.1. URI Registration . . . . . . . . . . . . . . . . . . . . 44
6.2. YANG Module Name Registration . . . . . . . . . . . . . . 43 6.2. YANG Module Name Registration . . . . . . . . . . . . . . 44
7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 44 7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 45
8. References . . . . . . . . . . . . . . . . . . . . . . . . . 44 8. References . . . . . . . . . . . . . . . . . . . . . . . . . 45
8.1. Normative References . . . . . . . . . . . . . . . . . . 44 8.1. Normative References . . . . . . . . . . . . . . . . . . 45
8.2. Informative References . . . . . . . . . . . . . . . . . 45 8.2. Informative References . . . . . . . . . . . . . . . . . 47
Appendix A. Extending ACL model examples . . . . . . . . . . . . 46 Appendix A. Extending ACL model examples . . . . . . . . . . . . 48
A.1. A company proprietary module example . . . . . . . . . . 46 A.1. A company proprietary module example . . . . . . . . . . 48
A.2. Linux nftables . . . . . . . . . . . . . . . . . . . . . 50 A.2. Linux nftables . . . . . . . . . . . . . . . . . . . . . 51
A.3. Ethertypes . . . . . . . . . . . . . . . . . . . . . . . 51 A.3. Ethertypes . . . . . . . . . . . . . . . . . . . . . . . 52
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 59 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 60
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 (PBR), firewalls etc.
An ACL is an user-ordered 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 actions.
criteria.
The match criteria allows for definition of packet headers and The match criteria allow for definition of packet headers and
metadata, all of which must be true for the match to occur. metadata, the contents of which must match the definitions.
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 (CoS) or port numbers. as address or Class of Service (CoS) or port numbers.
o In case a 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 length of the packet as received over the wire.
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 are 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 unbounded depending on the capabilities list of potential actions is unbounded depending on the capabilities
of the networking 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 the application/attachment of the ACL to an interface, VRF,
session, QoS policy, routing protocols amongst various other config vty/tty session, QoS policy, or routing protocols, amongst various
attachment points. Once attached, it is used for filtering traffic other configuration attachment points. Once attached, it is used for
using the match criteria in the ACE's and taking appropriate filtering traffic using the match criteria in the ACEs and taking
action(s) that have been configured against that ACE. In order to appropriate action(s) that have been configured against that ACE. In
apply an ACL to any attachment point other than an interface, vendors order to apply an ACL to any attachment point other than an
would have to augment the ACL YANG model. interface, vendors would have to augment the ACL YANG model.
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 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-04-27 needs to get o Revision date in model, in the format 2018-10-01 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
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 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
MAC: Media Access Control MAC: Media Access Control
PBR: Policy Based Routing
TCP: Transmission Control Protocol TCP: Transmission Control Protocol
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
skipping to change at page 4, line 46 skipping to change at page 4, line 48
1.3. Tree Diagram 1.3. Tree Diagram
For a reference to the annotations used in tree diagrams included in For a reference to the annotations used in tree diagrams included in
this draft, please see YANG Tree Diagrams [RFC8340]. this draft, please see YANG Tree Diagrams [RFC8340].
2. Problem Statement 2. Problem Statement
This document defines a YANG 1.1 [RFC7950] data model for the This document defines a YANG 1.1 [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 application/attachment models.
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 has 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 actions. The match
match criteria allows for definition of packet headers or metadata, criteria allow for definition of contents of the packet headers or
if supported by the vendor. Packet header matching applies to fields metadata, if supported by the vendor. Packet header matching applies
visible in the packet such as address or CoS or port numbers. to fields visible in the packet such as address or CoS or port
Metadata matching applies to fields associated with the packet, but numbers. Metadata matching applies to fields associated with the
not in the packet header such as input interface, packet length, or packet, but not in the packet header, such as input interface, packet
source or destination prefix length. The actions can be any sort of length, or source or destination prefix length. The actions can be
operation from logging to rate limiting or dropping to simply any sort of operation from logging to rate limiting or dropping to
forwarding. Actions on the first matching ACE are applied with no simply forwarding. Actions on the first matching ACE are applied
processing of subsequent ACEs. with no processing of 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 interface of a applied to multiple targets within the device, such as interface of a
networking 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, distinct ACLs etc. When applied to interfaces of a networked device, distinct ACLs
are defined for the ingress (input) or egress (output) interface. are defined for the ingress (input) or egress (output) interface.
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 in design, and we hope to achieve models. The base model is simple in design, and we hope to 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 matching on
or "Device can support of IPv4 headers". The second set of feature Ethernet headers" or "Device can support matching on IPv4 headers".
statements specify the combinations of headers the device is willing The second set of feature statements specify the combinations of
to support. These include features such as "Plain IPv6 ACL headers the device is willing to support. These include features
supported" or "Ethernet, IPv4 and IPv6 ACL combinations supported". such as "Plain IPv6 ACL 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 combination of 'if-feature' checks and 'must' statements allow for
the selection of relevant match fields that a user can define rules the selection of relevant match fields that a user can define rules
for. for.
If there is a need to define a 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.
module: ietf-access-control-list module: ietf-access-control-list
+--rw acls +--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)
skipping to change at page 6, line 36 skipping to change at page 6, line 40
| | | | yang:mac-address | | | | yang:mac-address
| | | +--rw source-mac-address? | | | +--rw source-mac-address?
| | | | yang:mac-address | | | | yang:mac-address
| | | +--rw source-mac-address-mask? | | | +--rw source-mac-address-mask?
| | | | yang:mac-address | | | | yang:mac-address
| | | +--rw ethertype? | | | +--rw ethertype?
| | | eth:ethertype | | | eth:ethertype
| | +--rw (l3)? | | +--rw (l3)?
| | | +--:(ipv4) | | | +--:(ipv4)
| | | | +--rw ipv4 {match-on-ipv4}? | | | | +--rw ipv4 {match-on-ipv4}?
| | | | +--rw dscp? inet:dscp | | | | +--rw dscp?
| | | | +--rw ecn? uint8 | | | | | inet:dscp
| | | | +--rw length? uint16 | | | | +--rw ecn?
| | | | +--rw ttl? uint8 | | | | | uint8
| | | | +--rw protocol? uint8 | | | | +--rw length?
| | | | +--rw ihl? uint8 | | | | | uint16
| | | | +--rw flags? bits | | | | +--rw ttl?
| | | | +--rw offset? uint16 | | | | | uint8
| | | | +--rw identification? uint16 | | | | +--rw protocol?
| | | | | uint8
| | | | +--rw ihl?
| | | | | uint8
| | | | +--rw flags?
| | | | | bits
| | | | +--rw offset?
| | | | | uint16
| | | | +--rw identification?
| | | | | uint16
| | | | +--rw (destination-network)? | | | | +--rw (destination-network)?
| | | | | +--:(destination-ipv4-network) | | | | | +--:(destination-ipv4-network)
| | | | | +--rw destination-ipv4-network? | | | | | +--rw destination-ipv4-network?
| | | | | inet:ipv4-prefix | | | | | inet:ipv4-prefix
| | | | +--rw (source-network)? | | | | +--rw (source-network)?
| | | | +--:(source-ipv4-network) | | | | +--:(source-ipv4-network)
| | | | +--rw source-ipv4-network? | | | | +--rw source-ipv4-network?
| | | | inet:ipv4-prefix | | | | inet:ipv4-prefix
| | | +--:(ipv6) | | | +--:(ipv6)
| | | +--rw ipv6 {match-on-ipv6}? | | | +--rw ipv6 {match-on-ipv6}?
| | | +--rw dscp? inet:dscp | | | +--rw dscp?
| | | +--rw ecn? uint8 | | | | inet:dscp
| | | +--rw length? uint16 | | | +--rw ecn?
| | | +--rw ttl? uint8 | | | | uint8
| | | +--rw protocol? uint8 | | | +--rw length?
| | | | uint16
| | | +--rw ttl?
| | | | uint8
| | | +--rw protocol?
| | | | uint8
| | | +--rw (destination-network)? | | | +--rw (destination-network)?
| | | | +--:(destination-ipv6-network) | | | | +--:(destination-ipv6-network)
| | | | +--rw destination-ipv6-network? | | | | +--rw destination-ipv6-network?
| | | | inet:ipv6-prefix | | | | inet:ipv6-prefix
| | | +--rw (source-network)? | | | +--rw (source-network)?
| | | | +--:(source-ipv6-network) | | | | +--:(source-ipv6-network)
| | | | +--rw source-ipv6-network? | | | | +--rw source-ipv6-network?
| | | | inet:ipv6-prefix | | | | inet:ipv6-prefix
| | | +--rw flow-label? | | | +--rw flow-label?
| | | inet:ipv6-flow-label | | | inet:ipv6-flow-label
| | +--rw (l4)? | | +--rw (l4)?
| | | +--:(tcp) | | | +--:(tcp)
| | | | +--rw tcp {match-on-tcp}? | | | | +--rw tcp {match-on-tcp}?
| | | | +--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? bits | | | | +--rw flags? bits
| | | | +--rw window-size? uint16 | | | | +--rw window-size? uint16
| | | | +--rw urgent-pointer? uint16 | | | | +--rw urgent-pointer? uint16
| | | | +--rw options? uint32 | | | | +--rw options? binary
| | | | +--rw source-port | | | | +--rw source-port
| | | | | +--rw (source-port)? | | | | | +--rw (source-port)?
| | | | | +--:(range-or-operator) | | | | | +--:(range-or-operator)
| | | | | +--rw (port-range-or-operator)? | | | | | +--rw (port-range-or-operator)?
| | | | | +--:(range) | | | | | +--:(range)
| | | | | | +--rw lower-port | | | | | | +--rw lower-port
| | | | | | | inet:port-number | | | | | | | inet:port-number
| | | | | | +--rw upper-port | | | | | | +--rw upper-port
| | | | | | inet:port-number | | | | | | inet:port-number
| | | | | +--:(operator) | | | | | +--:(operator)
skipping to change at page 8, line 44 skipping to change at page 9, line 14
| | | | | +--rw upper-port | | | | | +--rw upper-port
| | | | | inet:port-number | | | | | inet:port-number
| | | | +--:(operator) | | | | +--:(operator)
| | | | +--rw operator? operator | | | | +--rw operator? operator
| | | | +--rw port | | | | +--rw port
| | | | inet:port-number | | | | inet:port-number
| | | +--:(icmp) | | | +--:(icmp)
| | | +--rw icmp {match-on-icmp}? | | | +--rw icmp {match-on-icmp}?
| | | +--rw type? uint8 | | | +--rw type? uint8
| | | +--rw code? uint8 | | | +--rw code? uint8
| | | +--rw rest-of-header? uint32 | | | +--rw rest-of-header? binary
| | +--rw egress-interface? if:interface-ref | | +--rw egress-interface? if:interface-ref
| | +--rw ingress-interface? if:interface-ref | | +--rw ingress-interface? if:interface-ref
| +--rw actions | +--rw actions
| | +--rw forwarding identityref | | +--rw forwarding identityref
| | +--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}?
skipping to change at page 10, line 15 skipping to change at page 10, line 32
ability for ACLs 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 [RFC8343]. [RFC6991], and A YANG Data Model for Interface Management [RFC8343].
<CODE BEGINS> file "ietf-access-control-list@2018-04-27.yang" <CODE BEGINS> file "ietf-access-control-list@2018-10-01.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 11, line 26 skipping to change at page 11, line 42
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-04-27 { revision 2018-10-01 {
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 14, line 36 skipping to change at page 15, line 4
"The 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
"The 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
"The device can support TCP headers."; "The device can support matching on TCP headers.";
} }
feature match-on-udp { feature match-on-udp {
description description
"The device can support UDP header."; "The device can support matching on UDP headers.";
} }
feature match-on-icmp { feature match-on-icmp {
description description
"The device can support ICMP header."; "The device can support matching on ICMP (v4 and v6) headers.";
} }
/* /*
* 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 16, line 43 skipping to change at page 17, line 11
"Common grouping for ACL counters"; "Common grouping for ACL counters";
leaf matched-packets { leaf matched-packets {
type yang:counter64; type yang:counter64;
config false; config false;
description description
"Count of the number of packets matching the current ACL "Count of the number of packets matching the current ACL
entry. entry.
An implementation should provide this counter on a An implementation should provide this counter on a
per-interface per-ACL-entry if possible. per-interface per-ACL-entry basis if possible.
If an implementation only supports ACL counters per entry If an implementation only supports ACL counters on a per
(i.e., not broken out per interface), then the value entry basis (i.e., not broken out per interface), then the
should be equal to the aggregate count across all interfaces. value should be equal to the aggregate count across all
interfaces.
An implementation that provides counters per entry per An implementation that provides counters on a per entry per
interface is not required to also provide an aggregate count, interface basis is not required to also provide an aggregate
e.g., per entry -- the user is expected to be able implement count, e.g., per entry -- the user is expected to be able
the required aggregation if such a count is needed."; implement the required aggregation if such a count is
needed.";
} }
leaf matched-octets { leaf matched-octets {
type yang:counter64; type yang:counter64;
config false; config false;
description description
"Count of the number of octets (bytes) matching the current "Count of the number of octets (bytes) matching the current
ACL entry. ACL entry.
An implementation should provide this counter on a An implementation should provide this counter on a
skipping to change at page 24, line 23 skipping to change at page 24, line 41
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 are very large, the base draft
not include these directly but references them by 'uses' statement to does not include these directly but references them by 'uses'
keep the base module simple. In case more match conditions are statement to keep the base module simple. In case more match
needed, those can be added by augmenting choices within container conditions are needed, those can be added by augmenting choices
"matches" in ietf-access-control-list.yang model. within container "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], TCP [RFC0793],
Differentiated Services Field in the IPv4 and IPv6 Headers [RFC2474], Definition of the Differentiated Services Field in the IPv4 and IPv6
The Addition of Explicit Congestion Notification (ECN) to IP Headers [RFC2474], The Addition of Explicit Congestion Notification
[RFC3168], , IPv6 Scoped Address Architecture [RFC4007], IPv6 (ECN) to IP [RFC3168], , IPv6 Scoped Address Architecture [RFC4007],
Addressing Architecture [RFC4291], A Recommendation for IPv6 Address IPv6 Addressing Architecture [RFC4291], A Recommendation for IPv6
Text Representation [RFC5952], IPv6 [RFC8200]. Address Text Representation [RFC5952], IPv6 [RFC8200].
<CODE BEGINS> file "ietf-packet-fields@2018-04-27.yang" <CODE BEGINS> file "ietf-packet-fields@2018-10-01.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 25, line 49 skipping to change at page 26, line 19
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-04-27 { revision 2018-10-01 {
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 {
skipping to change at page 35, line 4 skipping to change at page 35, line 23
leaf window-size { leaf window-size {
type uint16; type uint16;
units "bytes"; 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 beyond the segment the number of window size units beyond the segment
identified by the sequence number in the acknowledgment identified by the sequence number in the acknowledgment
field that the sender of this segment is currently field 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.";
} }
leaf options { leaf options {
type uint32; type binary {
length "1..40";
}
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
field indicates the type of option, and is the field indicates the type of option, and is the
only field that is not optional. Depending on only field that is not optional. Depending on
what kind of option we are dealing with, what kind of option we are dealing with,
the next two fields may be set: the Option-Length the next two fields may be set: the Option-Length
field indicates the total length of the option, field indicates the total length of the option,
skipping to change at page 36, line 18 skipping to change at page 36, line 38
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 reference
"RFC 792: Internet Control Message Protocol (ICMP)."; "RFC 792: Internet Control Message Protocol (ICMP),
RFC 4443: Internet Control Message Protocol (ICMPv6)
for Internet Protocol Version 6 (IPv6)
Specifciation.";
} }
leaf code { leaf code {
type uint8; type uint8;
description description
"ICMP subtype. Also known as Control messages."; "ICMP subtype. Also known as Control messages.";
reference
"RFC 792: Internet Control Message Protocol (ICMP),
RFC 4443: Internet Control Message Protocol (ICMPv6)
for Internet Protocol Version 6 (IPv6)
Specifciation.";
} }
leaf rest-of-header { leaf rest-of-header {
type uint32; type binary;
description description
"Four-bytes field, contents vary based on the "Unbounded in length, the contents vary based on the
ICMP type and code."; ICMP type and code. Also referred to as 'Message Body'
in ICMPv6.";
reference
"RFC 792: Internet Control Message Protocol (ICMP),
RFC 4443: Internet Control Message Protocol (ICMPv6)
for Internet Protocol Version 6 (IPv6)
Specifciation.";
} }
} }
} }
<CODE ENDS> <CODE ENDS>
4.3. An ACL Example 4.3. ACL Examples
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:
[note: '\' line wrapping for formatting only] [note: '\' line wrapping for formatting only]
<?xml version="1.0" encoding="UTF-8"?> <?xml version="1.0" encoding="UTF-8"?>
<config xmlns="urn:ietf:params:xml:ns:netconf:base:1.0"> <config xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
skipping to change at page 42, line 39 skipping to change at page 43, line 39
</acls> </acls>
</config> </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 [RFC8446].
The NETCONF Access Control Model (NACM [RFC8341]) provides the means The NETCONF Access Control Model (NACM [RFC8341]) provides the means
to restrict access for particular NETCONF users to a pre-configured to restrict access for particular NETCONF users to a pre-configured
subset of all available NETCONF protocol operations and content. subset of all available NETCONF protocol operations and content.
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:
/acls/acl/aces: This list specifies all the configured access /acls/acl/aces: This list specifies all the configured access
control entries on the device. Unauthorized write access to this control entries on the device. Unauthorized write access to this
list can allow intruders to access and control the system. list can allow intruders to modify the entries so as to permit
Unauthorized read access to this list can allow intruders to spoof traffic that should not be permitted, or deny traffic that should
packets with authorized addresses thereby compromising the system. be permitted. The former may result in a DoS attack, or
compromise the device. The latter may result in a DoS attack.
The impact of an unauthorized read access of the list will allow
the attacker to determine which rules are in effect, to better
craft an attack.
/acls/acl/aces/ace/actions/logging: This node specifies ability to
log packets that match this ace entry. Unauthorized write access
to this node can allow intruders to enable logging on one or many
ace entries, overwhelming the server in the process. Unauthorized
read access of this node can allow intruders to access logging
information, which could be used to craft an attack the server.
6. IANA Considerations 6. IANA Considerations
This document registers three URIs and three YANG modules. This document registers three URIs and three YANG modules.
6.1. URI Registration 6.1. URI Registration
This document registers three URIs in the IETF XML registry This document registers three URIs in the IETF XML registry
[RFC3688]. Following the format in RFC 3688, the following [RFC3688]. Following the format in RFC 3688, the following
registration is requested to be made: registration is requested to be made:
skipping to change at page 44, line 39 skipping to change at page 46, line 5
8.1. Normative References 8.1. Normative References
[RFC0791] Postel, J., "Internet Protocol", STD 5, RFC 791, [RFC0791] Postel, J., "Internet Protocol", STD 5, RFC 791,
DOI 10.17487/RFC0791, September 1981, DOI 10.17487/RFC0791, September 1981,
<https://www.rfc-editor.org/info/rfc791>. <https://www.rfc-editor.org/info/rfc791>.
[RFC0792] Postel, J., "Internet Control Message Protocol", STD 5, [RFC0792] Postel, J., "Internet Control Message Protocol", STD 5,
RFC 792, DOI 10.17487/RFC0792, September 1981, RFC 792, DOI 10.17487/RFC0792, September 1981,
<https://www.rfc-editor.org/info/rfc792>. <https://www.rfc-editor.org/info/rfc792>.
[RFC0793] Postel, J., "Transmission Control Protocol", STD 7,
RFC 793, DOI 10.17487/RFC0793, September 1981,
<https://www.rfc-editor.org/info/rfc793>.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, Requirement Levels", BCP 14, RFC 2119,
DOI 10.17487/RFC2119, March 1997, DOI 10.17487/RFC2119, March 1997,
<https://www.rfc-editor.org/info/rfc2119>. <https://www.rfc-editor.org/info/rfc2119>.
[RFC2474] Nichols, K., Blake, S., Baker, F., and D. Black, [RFC2474] Nichols, K., Blake, S., Baker, F., and D. Black,
"Definition of the Differentiated Services Field (DS "Definition of the Differentiated Services Field (DS
Field) in the IPv4 and IPv6 Headers", RFC 2474, Field) in the IPv4 and IPv6 Headers", RFC 2474,
DOI 10.17487/RFC2474, December 1998, DOI 10.17487/RFC2474, December 1998,
<https://www.rfc-editor.org/info/rfc2474>. <https://www.rfc-editor.org/info/rfc2474>.
skipping to change at page 46, line 5 skipping to change at page 47, line 20
[RFC8343] Bjorklund, M., "A YANG Data Model for Interface [RFC8343] Bjorklund, M., "A YANG Data Model for Interface
Management", RFC 8343, DOI 10.17487/RFC8343, March 2018, Management", RFC 8343, DOI 10.17487/RFC8343, March 2018,
<https://www.rfc-editor.org/info/rfc8343>. <https://www.rfc-editor.org/info/rfc8343>.
8.2. Informative References 8.2. Informative 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-editor.org/info/rfc3688>. <https://www.rfc-editor.org/info/rfc3688>.
[RFC5246] Dierks, T. and E. Rescorla, "The Transport Layer Security
(TLS) Protocol Version 1.2", RFC 5246,
DOI 10.17487/RFC5246, August 2008,
<https://www.rfc-editor.org/info/rfc5246>.
[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-editor.org/info/rfc6020>. <https://www.rfc-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,
<https://www.rfc-editor.org/info/rfc6241>. <https://www.rfc-editor.org/info/rfc6241>.
skipping to change at page 46, line 43 skipping to change at page 48, line 5
[RFC8340] Bjorklund, M. and L. Berger, Ed., "YANG Tree Diagrams", [RFC8340] Bjorklund, M. and L. Berger, Ed., "YANG Tree Diagrams",
BCP 215, RFC 8340, DOI 10.17487/RFC8340, March 2018, BCP 215, RFC 8340, DOI 10.17487/RFC8340, March 2018,
<https://www.rfc-editor.org/info/rfc8340>. <https://www.rfc-editor.org/info/rfc8340>.
[RFC8341] Bierman, A. and M. Bjorklund, "Network Configuration [RFC8341] Bierman, A. and M. Bjorklund, "Network Configuration
Access Control Model", STD 91, RFC 8341, Access Control Model", STD 91, RFC 8341,
DOI 10.17487/RFC8341, March 2018, DOI 10.17487/RFC8341, March 2018,
<https://www.rfc-editor.org/info/rfc8341>. <https://www.rfc-editor.org/info/rfc8341>.
[RFC8446] Rescorla, E., "The Transport Layer Security (TLS) Protocol
Version 1.3", RFC 8446, DOI 10.17487/RFC8446, August 2018,
<https://www.rfc-editor.org/info/rfc8446>.
Appendix A. Extending ACL model examples Appendix A. Extending ACL model examples
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, actions, and
criteria, and default actions when no ACE matches are found. All default actions for when no ACE matches are found. All these are
these are company proprietary extensions or system feature company proprietary extensions or system feature extensions.
extensions. "example-newco-acl" is just an example and it is "example-newco-acl" is just an example and it is expected that
expected that vendors will create their own proprietary models. vendors will create their own proprietary models.
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 {
skipping to change at page 47, line 27 skipping to change at page 48, line 41
} }
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-04-27 { revision 2018-10-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";
} }
augment "/acl:acls/acl:acl/" + augment "/acl:acls/acl:acl/" +
"acl:aces/acl:ace/" + "acl:aces/acl:ace/" +
skipping to change at page 51, line 24 skipping to change at page 52, line 24
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-04-27.yang" <CODE BEGINS> file "ietf-ethertypes@2018-10-01.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 51, line 49 skipping to change at page 52, line 49
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-04-27 { revision 2018-10-01 {
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;
skipping to change at page 59, line 9 skipping to change at page 60, line 9
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
Mahesh Jethanandani Mahesh Jethanandani
VMware
Email: mjethanandani@gmail.com Email: mjethanandani@gmail.com
Lisa Huang
General Electric
Email: lyihuang16@gmail.com
Sonal Agarwal Sonal Agarwal
Cisco Systems, Inc. Cisco Systems, Inc.
Email: sagarwal12@gmail.com Email: sagarwal12@gmail.com
Lisa Huang
Email: huangyi_99@yahoo.com
Dana Blair Dana Blair
Cisco Systems, Inc.
Email: dblair@cisco.com Email: dana@blairhome.com
 End of changes. 56 change blocks. 
130 lines changed or deleted 174 lines changed or added

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