Generic YANG Data Model for the Management of Operations, Administration, and Maintenance (OAM) Protocols that use Connectionless Communications
draft-ietf-lime-yang-connectionless-oam-14
The information below is for an old version of the document.
| Document | Type |
This is an older version of an Internet-Draft that was ultimately published as RFC 8532.
|
|
|---|---|---|---|
| Authors | Deepak Kumar , Zitao Wang , Qin Wu , Reshad Rahman , Srihari Raghavan | ||
| Last updated | 2017-10-25 (Latest revision 2017-10-24) | ||
| Replaces | draft-kumar-lime-yang-connectionless-oam | ||
| RFC stream | Internet Engineering Task Force (IETF) | ||
| Formats | |||
| Reviews |
GENART Telechat review
(of
-13)
by Elwyn Davies
Ready w/issues
YANGDOCTORS Early review
(of
-05)
by Carl Moberg
On the Right Track
|
||
| Additional resources | Mailing list discussion | ||
| Stream | WG state | Submitted to IESG for Publication | |
| Document shepherd | Carlos Pignataro | ||
| Shepherd write-up | Show Last changed 2017-10-04 | ||
| IESG | IESG state | Became RFC 8532 (Proposed Standard) | |
| Consensus boilerplate | Yes | ||
| Telechat date |
(None)
Needs a YES. Needs 9 more YES or NO OBJECTION positions to pass. |
||
| Responsible AD | Benoît Claise | ||
| Send notices to | Ron Bonica <rbonica@juniper.net>, Carlos Pignataro <cpignata@cisco.com> | ||
| IANA | IANA review state | IANA OK - Actions Needed |
draft-ietf-lime-yang-connectionless-oam-14
TEAS Working Group Y. Lee (Editor)
Internet Draft Dhruv Dhody
Intended Status: Standard Track Satish Karunanithi
Expires: January 2, 2019 Huawei
Ricard Vilalta
CTTC
Daniel King
Lancaster University
Daniele Ceccarelli
Ericsson
July 2, 2018
YANG models for ACTN TE Performance Monitoring Telemetry and Network
Autonomics
draft-lee-teas-actn-pm-telemetry-autonomics-07
Status of this Memo
This Internet-Draft is submitted to IETF in full conformance with
the provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that
other groups may also distribute working documents as Internet-
Drafts.
Internet-Drafts are draft documents valid for a maximum of six
months and may be updated, replaced, or obsoleted by other documents
at any time. It is inappropriate to use Internet-Drafts as
reference material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt
The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html.
This Internet-Draft will expire on January 2, 2019.
Copyright Notice
Copyright (c) 2018 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of
Lee, et al. Expires January 2019 [Page 1]
Internet-Draft ACTN PM Telemetry & Network Autonomics July 2018
publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with
respect to this document. Code Components extracted from this
document must include Simplified BSD License text as described in
Section 4.e of the Trust Legal Provisions and are provided without
warranty as described in the Simplified BSD License.
Abstract
Abstraction and Control of TE Networks (ACTN) refers to the set of
virtual network operations needed to operate, control and manage
large-scale multi-domain, multi-layer and multi-vendor TE networks,
so as to facilitate network programmability, automation, efficient
resource sharing.
This document provides YANG data models that describe Key
Performance Indicator (KPI) telemetry and network autonomics for TE-
tunnels and ACTN VNs.
Table of Contents
1. Introduction...................................................3
1.1. Terminology...............................................3
1.2. Tree Structure - Legend...................................3
2. Use-Cases......................................................4
3. Design of the Data Models......................................5
3.1. TE KPI Telemetry Model....................................6
3.2. ACTN TE KPI Telemetry Model...............................6
4. Notification...................................................8
4.1. YANG Push Subscription Examples...........................8
5. YANG Data Tree.................................................9
6. Yang Data Model...............................................11
6.1. ietf-te-kpi-telemetry model..............................11
6.2. ietf-actn-te-kpi-telemetry model.........................19
7. Security Considerations.......................................22
8. IANA Considerations...........................................22
9. Acknowledgements..............................................22
10. References...................................................22
10.1. Informative References..................................22
10.2. Normative References....................................23
11. Contributors.................................................24
Authors' Addresses...............................................24
Lee, et al. Expires January 2019 [Page 2]
Internet-Draft ACTN PM Telemetry & Network Autonomics July 2018
1. Introduction
Abstraction and Control of TE Networks (ACTN) describes a method for
operating a Traffic Engineered (TE) network (such as an MPLS-TE
network or a layer 1/0 transport network) to provide connectivity
and virtual network services for customers of the TE network [ACTN-
Frame]. The services provided can be optimized to meet the
requirements (such as traffic patterns, quality, and reliability) of
the applications hosted by the customers. Data models are a
representation of objects that can be configured or monitored within
a system. Within the IETF, YANG [RFC6020] is the language of choice
for documenting data models, and YANG models have been produced to
allow configuration or modeling of a variety of network devices,
protocol instances, and network services. YANG data models have been
classified in [Netmod-Yang-Model-Classification] and [Service-YANG].
[ACTN-VN] describes how customers or end to end orchestrators can
request and/or instantiate a generic virtual network service. [ACTN-
Applicability] describes a connection between IETF YANG model
classifications to ACTN interfaces. In particular, it describes the
customer service model can be mapped into the CMI (CNC-MDSC
Interface) of the ACTN architecture.
The YANG model on the ACTN CMI is known as customer service model in
[Service-YANG]. [PCEP-Service-Aware] describes key network
performance data to be considered for end-to-end path computation in
TE networks. Key performance indicator is a term that describes
critical performance data that may affect VN/TE service.
1.1. Terminology
1.2. Tree Structure - Legend
A simplified graphical representation of the data model is used in
Section 5 of this this document. The meaning of the symbols in
these diagrams is defined in [RFC8342].
1.3. Prefixes in Data Node Names
In this document, names of data nodes and other data model objects
are prefixed using the standard prefix associated with the
corresponding YANG imported modules, as shown in Table 1.
Lee, et al. Expires January 2019 [Page 3]
Internet-Draft ACTN PM Telemetry & Network Autonomics July 2018
+---------+------------------------------+-----------------+
| Prefix | YANG module | Reference |
+---------+------------------------------+-----------------+
| rt | ietf-routing-types | [Routing-Types] |
| te | ietf-te | [TE-tunnel] |
| te-types| ietf-te-types | [TE-Types] |
| te-kpi | ietf-te-kpi-telemetry | [This I-D] |
| vn | ietf-actn-vn | [ACTN-VN] |
| actn-tel| ietf-actn-te-kpi-telemetry | {This I-D] |
+---------+------------------------------+-----------------+
Table 1: Prefixes and corresponding YANG modules
2. Use-Cases
[ACTN-PERF] describes use-cases relevant to this draft. It
introduces the dynamic creation, modification and optimization of
services based on the performance monitoring in the Abstraction and
Control of Transport Networks (ACTN) architecture. Figure 1 shows a
high-level workflows for dynamic service control based on traffic
monitoring.
Some of the key points from [ACTN-PERF] are as follows:
. Network traffic monitoring is important to facilitate automatic
discovery of the imbalance of network traffic, and initiate the
network optimization, thus helping the network operator or the
virtual network service provider to use the network more
efficiently and save CAPEX/OPEX.
. Customer services have various SLA requirements, such as
service availability, latency, latency jitter, packet loss
rate, BER, etc. The transport network can satisfy service
availability and BER requirements by providing different
protection and restoration mechanisms. However, for other
performance parameters, there are no such mechanisms. In order
to provide high quality services according to customer SLA, one
possible solution is to measure the service SLA related
performance parameters, and dynamically provision and optimize
services based on the performance monitoring results.
. Performance monitoring in a large scale network could generate
a huge amount of performance information. Therefore, the
appropriate way to deliver the information in CMI and MPI
interfaces should be carefully considered.
Lee, et al. Expires January 2019 [Page 4]
Internet-Draft ACTN PM Telemetry & Network Autonomics July 2018
+-------------------------------------------+
| CNC +-----------------------------+ |
| | Dynamic Service Control APP | |
| +-----------------------------+ |
+-------------------------------------------+
1.Traffic| /|\4.Traffic | /|\
Monitor& | | Monitor | | 8.Traffic
Optimize | | Result 5.Service | | modify &
Policy | | modify& | | optimize
\|/ | optimize Req.\|/ | result
+------------------------------------------------+
| MDSC +-------------------------------+ |
| |Dynamic Service Control Agent | |
| +-------------------------------+ |
| +---------------+ +-------------------+ |
| | Flow Optimize | | vConnection Agent | |
| +---------------+ +-------------------+ |
+------------------------------------------------+
2. Path | /|\3.Traffic | |
Monitor | | Monitor | |7.Path
Request | | Result 6.Path | | modify &
| | modify&"MAC address type";
}
leaf mac-address {
type yang:mac-address;
mandatory true;
description
"MAC Address";
}
description
"MAC Address based TP Addressing.";
}
container ipv4-address {
when "derived-from-or-self(../tp-location-type,"+
"'cl-oam:ipv4-address-type')" {
description
"IPv4 address type";
}
leaf ipv4-address {
type inet:ipv4-address;
mandatory true;
description
"IPv4 Address";
}
description
"IP Address based TP Addressing.";
}
container ipv6-address {
when "derived-from-or-self(../tp-location-type,"+
"'cl-oam:ipv6-address-type')" {
description
"IPv6 address type";
}
leaf ipv6-address {
Kumar, et al. Expires April 27, 2018 [Page 24]
Internet-Draft Connectionless OAM YANG model October 2017
type inet:ipv6-address;
mandatory true;
description
"IPv6 Address";
}
description
"ipv6 Address based TP Addressing.";
}
container tp-attribute {
when "derived-from-or-self(../tp-location-type,"+
"'cl-oam:tp-attribute-type')" {
description
"Test point attribute type";
}
leaf tp-attribute-type {
type address-attribute-type;
description
"Test point type.";
}
choice tp-attribute-value {
description
"Test point value.";
case ip-prefix {
leaf ip-prefix {
type inet:ip-prefix;
description
"IP prefix.";
}
}
case bgp {
leaf bgp {
type inet:ip-prefix;
description
"BGP Labeled Prefix ";
}
}
case tunnel {
leaf tunnel-interface {
type uint32;
description
"VPN Prefix ";
}
}
case pw {
leaf remote-pe-address {
type inet:ip-address;
description
Kumar, et al. Expires April 27, 2018 [Page 25]
Internet-Draft Connectionless OAM YANG model October 2017
"Remote pe address.";
}
leaf pw-id {
type uint32;
description
"Pseudowire ID is a non-zero 32-bit ID.";
reference
"RFC 4379 :Detecting Multi-Protocol Label
Switched (MPLS) Data Plane Failures";
}
}
case vpls {
leaf route-distinguisher {
type rt:route-distinguisher;
description
"Route Distinguisher is an 8 octets identifier
used to distinguish information about various
L2VPN advertised by a node.";
reference
"RFC 4379 :Detecting Multi-Protocol Label
Switched (MPLS) Data Plane Failures";
}
leaf sender-ve-id {
type uint16;
description
"Sender's VE ID. The VE ID (VPLS Edge Identifier)
is a 2-octet identifier.";
reference
"RFC 4379 :Detecting Multi-Protocol Label
Switched (MPLS) Data Plane Failures";
}
leaf receiver-ve-id {
type uint16;
description
"Receiver's VE ID.The VE ID (VPLS Edge Identifier)
is a 2-octet identifier.";
reference
"RFC 4379 :Detecting Multi-Protocol Label
Switched (MPLS) Data Plane Failures";
}
}
case mpls-mldp {
choice root-address {
description
"Root address choice.";
case ip-address {
leaf source-address {
Kumar, et al. Expires April 27, 2018 [Page 26]
Internet-Draft Connectionless OAM YANG model October 2017
type inet:ip-address;
description
"IP address.";
}
leaf group-ip-address {
type inet:ip-address;
description
"Group ip address.";
}
}
case vpn {
leaf as-number {
type inet:as-number;
description
"The AS number represents autonomous system
numbers which identify an Autonomous System.";
}
}
case global-id {
leaf lsp-id {
type string;
description
"LSP ID is an identifier of a LSP
within a MPLS network.";
reference
"RFC 4379 :Detecting Multi-Protocol Label
Switched (MPLS) Data Plane Failures";
}
}
}
}
}
description
"Test Point Attribute Container";
}
container system-info {
when "derived-from-or-self(../tp-location-type,"+
"'cl-oam:system-id-address-type')" {
description
"System id address type";
}
leaf system-id {
type rt:router-id;
description
"System ID assigned to this node.";
}
description
Kumar, et al. Expires April 27, 2018 [Page 27]
Internet-Draft Connectionless OAM YANG model October 2017
"system ID container.";
}
description
"TP Address";
}
grouping tp-address-ni {
description
"Test point address with VRF.";
leaf ni {
type routing-instance-ref;
description
"The ni is used to describe virtual resource partitioning
that may be present on a network device.Example of common
industry terms for virtual resource partitioning is VRF
instance.";
}
uses tp-address;
}
grouping connectionless-oam-tps {
list oam-neighboring-tps {
key "index";
leaf index {
type uint16{
range "0..65535";
}
description
"List of related neighboring test points in adjacent
layers up and down the stack for the same interface
that are related to the current test point";
}
leaf position {
type int8 {
range "-1..1";
}
default "0";
description
"The relative position
of neighboring test point
corresponding to the current
test point.Level 0 indicates no neighboring
test points placed before or after the current
test point in the same layer.-1 means there is
a neighboring test point placed before the current
test point in the same layer and +1 means there is
a neighboring test point placed after the current
test point in same layer.";
}
choice tp-location {
Kumar, et al. Expires April 27, 2018 [Page 28]
Internet-Draft Connectionless OAM YANG model October 2017
case mac-address {
leaf mac-address-location {
type yang:mac-address;
description
"MAC Address";
}
description
"MAC Address based TP Addressing.";
}
case ipv4-address {
leaf ipv4-address-location {
type inet:ipv4-address;
description
"Ipv4 Address";
}
description
"IP Address based TP Addressing.";
}
case ipv6-address {
leaf ipv6-address-location {
type inet:ipv6-address;
description
"IPv6 Address";
}
description
"IPv6 Address based TP Addressing.";
}
case as-number {
leaf as-number-location {
type inet:as-number;
description
"AS number location";
}
description
"AS number for point to multipoint OAM";
}
case system-id {
leaf system-id-location {
type router-id;
description
"System id location";
}
description
"System ID";
}
description
"TP location.";
Kumar, et al. Expires April 27, 2018 [Page 29]
Internet-Draft Connectionless OAM YANG model October 2017
}
description
"List of neighboring test points in the same layer that are related to current test
point. If the neighboring test-point is placed after the current test point, the
position is specified as +1. If neighboring test-point
is placed before the current test point, the position is specified
as -1, if no neighboring test points placed before or after the current
test point in the same layer, the position is specified as 0.";
}
description
"Connectionless OAM related neighboring test points list.";
}
grouping tp-technology {
choice technology {
default "technology-null";
case technology-null {
description
"This is a placeholder when no technology is needed.";
leaf tech-null {
type empty;
description
"There is no technology to be defined.";
}
}
description
"Technology choice.";
}
description
"OAM Technology";
}
grouping tp-tools {
description
"Test Point OAM Toolset.";
container tp-tools {
leaf continuity-check {
type boolean;
mandatory true;
description
"A flag indicating whether or not the
continuity check function is supported.";
reference
"RFC 792: INTERNET CONTROL MESSAGE PROTOCOL.
RFC 4443: Internet Control Message Protocol (ICMPv6)
for the Internet Protocol Version 6 (IPv6) Specification.
RFC 5880: Bidirectional Forwarding Detection.
RFC 5881: BFD for IPv4 and IPv6.
RFC 5883: BFD for Multihop Paths.
Kumar, et al. Expires April 27, 2018 [Page 30]
Internet-Draft Connectionless OAM YANG model October 2017
RFC 5884: BFD for MPLS Label Switched Paths.
RFC 5885: BFD for PW VCCV.
RFC 6450: Multicast Ping Protocol.
RFC 8029: Detecting Multiprotocol Label Switched
(MPLS) Data-Plane Failures.";
}
leaf path-discovery {
type boolean;
mandatory true;
description
"A flag indicating whether or not the
path discovery function is supported.";
reference
"RFC 792: INTERNET CONTROL MESSAGE PROTOCOL.
RFC 4443: Internet Control Message Protocol (ICMPv6)
for the Internet Protocol Version 6 (IPv6) Specification.
RFC 4884: Extended ICMP to Support Multi-part Message.
RFC 5837:Extending ICMP for Interface.
and Next-Hop Identification.
RFC 8029: Detecting Multiprotocol Label Switched (MPLS)
Data-Plane Failures.";
}
description
"Container for test point OAM tools set.";
}
}
grouping test-point-location-info {
uses tp-technology;
uses tp-tools;
anydata root {
yangmnt:mount-point "root";
description
"Root for models supported per
test point";
}
uses connectionless-oam-tps;
description
"Test point Location";
}
grouping test-point-locations {
description
"Group of test point locations.";
leaf tp-location-type {
type identityref {
base tp-address-technology-type;
}
description
"Test point location type.";
amp; | | optimize
\|/ | optimize Req.\|/ | result
+-------------------------------------------------------+
| PNC +----------------------+ +----------------------+ |
| | Network Provisioning | |Abstract Topology Gen.| |
| +----------------------+ +----------------------+ |
| +------------------+ +--------------------+ |
| |Network Monitoring| |Physical Topology DB| |
| +------------------+ +--------------------+ |
+-------------------------------------------------------+
Figure 1 Workflows for dynamic service control based on traffic
monitoring
3. Design of the Data Models
The YANG models developed in this document describe two models:
(i) TE KPI Telemetry Model which provides the TE-Tunnel level of
performance monitoring mechanism (See Section 4 for details)
(ii) ACTN TE KPI Telemetry Model which provides the VN level of the
aggregated performance monitoring mechanism (See Section 5
for details)
Lee, et al. Expires January 2019 [Page 5]
Internet-Draft ACTN PM Telemetry & Network Autonomics July 2018
The models include -
(i) Performance Telemetry details as measured during the last
interval, ex delay.
(ii) Scaling Intent based on with TE/VN could be scaled in/out.
[Editor's Note - Need to decide if scaling and telemetry can be in
the same model as per the current draft.]
3.1. TE KPI Telemetry Model
This module describes performance telemetry for TE-tunnel model. The
telemetry data is augmented to tunnel state. This module also
allows autonomic traffic engineering scaling intent configuration
mechanism on the TE-tunnel level. Various conditions can be set for
auto-scaling based on the telemetry data.
The TE KPI Telemetry Model augments the TE-Tunnel Model to enhance
TE performance monitoring capability. This monitoring capability
will facilitate proactive re-optimization and reconfiguration of TEs
based on the performance monitoring data collected via the TE KPI
Telemetry YANG model.
+------------+ +--------------+
| TE-Tunnel | | TE KPI |
| Model |<---------| Telemetry |
+------------+ augments | Model |
+--------------+
3.2. ACTN TE KPI Telemetry Model
This module describes performance telemetry for ACTN VN model. The
telemetry data is augmented both at the VN Level as well as
individual VN member level. This module also allows autonomic
traffic engineering scaling intent configuration mechanism on the VN
Lee, et al. Expires January 2019 [Page 6]
Internet-Draft ACTN PM Telemetry & Network Autonomics July 2018
level. Scale in/out criteria might be used for network autonomics in
order the controller to react to a certain set of variations in
monitored parameters.
Moreover, this module also provides mechanism to define aggregated
telemetry parameters as a grouping of underlying VN level telemetry
parameters. Grouping operation (such as maximum, mean) could be set
at the time of configuration. For example, if maximum grouping
operation is used for delay at the VN level, the VN telemetry data
is reported as the maximum {delay_vn_member_1, delay_vn_member_2,..
delay_vn_member_N}. Thus, this telemetry abstraction mechanism
allows the grouping of a certain common set of telemetry values
under a grouping operation. This can be done at the VN-member level
to suggest how the E2E telemetry be inferred from the per domain
tunnel created and monitored by PNCs. One proposed example is the
following:
+------------------------------------------------------------+
| CNC |
| |
+------------------------------------------------------------+
1.CNC sets the | /|\ 2. MDSC gets VN Telemetry
grouping op, and | |
subscribes to the | | VN KPI TELEMETRY (VN Level)
VN level telemetry for | | VN Utilized-bw-percentage:
Delay and | | Minimum across VN Members
Utilized-bw-pecentage | | VN Delay: Maximum across VN
\|/ | Members
+------------------------------------------------------------+
| MDSC |
| |
+------------------------------------------------------------+
The ACTN VN TE-Telemetry Model augments the basic ACTN VN model to
enhance VN monitoring capability. This monitoring capability will
facilitate proactive re-optimization and reconfiguration of VNs
based on the performance monitoring data collected via the ACTN VN
Telemetry YANG model.
+----------+ +--------------+
| ACTN VN | augments | ACTN |
| Model |<---------| TE-Telemetry |
+----------+ | Model |
+--------------+
Lee, et al. Expires January 2019 [Page 7]
Internet-Draft ACTN PM Telemetry & Network Autonomics July 2018
4. Notification
This model does not define specific notifications. To enable
notifications, the mechanism defined in [I-D.ietf-netconf-yang-push]
and [I-D.ietf-netconf-rfc5277bis] can be used. This mechanism
currently allows the user to:
. Subscribe notifications on a per client basis.
. Specify subtree filters or xpath filters so that only interested
contents will be sent.
. Specify either periodic or on-demand notifications.
4.1. YANG Push Subscription Examples
Below example shows the way for a client to subscribe for the
telemetry information for a particular tunnel (Tunnel1). The
telemetry parameter that the client is interested in is the utilized
bandwidth percentage.
<netconf:rpc netconf:message-id="101"
xmlns:netconf="urn:ietf:params:xml:ns:netconf:base:1.0">
<establish-subscription
xmlns="urn:ietf:params:xml:ns:yang:ietf-yang-push:1.0">
<filter netconf:type="subtree">
<te xmlns="urn:ietf:params:xml:ns:yang:ietf-te">
<tunnels>
<tunnel>
<name>Tunnel1</name>
<identifier/>
<state>
<te-telemetry
xmlns="urn:ietf:params:xml:ns:yang:ietf-te-kpi-telemetry">
<utilized-
percentage/>
</te-telemetry>
</state>
</tunnel>
Lee, et al. Expires January 2019 [Page 8]
Internet-Draft ACTN PM Telemetry & Network Autonomics July 2018
</tunnels>
</te>
</filter>
<period>500</period>
<encoding>encode-xml</encoding>
</establish-subscription>
</netconf:rpc>
This example shows the way for a client to subscribe for the
telemetry information for all VNs. The telemetry parameter that the
client is interested in is one-way delay and utilized bandwidth
percentage.
<netconf:rpc netconf:message-id="101"
xmlns:netconf="urn:ietf:params:xml:ns:netconf:base:1.0">
<establish-subscription
xmlns="urn:ietf:params:xml:ns:yang:ietf-yang-push:1.0">
<filter netconf:type="subtree">
<actn-state xmlns="urn:ietf:params:xml:ns:yang:ietf-actn-
vn">
<vn>
<vn-list>
<vn-id/>
<vn-name/>
<vn-
telemetry xmlns="urn:ietf:params:xml:ns:yang:ietf-actn-te-kpi-
telemetry">
<one-way-delay/>
<utilized-
percentage/>
</vn-telemetry >
</vn-list>
</vn>
</actn-state>
</filter>
<period>500</period>
</establish-subscription>
</netconf:rpc>
5. YANG Data Tree
Lee, et al. Expires January 2019 [Page 9]
Internet-Draft ACTN PM Telemetry &Kumar, et al. Expires April 27, 2018 [Page 31]
Internet-Draft Connectionless OAM YANG model October 2017
}
container ipv4-location-type {
when "derived-from-or-self(../tp-location-type,"+
"'cl-oam:ipv4-address-type')" {
description
"When test point location type is equal to ipv4 address.";
}
container test-point-ipv4-location-list {
list test-point-locations {
key "ipv4-location ni";
leaf ipv4-location {
type inet:ipv4-address;
description
"IPv4 Address.";
}
leaf ni {
type routing-instance-ref;
description
"The ni is used to describe the
corresponding network instance";
}
uses test-point-location-info;
description
"List of test point locations.";
}
description
"Serves as top-level container
for test point location list.";
}
description
"ipv4 location type container.";
}
container ipv6-location-type {
when "derived-from-or-self(../tp-location-type,"+
"'cl-oam:ipv6-address-type')" {
description
"when test point location is equal to ipv6 address";
}
container test-point-ipv6-location-list {
list test-point-locations {
key "ipv6-location ni";
leaf ipv6-location {
type inet:ipv6-address;
description
"IPv6 Address.";
}
leaf ni {
Kumar, et al. Expires April 27, 2018 [Page 32]
Internet-Draft Connectionless OAM YANG model October 2017
type routing-instance-ref;
description
"The ni is used to describe the
corresponding network instance";
}
uses test-point-location-info;
description
"List of test point locations.";
}
description
"Serves as top-level container
for test point location list.";
}
description
"ipv6 location type container.";
}
container mac-location-type {
when "derived-from-or-self(../tp-location-type,"+
"'cl-oam:mac-address-type')" {
description
"when test point location type is equal to mac address.";
}
container test-point-mac-address-location-list {
list test-point-locations {
key "mac-address-location";
leaf mac-address-location {
type yang:mac-address;
description
"MAC Address";
}
uses test-point-location-info;
description
"List of test point locations.";
}
description
"Serves as top-level container
for test point location list.";
}
description
"mac address location type container.";
}
container group-as-number-location-type {
when "derived-from-or-self(../tp-location-type,"+
"'cl-oam:as-number-address-type')" {
description
"when test point location type is equal to as-number.";
}
Kumar, et al. Expires April 27, 2018 [Page 33]
Internet-Draft Connectionless OAM YANG model October 2017
container test-point-as-number-location-list {
list test-point-locations {
key "as-number-location";
leaf as-number-location {
type inet:as-number;
description
"AS number for point to multi point OAM.";
}
leaf ni {
type routing-instance-ref;
description
"The ni is used to describe the
corresponding network instance";
}
uses test-point-location-info;
description
"List of test point locations.";
}
description
"Serves as top-level container
for test point location list.";
}
description
"as number location type container.";
}
container group-system-id-location-type {
when "derived-from-or-self(../tp-location-type,"+
"'cl-oam:system-id-address-type')" {
description
"when test point location type is equal to system-info.";
}
container test-point-system-info-location-list {
list test-point-locations {
key "system-id-location";
leaf system-id-location {
type inet:uri;
description
"System Id.";
}
leaf ni {
type routing-instance-ref;
description
"The ni is used to describe the
corresponding network instance";
}
uses test-point-location-info;
description
"List of test point locations.";
Kumar, et al. Expires April 27, 2018 [Page 34]
Internet-Draft Connectionless OAM YANG model October 2017
}
description
"Serves as top-level container for
test point location list.";
}
description
"system ID location type container.";
}
}
augment "/nd:networks/nd:network/nd:node" {
description
"Augment test points of connectionless oam.";
uses test-point-locations;
}
grouping timestamp {
description
"Grouping for timestamp.";
leaf timestamp-type {
type identityref {
base timestamp-type;
}
description
"Type of Timestamp, such as Truncated PTP, NTP.";
}
container timestamp-64bit {
when "derived-from-or-self(../timestamp-type, 'cl-oam:truncated-ptp')"+
"or derived-from-or-self(../timestamp-type,'cl-oam:ntp64')" {
description
"Only applies when Truncated NTP or 64bit NTP Timestamp.";
}
leaf timestamp-sec {
type uint32;
description
"Absolute timestamp in seconds as per IEEE1588v2
or seconds part in 64-bit NTP timestamp.";
}
leaf timestamp-nanosec {
type uint32;
description
"Fractional part in nanoseconds as per IEEE1588v2
or Fractional part in 64-bit NTP timestamp.";
}
description
"Container for 64bit timestamp.";
}
container timestamp-80bit {
when "derived-from-or-self(../timestamp-type, 'cl-oam:ptp80')"{
Kumar, et al. Expires April 27, 2018 [Page 35]
Internet-Draft Connectionless OAM YANG model October 2017
description
"Only applies when 80bit PTP Timestamp.";
}
if-feature ptp-long-format;
leaf timestamp-sec {
type uint64 {
range "0..281474976710656";
}
description
"48bit Timestamp in seconds as per IEEE1588v2.";
}
leaf timestamp-nanosec {
type uint32;
description
"Fractional part in nanoseconds as per IEEE1588v2
or Fractional part in 64-bit NTP timestamp.";
}
description
"Container for 64bit timestamp.";
}
container ntp-timestamp-32bit {
when "derived-from-or-self(../timestamp-type, 'cl-oam:truncated-ntp')"{
description
"Only applies when 32 bit NTP Short format Timestamp.";
}
if-feature ntp-short-format;
leaf timestamp-sec {
type uint16;
description
"Timestamp in seconds as per short format NTP.";
}
leaf timestamp-nanosec {
type uint16;
description
"Truncated Fractional part in 16-bit NTP timestamp.";
}
description
"Container for 64bit timestamp.";
}
container icmp-timestamp-32bit {
when "derived-from-or-self(../timestamp-type, 'cl-oam:icmp-ntp')"{
description
"Only applies when Truncated NTP or 64bit NTP Timestamp.";
}
if-feature icmp-timestamp;
leaf timestamp-millisec {
type uint32;
Kumar, et al. Expires April 27, 2018 [Page 36]
Internet-Draft Connectionless OAM YANG model October 2017
description
"timestamp in milliseconds for ICMP timestamp.";
}
description
"Container for 32bit timestamp.";
}
}
grouping path-discovery-data {
description
"Path discovery related data output from nodes.";
container src-test-point {
description
"Source test point.";
uses tp-address-ni;
}
container dest-test-point {
description
"Destination test point.";
uses tp-address-ni;
}
leaf sequence-number {
type uint64;
default "0";
description
"Sequence number in data packets.A value of
zero indicates that no sequence number is sent.";
}
leaf hop-cnt {
type uint8;
default "0";
description
"Hop count.A value of zero indicates
that no hop count is sent";
}
uses session-packet-statistics;
uses session-error-statistics;
uses session-delay-statistics;
uses session-jitter-statistics;
container path-verification {
description
"Optional path verification related information.";
leaf flow-info {
type string;
description
"Informations that refers to the flow.";
}
uses session-path-verification-statistics;
Kumar, et al. Expires April 27, 2018 [Page 37]
Internet-Draft Connectionless OAM YANG model October 2017
}
container path-trace-info {
description
"Optional path trace per-hop test point information.
The path trace information list has typically a single
element for per-hop cases like path-discovery RPC operation
but allows a list of hop related information for other types of
data retrieval methods.";
list path-trace-info-list {
key "index";
description
"Path trace information list.";
leaf index {
type uint32;
description
"Trace information index.";
}
uses tp-address-ni;
uses timestamp;
leaf ingress-intf-name {
type if:interface-ref;
description
"Ingress interface name";
}
leaf egress-intf-name {
type if:interface-ref;
description
"Egress interface name";
}
leaf queue-depth {
type uint32;
description
"Length of the queue of the interface from where
the packet is forwarded out. The queue depth could
be the current number of memory buffers used by the
queue and a packet can consume one or more memory buffers
thus constituting device-level information.";
}
leaf transit-delay {
type uint32;
description
"Time in nano seconds
packet spent transiting a node.";
}
leaf app-meta-data {
type uint64;
description
Kumar, et al. Expires April 27, 2018 [Page 38]
Internet-Draft Connectionless OAM YANG model October 2017
"Application specific
data added by node.";
}
}
}
}
grouping continuity-check-data {
description
"Continuity check data output from nodes.";
container src-test-point {
description
"Source test point.";
uses tp-address-ni;
leaf egress-intf-name {
type if:interface-ref;
description
"Egress interface name.";
}
}
container dest-test-point {
description
"Destination test point.";
uses tp-address-ni;
leaf ingress-intf-name {
type if:interface-ref;
description
"Ingress interface name.";
}
}
leaf sequence-number {
type uint64;
default "0";
description
"Sequence number in data packets.A value of
zero indicates that no sequence number is sent.";
}
leaf hop-cnt {
type uint8;
default "0";
description
"Hop count.A value of zero indicates
that no hop count is sent";
}
uses session-packet-statistics;
uses session-error-statistics;
uses session-delay-statistics;
uses session-jitter-statistics;
Kumar, et al. Expires April 27, 2018 [Page 39]
Internet-Draft Connectionless OAM YANG model October 2017
}
container cc-session-statistics-data {
if-feature "continuity-check";
config false;
description
"CC operational information.";
container cc-ipv4-sessions-statistics {
description
"CC ipv4 sessions";
uses cc-session-statistics;
}
container cc-ipv6-sessions-statistics {
description
"CC ipv6 sessions";
uses cc-session-statistics;
}
}
}
<CODE ENDS>
5. Connectionless model applicability
The "ietf-connectionless-oam" model defined in this document provides
a technology-independent abstraction of key OAM constructs for
connectionless protocols. This model can be further extended to
include technology specific details, e.g., adding new data nodes with
technology specific functions and parameters into proper anchor
points of the base model, so as to develop a technology-specific
connectionless OAM model.
This section demonstrates the usability of the connectionless YANG
OAM data model to various connectionless OAM technologies, e.g., BFD,
LSP ping. Note that, in this section, several snippets of
technology-specific model extensions are presented for illustrative
purposes. The complete model extensions should be worked on in
respective protocol working groups.
5.1. BFD Extension
RFC 7276 defines BFD as a connection-oriented protocol. It is used
to monitor a connectionless protocol in the case of basic BFD for IP.
Kumar, et al. Expires April 27, 2018 [Page 40]
Internet-Draft Connectionless OAM YANG model October 2017
5.1.1. Augment Method
The following sections shows how the "ietf-connectionless-oam" model
can be extended to cover BFD technology. For this purpose, a set of
extension are introduced such as technology-type extension and test-
point attributes extension.
Note that a dedicated BFD YANG data model [I-D.ietf-bfd-yang] is also
standardized. Augmentation of the "ietf-connectionless-oam" model
with BFD specific details provides an alternative approach that
provides a unified view of management information across various OAM
protocols. The BFD specific details can be the grouping defined in
the BFD model avoiding duplication of effort.
5.1.1.1. Technology type extension
No BFD technology type has been defined in the "ietf-connectionless-
oam" model. Therefore a technology type extension is required in the
model Extension.
The snippet below depicts an example of adding the "bfd" type as an
augment to the ietf-connectionless-oam" model:
augment "/nd:networks/nd:network/nd:node/"
+"coam:location-type/coam:ipv4-location-type"
+"/coam:test-point-ipv4-location-list/"
+"coam:test-point-locations/coam:technology"
{
leaf bfd{
type string;
}
}
5.1.1.2. Test point attributes extension
To support BFD technology, the "ietf-connectionless-oam" model can be
extended by adding specific parameters into the "test-point-
locations" list and/or adding a new location type such as "BFD over
MPLS TE" under "location-type".
5.1.1.2.1. Define and insert new nodes into corresponding test-point-
location
In the "ietf-connectionless-oam" model, multiple "test-point-
location" lists are defined under the "location-type" choice node.
Therefore, to derive a model for some BFD technologies ( such as ip
single-hop, ip multi-hops, etc), data nodes for BFD specific details
need to be added into corresponding "test-point-locations" list. In
Kumar, et al. Expires April 27, 2018 [Page 41]
Internet-Draft Connectionless OAM YANG model October 2017
this section, some groupings which are defined in [I-D.ietf-bfd-yang]
are reused as follow:
The snippet below shows how the "ietf-connectionless-oam" model can
be extended to support "BFD IP single-hop":
augment "/nd:networks/nd:network/nd:node/"
+"coam:location-type/coam:ipv4-location-type"
+"/coam:test-point-ipv4-location-list/"
+"coam:test-point-locations"
{
container session-cfg {
description "BFD IP single-hop session configuration";
list sessions {
key "interface dest-addr";
description "List of IP single-hop sessions";
leaf interface {
type if:interface-ref;
description
"Interface on which the BFD session is running.";
}
leaf dest-addr {
type inet:ip-address;
description "IP address of the peer";
}
uses bfd:bfd-grouping-common-cfg-parms;
uses bfd:bfd-grouping-echo-cfg-parms;
}
}
}
Similar augmentations can be defined to support other BFD
technologies such as BFD IP multi-hop, BFD over MPLS, etc.
5.1.1.2.2. Add new location-type cases
In the "ietf-connectionless-oam" model, If there is no appropriate
"location type" case that can be extended, a new "location-type" case
can be defined and inserted into the "location-type" choice node.
Therefore, the model user can flexibly add "location-type" to support
other type of test point which are not defined in the "ietf-
connectionless-oam" model. In this section, a new "location-type"
case is added and some groupings that are defined in
[I-D.ietf-bfd-yang] are reused as follows:
The snippet below shows how the "ietf-connectionless-oam" model can
be extended to support "BFD over MPLS-TE":
Kumar, et al. Expires April 27, 2018 [Page 42]
Internet-Draft Connectionless OAM YANG model October 2017
augment "/nd:networks/nd:network/nd:node/coam:location-type"{
case te-location{
list test-point-location-list{
key "tunnel-name";
leaf tunnel-name{
type leafref{
path "/te:te/te:tunnels/te:tunnel/te:name";
}
description
"point to a te instance.";
}
uses bfd:bfd-grouping-common-cfg-parms;
uses bfd-mpls:bfd-encap-cfg;
}
}
}
Similar augmentations can be defined to support other BFD
technologies such as BFD over LAG, etc.
5.1.2. Schema Mount
Another alternative method is using the schema mount mechanism [I-
D.ietf-netmod-schema-mount] in the "ietf-connectionless-oam" model.
Within the "test-point-locations" list, a "root" attribute is defined
to provide a mount point for models mounted per "test-point-
locations". Therefore, the "ietf-connectionless-oam" model can
provide a place in the node hierarchy where other OAM YANG data
models can be attached, without any special extension in the "ietf-
connectionless-oam" YANG data models [I-D.ietf-netmod-schema-mount].
Note that the limitation of the Schema Mount method is it is not
allowed to specify certain modules that are required to be mounted
under a mount point.
The snippet below depicts the definition of the "root" attribute.
anydata root {
yangmnt:mount-point root;
description
"Root for models supported per
test point";
}
The following section shows how the "ietf-connectionless-oam" model
can use schema mount to support BFD technology.
Kumar, et al. Expires April 27, 2018 [Page 43]
Internet-Draft Connectionless OAM YANG model October 2017
5.1.2.1. BFD Modules be populated in schema-mount
To support BFD technology, "ietf-bfd-ip-sh" and "ietf-bfd-ip-mh" YANG
modules might be populated in the "schema-mounts" container:
<schema-mounts
xmlns="urn:ietf:params:xml:ns:yang:ietf-yang-schema-mount">
<mount-point>
<module> ietf-connectionless-oam </module>
<name>root</name>
<use-schema>
<name>root</name>
</use-schema>
</mount-point>
<schema>
<name>root</name>
<module>
<name>ietf-bfd-ip-sh </name>
<revision>2016-07-04</revision>
<namespace>
urn:ietf:params:xml:ns:yang:ietf-bfd-ip-sh
</namespace>
<conformance-type>implement</conformance-type>
</module>
<module>
<name>ietf-bfd-ip-mh </name>
<revision> 2016-07-04</revision>
<namespace>
urn:ietf:params:xml:ns:yang:ietf-bfd-ip-mh
</namespace>
<conformance-type>implement</conformance-type>
</module>
</schema>
</schema-mounts>
and the " ietf-connectionless-oam " module might have:
Kumar, et al. Expires April 27, 2018 [Page 44]
Internet-Draft Connectionless OAM YANG model October 2017
<ietf-connectionless-oam
uri="urn:ietf:params:xml:ns:yang:ietf-connectionless-oam">
......
<test-point-locations>
<ipv4-location>192.0.2.1</ipv4-location>
......
<root>
<ietf-bfd-ip-sh uri="urn:ietf:params:xml:ns:yang:ietf-bfd-ip-sh">
<ip-sh>
foo
......
</ip-sh>
</ietf-bfd-ip-sh>
<ietf-bfd-ip-mh uri="urn:ietf:params:xml:ns:yang:ietf-bfd-ip-mh">
<ip-mh>
foo
......
</ip-mh>
</ietf-bfd-ip-mh>
</root>
</test-point-locations>
</ietf-connectionless-oam>
5.2. LSP ping extension
5.2.1. Augment Method
The following sections shows how the "ietf-connectionless-oam" model
can be extended to support LSP ping technology. For this purpose, a
set of extensions are introduced such as the "technology-type"
extension and the test-point "attributes" extension.
Note that a LSP Ping YANG data model
[I-D.zheng-mpls-lsp-ping-yang-cfg] has been standardized. As with
BFD, users can choose to use the "ietf-connectioless-oam" as basis
and augment the "ietf- connectionless-oam" model with LSP Ping
specific details in the model extension to provide a unified view
across different technologies. The LSP Ping specific details can be
the grouping defined in the LSP ping model to avoid duplication of
effort.
5.2.1.1. Technology type extension
No lsp-ping technology type has been defined in the "ietf-
connectionless-oam" model. Therefore a technology type extension is
required in the model extension.
Kumar, et al. Expires April 27, 2018 [Page 45]
Internet-Draft Connectionless OAM YANG model October 2017
The snippet below depicts an example of augmenting the "ietf-
connectionless-oam" with "lsp-ping" type:
augment "/nd:networks/nd:network/nd:node/"
+"coam:location-type/coam:ipv4-location-type"
+"/coam:test-point-ipv4-location-list/"
+"coam:test-point-locations/coam:technology"
{
leaf lsp-ping{
type string;
}
}
5.2.1.2. Test point attributes extension
To support lsp-ping, the "ietf-connectionless-oam" model can be
extended and add lsp-ping specific parameters can be defined and
under "test-point-locations" list.
User can reuse the attributes or groupings which are defined in
[I-D.zheng-mpls-lsp-ping-yang-cfg] as follows:
The snippet below depicts an example of augmenting the "test-point-
locations" list with lsp ping attributes:
augment "/nd:networks/nd:network/nd:node/"
+"coam:location-type/coam:ipv4-location-type"
+"/coam:test-point-ipv4-location-list/"
+"coam:test-point-locations"
{
list lsp-ping {
key "lsp-ping-name";
leaf lsp-ping-name {
type string {
length "1..31";
}
mandatory "true";
description "LSP Ping test name.";
......
}
5.2.2. Schema Mount
And another alternative method is using schema mount mechanism
[I-D.ietf-netmod-schema-mount] in the "ietf-connectionless-oam".
Within the "test-point-locations" list, a "root" attribute is defined
to provide a mounted point for models mounted per "test-point-
locations". Therefore, the "ietf-connectionless-oam" model can
Kumar, et al. Expires April 27, 2018 [Page 46]
Internet-Draft Connectionless OAM YANG model October 2017
provide a place in the node hierarchy where other OAM YANG data
models can be attached, without any special extension in the "ietf-
connectionless-oam" YANG data models [I-D.ietf-netmod-schema-mount].
Note that the limitation of the Schema Mount method is it is not
allowed to specify certain modules that are required to be mounted
under a mount point.
The snippet below depicts the definition of "root" attribute.
anydata root {
yangmnt:mount-point root;
description
"Root for models supported per
test point";
}
The following section shows how the "ietf-connectionless-oam" model
can use schema mount to support LSP-PING technology.
5.2.2.1. LSP-PING Modules be populated in schema-mount
To support LSP-PING technology, "ietf-lspping" YANG module
[I-D.zheng-mpls-lsp-ping-yang-cfg] might be populated in the "schema-
mounts" container:
<schema-mounts
xmlns="urn:ietf:params:xml:ns:yang:ietf-yang-schema-mount">
<mount-point>
<module> ietf-connectionless-oam </module>
<name>root</name>
<use-schema>
<name>root</name>
</use-schema>
</mount-point>
<schema>
<name>root</name>
<module>
<name>ietf-lspping </name>
<revision>2016-03-18</revision>
<namespace>
urn:ietf:params:xml:ns:yang: ietf-lspping
</namespace>
<conformance-type>implement</conformance-type>
</module>
</schema>
</schema-mounts>
and the " ietf-connectionless-oam " module might have:
Kumar, et al. Expires April 27, 2018 [Page 47]
Internet-Draft Connectionless OAM YANG model October 2017
<ietf-connectionless-oam
uri="urn:ietf:params:xml:ns:yang:ietf-connectionless-oam">
......
<test-point-locations>
<ipv4-location> 192.0.2.1</ipv4-location>
......
<root>
<ietf-lspping uri="urn:ietf:params:xml:ns:yang:ietf-lspping">
<lsp-pings>
foo
......
</lsp-pings>
</ietf-lspping>
</root>
</test-point-locations>
</ietf-connectionless-oam>
6. Security Considerations
The YANG module defined in this document is designed to be accessed
via network management protocols such as NETCONF [RFC6241] or
RESTCONF [RFC8040]. The lowest NETCONF layer is the secure transport
layer, and the mandatory-to-implement secure transport is Secure
Shell (SSH) [RFC6242]. The lowest RESTCONF layer is HTTPS, and the
mandatory-to-implement secure transport is TLS [RFC5246].
The NETCONF access control model [RFC6536] provides the means to
restrict access for particular NETCONF or RESTCONF users to a
preconfigured subset of all available NETCONF or RESTCONF protocol
operations and content.
There are a number of data nodes defined in this YANG module that are
writable/creatable/deletable (i.e., config true, which is the
default). These data nodes may be considered sensitive or vulnerable
in some network environments. Write operations (e.g., edit-config)
to these data nodes without proper protection can have a negative
effect on network operations.
The vulnerable "config true" subtrees and data nodes are the
following:
/nd:networks/nd:network/nd:node/cl-oam:location-type/cl-oam:ipv4-
location-type/cl-oam:test-point-ipv4-location-list/cl-oam:test-
point-locations/
/nd:networks/nd:network/nd:node/cl-oam:location-type/cl-oam:ipv6-
location-type/cl-oam:test-point-ipv6-location-list/cl-oam:test-
point-locations/
Kumar, et al. Expires April 27, 2018 [Page 48]
Internet-Draft Connectionless OAM YANG model October 2017
/nd:networks/nd:network/nd:node/cl-oam:location-type/cl-oam:mac-
location-type/cl-oam:test-point-mac-address-location-list/cl-
oam:test-point-locations/
/nd:networks/nd:network/nd:node/cl-oam:location-type/cl-oam:group-
as-number-location-type/cl-oam:test-point-as-number-location-list/
cl-oam:test-point-locations/
/nd:networks/nd:network/nd:node/cl-oam:location-type/cl-oam:group-
system-id-location-type/cl-oam:test-point-system-info-location-
list/cl-oam:test-point-locations/
Unauthorized access to any of these lists can adversely affect OAM
management system handling of end-to-end OAM and coordination of OAM
within underlying network layers. This may lead to inconsistent
configuration, reporting, and presentation for the OAM mechanisms
used to manage the network.
Some of the readable data nodes in this YANG module may be considered
sensitive or vulnerable in some network environments. It is thus
important to control read access (e.g., via get, get-config, or
notification) to these data nodes. These are the subtrees and data
nodes and their sensitivity/vulnerability:
/coam:cc-session-statistics-data/cl-oam:cc-ipv4-sessions-
statistics/cl-oam:cc-session-statistics/cl-oam:session-count/
/coam:cc-session-statistics-data/cl-oam:cc-ipv4-sessions-
statistics/cl-oam:cc-session-statistics/cl-oam:session-up-count/
/coam:cc-session-statistics-data/cl-oam:cc-ipv4-sessions-
statistics/cl-oam:cc-session-statistics/cl-oam: session-down-
count/
/coam:cc-session-statistics-data/cl-oam:cc-ipv4-sessions-
statistics/cl-oam:cc-session-statistics/cl-oam:session-admin-down-
count/
/coam:cc-session-statistics-data/cl-oam:cc-ipv6-sessions-
statistics/cl-oam:cc-session-statistics/cl-oam:session-count/
/coam:cc-session-statistics-data/cl-oam:cc-ipv6-sessions-
statistics/cl-oam:cc-session-statistics/cl-oam:session-up-count//
/coam:cc-session-statistics-data/cl-oam:cc-ipv6-sessions-
statistics/cl-oam:cc-session-statistics/cl-oam:session-down-count/
Kumar, et al. Expires April 27, 2018 [Page 49]
Internet-Draft Connectionless OAM YANG model October 2017
/coam:cc-session-statistics-data/cl-oam:cc-ipv6-sessions-
statistics/cl-oam:cc-session-statistics/cl-oam:session-admin-down-
count/
7. IANA Considerations
This document registers a URI in the IETF XML registry [RFC3688].
Following the format in [RFC3688] the following registration is
requested to be made:
URI: urn:ietf:params:xml:ns:yang:ietf-connectionless-oam
Registrant Contact: The IESG.
XML: N/A, the requested URI is an XML namespace.
This document registers a YANG module in the YANG Module Names
registry [RFC7950].
name: ietf-connectionless-oam
namespace: urn:ietf:params:xml:ns:yang:ietf-connectionless-oam
prefix: cl-oam
reference: RFC XXXX
8. Acknowlegements
The authors of this document would like to thank Greg Mirsky and
others for their sustainable review and comments, proposals to
improve and stabilize document.
9. References
9.1. Normative References
[RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688,
DOI 10.17487/RFC3688, January 2004,
<https://www.rfc-editor.org/info/rfc3688>.
[RFC4443] Conta, A., Deering, S., and M. Gupta, Ed., "Internet
Control Message Protocol (ICMPv6) for the Internet
Protocol Version 6 (IPv6) Specification", STD 89,
RFC 4443, DOI 10.17487/RFC4443, March 2006,
<https://www.rfc-editor.org/info/rfc4443>.
Kumar, et al. Expires April 27, 2018 [Page 50]
Internet-Draft Connectionless OAM YANG model October 2017
[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>.
[RFC5905] Mills, D., Martin, J., Ed., Burbank, J., and W. Kasch,
"Network Time Protocol Version 4: Protocol and Algorithms
Specification", RFC 5905, DOI 10.17487/RFC5905, June 2010,
<https://www.rfc-editor.org/info/rfc5905>.
[RFC6021] Schoenwaelder, J., Ed., "Common YANG Data Types",
RFC 6021, DOI 10.17487/RFC6021, October 2010,
<https://www.rfc-editor.org/info/rfc6021>.
[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",
RFC 6991, DOI 10.17487/RFC6991, July 2013,
<https://www.rfc-editor.org/info/rfc6991>.
[RFC7223] Bjorklund, M., "A YANG Data Model for Interface
Management", RFC 7223, DOI 10.17487/RFC7223, May 2014,
<https://www.rfc-editor.org/info/rfc7223>.
[RFC792] Postel, J., "Internet Control Message Protocol", RFC 792,
September 1981.
[RFC7950] Bjorklund, M., Ed., "The YANG 1.1 Data Modeling Language",
RFC 7950, DOI 10.17487/RFC7950, August 2016,
<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>.
Kumar, et al. Expires April 27, 2018 [Page 51]
Internet-Draft Connectionless OAM YANG model October 2017
9.2. Informative References
[G.800] "Unified functional architecture of transport networks",
ITU-T Recommendation G.800, 2016.
[G.8013] "OAM functions and mechanisms for Ethernet based
networks", ITU-T Recommendation G.8013/Y.1731, 2013.
[I-D.ietf-bfd-yang]
Rahman, R., Zheng, L., Jethanandani, M., Networks, J., and
G. Mirsky, "YANG Data Model for Bidirectional Forwarding
Detection (BFD)", draft-ietf-bfd-yang-06 (work in
progress), June 2017.
[I-D.ietf-i2rs-yang-network-topo]
Clemm, A., Medved, J., Varga, R., Bahadur, N.,
Ananthakrishnan, H., and X. Liu, "A Data Model for Network
Topologies", draft-ietf-i2rs-yang-network-topo-17 (work in
progress), October 2017.
[I-D.ietf-lime-yang-connection-oriented-oam-model]
Kumar, D., Wu, Q., and Z. Wang, "Generic YANG Data Model
for Connection Oriented Operations, Administration, and
Maintenance(OAM) protocols", draft-ietf-lime-yang-
connection-oriented-oam-model-00 (work in progress), June
2017.
[I-D.ietf-lime-yang-connectionless-oam-methods]
Kumar, D., Wang, Z., Wu, Q., Rahman, R., and S. Raghavan,
"Retrieval Methods YANG Data Model for Connectionless
Operations, Administration, and Maintenance(OAM)
protocols", draft-ietf-lime-yang-connectionless-oam-
methods-10 (work in progress), October 2017.
[I-D.ietf-netmod-schema-mount]
Bjorklund, M. and L. Lhotka, "YANG Schema Mount", draft-
ietf-netmod-schema-mount-08 (work in progress), October
2017.
[I-D.ietf-rtgwg-ni-model]
Berger, L., Hopps, C., Lindem, A., Bogdanovic, D., and X.
Liu, "YANG Network Instances", draft-ietf-rtgwg-ni-
model-04 (work in progress), September 2017.
[I-D.ietf-rtgwg-routing-types]
Liu, X., Qu, Y., Lindem, A., Hopps, C., and L. Berger,
"Routing Area Common YANG Data Types", draft-ietf-rtgwg-
routing-types-17 (work in progress), October 2017.
Kumar, et al. Expires April 27, 2018 [Page 52]
Internet-Draft Connectionless OAM YANG model October 2017
[I-D.ietf-spring-sr-yang]
Litkowski, S., Qu, Y., Sarkar, P., and J. Tantsura, "YANG
Data Model for Segment Routing", draft-ietf-spring-sr-
yang-07 (work in progress), July 2017.
[I-D.zheng-mpls-lsp-ping-yang-cfg]
Zheng, L., Aldrin, S., Zheng, G., Mirsky, G., and R.
Rahman, "Yang Data Model for LSP-PING", draft-zheng-mpls-
lsp-ping-yang-cfg-05 (work in progress), June 2017.
[IEEE.1588]
"IEEE Standard for a Precision Clock Synchronization
Protocol for Networked Measurement and Control Systems",
IEEE IEEE Std 1588-2008, 2008.
[RFC5462] Andersson, L. and R. Asati, "Multiprotocol Label Switching
(MPLS) Label Stack Entry: "EXP" Field Renamed to "Traffic
Class" Field", RFC 5462, DOI 10.17487/RFC5462, February
2009, <https://www.rfc-editor.org/info/rfc5462>.
[RFC6136] Sajassi, A., Ed. and D. Mohan, Ed., "Layer 2 Virtual
Private Network (L2VPN) Operations, Administration, and
Maintenance (OAM) Requirements and Framework", RFC 6136,
DOI 10.17487/RFC6136, March 2011,
<https://www.rfc-editor.org/info/rfc6136>.
[RFC7276] Mizrahi, T., Sprecher, N., Bellagamba, E., and Y.
Weingarten, "An Overview of Operations, Administration,
and Maintenance (OAM) Tools", RFC 7276,
DOI 10.17487/RFC7276, June 2014,
<https://www.rfc-editor.org/info/rfc7276>.
Authors' Addresses
Deepak Kumar
CISCO Systems
510 McCarthy Blvd
Milpitas, CA 95035
USA
Email: dekumar@cisco.com
Kumar, et al. Expires April 27, 2018 [Page 53]
Internet-Draft Connectionless OAM YANG model October 2017
Michael Wang
Huawei Technologies,Co.,Ltd
101 Software Avenue, Yuhua District
Nanjing 210012
China
Email: wangzitao@huawei.com
Qin Wu
Huawei
101 Software Avenue, Yuhua District
Nanjing, Jiangsu 210012
China
Email: bill.wu@huawei.com
Reshad Rahman
Cisco Systems
2000 Innovation Drive
Kanata, Ontario K2K 3E8
Canada
Email: rrahman@cisco.com
Srihari Raghavan
Cisco Systems
Tril Infopark Sez, Ramanujan IT City
Neville Block, 2nd floor, Old Mahabalipuram Road
Chennai, Tamil Nadu 600113
India
Email: srihari@cisco.com
Kumar, et al. Expires April 27, 2018 [Page 54]
amp; Network Autonomics July 2018