draft-ietf-netmod-acl-model-18.txt   draft-ietf-netmod-acl-model-19.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 16, 2018 General Electric Expires: October 29, 2018 General Electric
S. Agarwal S. Agarwal
D. Blair D. Blair
Cisco Systems, Inc. Cisco Systems, Inc.
March 15, 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-18 draft-ietf-netmod-acl-model-19
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 September 16, 2018. This Internet-Draft will expire on October 29, 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 21 skipping to change at page 2, line 21
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. An ACL Example . . . . . . . . . . . . . . . . . . . . . 36
4.4. Port Range Usage and Other Examples . . . . . . . . . . . 37 4.4. Port Range Usage and Other Examples . . . . . . . . . . . 38
5. Security Considerations . . . . . . . . . . . . . . . . . . . 41 5. Security Considerations . . . . . . . . . . . . . . . . . . . 42
6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 42 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 43
6.1. URI Registration . . . . . . . . . . . . . . . . . . . . 42 6.1. URI Registration . . . . . . . . . . . . . . . . . . . . 43
6.2. YANG Module Name Registration . . . . . . . . . . . . . . 42 6.2. YANG Module Name Registration . . . . . . . . . . . . . . 43
7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 43 7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 44
8. References . . . . . . . . . . . . . . . . . . . . . . . . . 43 8. References . . . . . . . . . . . . . . . . . . . . . . . . . 44
8.1. Normative References . . . . . . . . . . . . . . . . . . 43 8.1. Normative References . . . . . . . . . . . . . . . . . . 44
8.2. Informative References . . . . . . . . . . . . . . . . . 45 8.2. Informative References . . . . . . . . . . . . . . . . . 45
Appendix A. Extending ACL model examples . . . . . . . . . . . . 46 Appendix A. Extending ACL model examples . . . . . . . . . . . . 46
A.1. A company proprietary module example . . . . . . . . . . 46 A.1. A company proprietary module example . . . . . . . . . . 46
A.2. Linux nftables . . . . . . . . . . . . . . . . . . . . . 49 A.2. Linux nftables . . . . . . . . . . . . . . . . . . . . . 50
A.3. Ethertypes . . . . . . . . . . . . . . . . . . . . . . . 50 A.3. Ethertypes . . . . . . . . . . . . . . . . . . . . . . . 51
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 58 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 59
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 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).
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-15 needs to get o Revision date in model, in the format 2018-04-27 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
skipping to change at page 4, line 40 skipping to change at page 4, line 40
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 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 this draft, please see YANG Tree Diagrams [RFC8340].
[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 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 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
skipping to change at page 10, line 13 skipping to change at page 10, line 13
logging option allows for a match to be logged that can later be used logging option allows for a match to be logged that can later be used
to determine which rule was matched upon. The model also defines the to determine which rule was matched upon. The model also defines the
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 [RFC6991], and A YANG Data Model for Interface Management [RFC8343].
[I-D.ietf-netmod-rfc7223bis].
<CODE BEGINS> file "ietf-access-control-list@2018-03-15.yang" <CODE BEGINS> file "ietf-access-control-list@2018-04-27.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 38 skipping to change at page 10, line 37
import ietf-packet-fields { import ietf-packet-fields {
prefix pf; prefix pf;
reference reference
"RFC XXXX - Network ACL YANG Model."; "RFC XXXX - Network ACL YANG Model.";
} }
import ietf-interfaces { import ietf-interfaces {
prefix if; prefix if;
reference reference
"I-D.draft-ietf-netmod-rfc7223bis - A YANG Data Model for "RFC 8343 - A YANG Data Model for Interface Management.";
Interface Management.";
} }
organization organization
"IETF NETMOD (Network 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
skipping to change at page 11, line 28 skipping to change at page 11, line 26
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-15 { revision 2018-04-27 {
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 24, line 39 skipping to change at page 24, line 37
"matches" in 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-15.yang" <CODE BEGINS> file "ietf-packet-fields@2018-04-27.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 51 skipping to change at page 25, line 49
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-15 { revision 2018-04-27 {
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 28, line 29 skipping to change at page 28, line 26
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: Internet Protocol, "RFC 791: Internet Protocol,
RFC 8200: IPv6."; RFC 8200: Internet Protocol, Version 6 (IPv6) Specification.";
} }
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 dropped. 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 reference
"RFC 791: Internet Protocol, "RFC 791: Internet Protocol,
RFC 8200: IPv6."; RFC 8200: Internet Protocol, Version 6 (IPv6) Specification.";
} }
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,
and if extension headers are present, the protocol is
present in the 'upper-layer' header.";
reference reference
"RFC 791: Internet Protocol, "RFC 791: Internet Protocol,
RFC 8200: IPv6."; RFC 8200: Internet Protocol, Version 6 (IPv6) Specification.";
} }
} }
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 27 skipping to change at page 33, line 26
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 reference
"RFC 3168: Explicit Congestion Notification."; "RFC 3168: The Addition of Explicit Congestion
Notification (ECN) to IP.";
} }
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 reference
"RFC 3168: Explicit Congestion Notification."; "RFC 3168: The Addition of Explicit Congestion
Notification (ECN) to IP.";
} }
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 37 skipping to change at page 34, line 38
} }
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 reference
"RFC 793: TCP."; "RFC 793: Transmission Control Protocol (TCP).";
} }
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
skipping to change at page 35, line 51 skipping to change at page 36, line 4
actual limit for the data length, which is actual limit for the data length, which is
imposed by the underlying IPv4 protocol, is imposed by the underlying IPv4 protocol, is
65,507 bytes (65,535 minus 8 byte UDP header 65,507 bytes (65,535 minus 8 byte UDP header
minus 20 byte IP header). minus 20 byte IP header).
In IPv6 jumbograms it is possible to have In IPv6 jumbograms it is possible to have
UDP packets of size greater than 65,535 bytes. UDP packets of size greater than 65,535 bytes.
RFC 2675 specifies that the length field is set RFC 2675 specifies that the length field is set
to zero if the length of the UDP header plus to zero if the length of the UDP header plus
UDP data is greater than 65,535."; UDP data is greater than 65,535.";
}
}
} }
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: ICMP."; "RFC 792: Internet Control Message Protocol (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;
skipping to change at page 37, line 40 skipping to change at page 37, line 40
</aces> </aces>
</acl> </acl>
</acls> </acls>
</config> </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:
acl 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
Requirement: Accept all DNS traffic destined for 2001:db8::/32 on
port 53.
[note: '\' line wrapping for formatting only]
<?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>allow-dns-packets</name>
<type>ipv6-acl-type</type>
<aces>
<ace>
<name>rule1</name>
<matches>
<ipv6>
<destination-ipv6-network>2001:db8::/32</destination-i\
pv6-network>
</ipv6>
<udp>
<destination-port>
<operator>eq</operator>
<port>53</port>
</destination-port>
</udp>
</matches>
<actions>
<forwarding>accept</forwarding>
</actions>
</ace>
</aces>
</acl>
</acls>
</config>
4.4. Port Range Usage and Other Examples 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 included. When only a port is present, it represents a upper-port included. When only a port is present, it represents a
port, with the operator specifying the range. port, with the operator specifying the range.
The following XML example represents a configuration where traffic to The following XML example represents a configuration where TCP
source ports 16384, 16385, 16386, and 16387 is dropped. traffic from source ports 16384, 16385, 16386, and 16387 is dropped.
[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">
<acls <acls
xmlns="urn:ietf:params:xml:ns:yang:ietf-access-control-list"> xmlns="urn:ietf:params:xml:ns:yang:ietf-access-control-list">
<acl> <acl>
<name>sample-port-acl</name> <name>sample-port-acl</name>
<type>ipv4-acl-type</type> <type>ipv4-acl-type</type>
<aces> <aces>
<ace> <ace>
skipping to change at page 38, line 34 skipping to change at page 39, line 32
</matches> </matches>
<actions> <actions>
<forwarding>drop</forwarding> <forwarding>drop</forwarding>
</actions> </actions>
</ace> </ace>
</aces> </aces>
</acl> </acl>
</acls> </acls>
</config> </config>
The following XML example represents a configuration where all ping The following XML example represents a configuration where all IPv4
echo requests are dropped. ICMP echo requests are dropped.
[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">
<acls <acls
xmlns="urn:ietf:params:xml:ns:yang:ietf-access-control-list"> xmlns="urn:ietf:params:xml:ns:yang:ietf-access-control-list">
<acl> <acl>
<name>sample-icmp-acl</name> <name>sample-icmp-acl</name>
<aces> <aces>
<ace> <ace>
<name>rule1</name> <name>rule1</name>
<matches> <matches>
<ipv4>
<protocol>1</protocol>
</ipv4>
<icmp> <icmp>
<type>8</type> <type>8</type>
<code>0</code> <code>0</code>
</icmp> </icmp>
</matches> </matches>
<actions> <actions>
<forwarding>drop</forwarding> <forwarding>drop</forwarding>
</actions> </actions>
</ace> </ace>
</aces> </aces>
</acl> </acl>
</acls> </acls>
</config> </config>
The following XML example represents a configuration of a single The following XML example represents a configuration of a single
port, port 21 that accepts traffic. port, port 21 that accepts TCP traffic.
[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">
<acls <acls
xmlns="urn:ietf:params:xml:ns:yang:ietf-access-control-list"> xmlns="urn:ietf:params:xml:ns:yang:ietf-access-control-list">
<acl> <acl>
<name>sample-ipv4-acl</name> <name>sample-ipv4-acl</name>
<type>ipv4-acl-type</type> <type>ipv4-acl-type</type>
<aces> <aces>
<ace> <ace>
<name>rule1</name> <name>rule1</name>
<matches> <matches>
<tcp> <tcp>
<source-port> <destination-port>
<operator>eq</operator> <operator>eq</operator>
<port>21</port> <port>21</port>
</source-port> </destination-port>
</tcp> </tcp>
</matches> </matches>
<actions> <actions>
<forwarding>accept</forwarding> <forwarding>accept</forwarding>
</actions> </actions>
</ace> </ace>
</aces> </aces>
</acl> </acl>
</acls> </acls>
</config> </config>
The following XML example represents a configuration specifying all The following XML example represents a configuration specifying all
ports that are not equal to 21, that will drop packets destined for ports that are not equal to 21, that will drop TCP packets destined
those ports. for those ports.
[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">
<acls <acls
xmlns="urn:ietf:params:xml:ns:yang:ietf-access-control-list"> xmlns="urn:ietf:params:xml:ns:yang:ietf-access-control-list">
<acl> <acl>
<name>sample-ipv4-acl</name> <name>sample-ipv4-acl</name>
<type>ipv4-acl-type</type> <type>ipv4-acl-type</type>
<aces> <aces>
<ace> <ace>
<name>rule1</name> <name>rule1</name>
<matches> <matches>
<tcp> <tcp>
<source-port> <destination-port>
<operator>neq</operator> <operator>neq</operator>
<port>21</port> <port>21</port>
</source-port> </destination-port>
</tcp> </tcp>
</matches> </matches>
<actions> <actions>
<forwarding>drop</forwarding> <forwarding>drop</forwarding>
</actions> </actions>
</ace> </ace>
</aces> </aces>
</acl> </acl>
</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 [RFC5246].
The NETCONF Access Control Model (NACM [RFC6536]) 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.
skipping to change at page 43, line 46 skipping to change at page 44, line 31
received more participation from many vendors. received more participation from many vendors.
Authors would like to thank Jason Sterne, Lada Lhotka, Juergen Authors would like to thank Jason Sterne, Lada Lhotka, Juergen
Schoenwalder, David Bannister, Jeff Haas, Kristian Larsson and Einar Schoenwalder, David Bannister, Jeff Haas, Kristian Larsson and Einar
Nilsen-Nygaard for their review of and suggestions to the draft. Nilsen-Nygaard for their review of and suggestions to the draft.
8. References 8. References
8.1. Normative References 8.1. Normative References
[I-D.ietf-netmod-rfc7223bis]
Bjorklund, M., "A YANG Data Model for Interface
Management", draft-ietf-netmod-rfc7223bis-03 (work in
progress), January 2018.
[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>.
[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,
skipping to change at page 44, line 29 skipping to change at page 45, line 10
"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>.
[RFC3168] Ramakrishnan, K., Floyd, S., and D. Black, "The Addition [RFC3168] Ramakrishnan, K., Floyd, S., and D. Black, "The Addition
of Explicit Congestion Notification (ECN) to IP", of Explicit Congestion Notification (ECN) to IP",
RFC 3168, DOI 10.17487/RFC3168, September 2001, RFC 3168, DOI 10.17487/RFC3168, September 2001,
<https://www.rfc-editor.org/info/rfc3168>. <https://www.rfc-editor.org/info/rfc3168>.
[RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688,
DOI 10.17487/RFC3688, January 2004,
<https://www.rfc-editor.org/info/rfc3688>.
[RFC4007] Deering, S., Haberman, B., Jinmei, T., Nordmark, E., and [RFC4007] Deering, S., Haberman, B., Jinmei, T., Nordmark, E., and
B. Zill, "IPv6 Scoped Address Architecture", RFC 4007, B. Zill, "IPv6 Scoped Address Architecture", RFC 4007,
DOI 10.17487/RFC4007, March 2005, DOI 10.17487/RFC4007, March 2005,
<https://www.rfc-editor.org/info/rfc4007>. <https://www.rfc-editor.org/info/rfc4007>.
[RFC4291] Hinden, R. and S. Deering, "IP Version 6 Addressing [RFC4291] Hinden, R. and S. Deering, "IP Version 6 Addressing
Architecture", RFC 4291, DOI 10.17487/RFC4291, February Architecture", RFC 4291, DOI 10.17487/RFC4291, February
2006, <https://www.rfc-editor.org/info/rfc4291>. 2006, <https://www.rfc-editor.org/info/rfc4291>.
[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>.
[RFC5952] Kawamura, S. and M. Kawashima, "A Recommendation for IPv6 [RFC5952] Kawamura, S. and M. Kawashima, "A Recommendation for IPv6
Address Text Representation", RFC 5952, Address Text Representation", RFC 5952,
DOI 10.17487/RFC5952, August 2010, DOI 10.17487/RFC5952, August 2010,
<https://www.rfc-editor.org/info/rfc5952>. <https://www.rfc-editor.org/info/rfc5952>.
[RFC6020] Bjorklund, M., Ed., "YANG - A Data Modeling Language for
the Network Configuration Protocol (NETCONF)", RFC 6020,
DOI 10.17487/RFC6020, October 2010,
<https://www.rfc-editor.org/info/rfc6020>.
[RFC6241] Enns, R., Ed., Bjorklund, M., Ed., Schoenwaelder, J., Ed.,
and A. Bierman, Ed., "Network Configuration Protocol
(NETCONF)", RFC 6241, DOI 10.17487/RFC6241, June 2011,
<https://www.rfc-editor.org/info/rfc6241>.
[RFC6242] Wasserman, M., "Using the NETCONF Protocol over Secure
Shell (SSH)", RFC 6242, DOI 10.17487/RFC6242, June 2011,
<https://www.rfc-editor.org/info/rfc6242>.
[RFC6536] Bierman, A. and M. Bjorklund, "Network Configuration
Protocol (NETCONF) Access Control Model", RFC 6536,
DOI 10.17487/RFC6536, March 2012,
<https://www.rfc-editor.org/info/rfc6536>.
[RFC6991] Schoenwaelder, J., Ed., "Common YANG Data Types", [RFC6991] Schoenwaelder, J., Ed., "Common YANG Data Types",
RFC 6991, DOI 10.17487/RFC6991, July 2013, RFC 6991, DOI 10.17487/RFC6991, July 2013,
<https://www.rfc-editor.org/info/rfc6991>. <https://www.rfc-editor.org/info/rfc6991>.
[RFC7950] Bjorklund, M., Ed., "The YANG 1.1 Data Modeling Language", [RFC7950] Bjorklund, M., Ed., "The YANG 1.1 Data Modeling Language",
RFC 7950, DOI 10.17487/RFC7950, August 2016, RFC 7950, DOI 10.17487/RFC7950, August 2016,
<https://www.rfc-editor.org/info/rfc7950>. <https://www.rfc-editor.org/info/rfc7950>.
[RFC8040] Bierman, A., Bjorklund, M., and K. Watsen, "RESTCONF
Protocol", RFC 8040, DOI 10.17487/RFC8040, January 2017,
<https://www.rfc-editor.org/info/rfc8040>.
[RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC [RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC
2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174,
May 2017, <https://www.rfc-editor.org/info/rfc8174>. May 2017, <https://www.rfc-editor.org/info/rfc8174>.
[RFC8200] Deering, S. and R. Hinden, "Internet Protocol, Version 6 [RFC8200] Deering, S. and R. Hinden, "Internet Protocol, Version 6
(IPv6) Specification", STD 86, RFC 8200, (IPv6) Specification", STD 86, RFC 8200,
DOI 10.17487/RFC8200, July 2017, DOI 10.17487/RFC8200, July 2017,
<https://www.rfc-editor.org/info/rfc8200>. <https://www.rfc-editor.org/info/rfc8200>.
[RFC8343] Bjorklund, M., "A YANG Data Model for Interface
Management", RFC 8343, DOI 10.17487/RFC8343, March 2018,
<https://www.rfc-editor.org/info/rfc8343>.
8.2. Informative References 8.2. Informative References
[I-D.ietf-netmod-yang-tree-diagrams] [RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688,
Bjorklund, M. and L. Berger, "YANG Tree Diagrams", draft- DOI 10.17487/RFC3688, January 2004,
ietf-netmod-yang-tree-diagrams-06 (work in progress), <https://www.rfc-editor.org/info/rfc3688>.
February 2018.
[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
the Network Configuration Protocol (NETCONF)", RFC 6020,
DOI 10.17487/RFC6020, October 2010,
<https://www.rfc-editor.org/info/rfc6020>.
[RFC6241] Enns, R., Ed., Bjorklund, M., Ed., Schoenwaelder, J., Ed.,
and A. Bierman, Ed., "Network Configuration Protocol
(NETCONF)", RFC 6241, DOI 10.17487/RFC6241, June 2011,
<https://www.rfc-editor.org/info/rfc6241>.
[RFC6242] Wasserman, M., "Using the NETCONF Protocol over Secure
Shell (SSH)", RFC 6242, DOI 10.17487/RFC6242, June 2011,
<https://www.rfc-editor.org/info/rfc6242>.
[RFC7011] Claise, B., Ed., Trammell, B., Ed., and P. Aitken, [RFC7011] Claise, B., Ed., Trammell, B., Ed., and P. Aitken,
"Specification of the IP Flow Information Export (IPFIX) "Specification of the IP Flow Information Export (IPFIX)
Protocol for the Exchange of Flow Information", STD 77, Protocol for the Exchange of Flow Information", STD 77,
RFC 7011, DOI 10.17487/RFC7011, September 2013, RFC 7011, DOI 10.17487/RFC7011, September 2013,
<https://www.rfc-editor.org/info/rfc7011>. <https://www.rfc-editor.org/info/rfc7011>.
[RFC8040] Bierman, A., Bjorklund, M., and K. Watsen, "RESTCONF
Protocol", RFC 8040, DOI 10.17487/RFC8040, January 2017,
<https://www.rfc-editor.org/info/rfc8040>.
[RFC8340] Bjorklund, M. and L. Berger, Ed., "YANG Tree Diagrams",
BCP 215, RFC 8340, DOI 10.17487/RFC8340, March 2018,
<https://www.rfc-editor.org/info/rfc8340>.
[RFC8341] Bierman, A. and M. Bjorklund, "Network Configuration
Access Control Model", STD 91, RFC 8341,
DOI 10.17487/RFC8341, March 2018,
<https://www.rfc-editor.org/info/rfc8341>.
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, 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-15 { revision 2018-04-27 {
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/" +
"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";
skipping to change at page 49, line 11 skipping to change at page 50, line 5
The following figure is the tree diagram of example-newco-acl. In The following figure is the tree diagram of example-newco-acl. In
this example, /ietf-acl:acls/ietf-acl:acl/ietf-acl:aces/ietf-acl:ace/ this example, /ietf-acl:acls/ietf-acl:acl/ietf-acl:aces/ietf-acl:ace/
ietf-acl:matches are augmented with two new choices, protocol- ietf-acl:matches are augmented with two new choices, protocol-
payload-choice and metadata. The protocol-payload-choice uses a payload-choice and metadata. The protocol-payload-choice 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 another in the packet header such as overall packet length. In another
example, /ietf-acl:acls/ietf-acl:acl/ietf-acl:aces/ietf-acl:ace/ietf- example, /ietf-acl:acls/ietf-acl:acl/ietf-acl:aces/ietf-acl:ace/ietf-
acl:actions are augmented with a 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:acls/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:acls/acl:acl/acl:aces/acl:ace/acl:actions: augment /acl:acls/acl:acl/acl:aces/acl:ace/acl:actions:
skipping to change at page 50, line 31 skipping to change at page 51, 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-03-15.yang" <CODE BEGINS> file "ietf-ethertypes@2018-04-27.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 8 skipping to change at page 51, 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-03-15 { revision 2018-04-27 {
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 51, line 46 skipping to change at page 52, line 40
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.
Hex value of 0x22F3."; Hex value of 0x22F3.";
reference reference
"RFC 6325 Routing Bridges (RBridges): Base Protocol "RFC 6325: Routing Bridges (RBridges): Base Protocol
Specification."; Specification.";
} }
enum srp { enum srp {
value 8938; value 8938;
description description
"Stream Reservation Protocol. Hex value of "Stream Reservation Protocol. Hex value of
0x22EA."; 0x22EA.";
reference reference
"IEEE 801.1Q-2011."; "IEEE 801.1Q-2011.";
} }
skipping to change at page 53, line 4 skipping to change at page 53, line 45
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: IPv6 "RFC 8200: Internet Protocol, Version 6 (IPv6)
Specification
RFC 8201: Path MTU Discovery for 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.";
} }
skipping to change at page 53, line 41 skipping to change at page 54, line 34
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: MPLS Architecture."; "RFC 3031: Multiprotocol Label Switching 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: MPLS Architecture."; "RFC 3031: Multiprotocol Label Switching 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: A method for Transmitting PPPoE."; "RFC 2516: A method for Transmitting PPP over Ethernet
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: A method for Transmitting PPPoE."; "RFC 2516: A method for Transmitting PPP over Ethernet
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
 End of changes. 59 change blocks. 
111 lines changed or deleted 144 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/