Internet Engineering Task Force (IETF) J. Schoenwaelder
Request for Comments: 8194 Jacobs University Bremen
Category: Standards Track V. Bajpai
ISSN: 2070-1721 Technical University of Munich
August 2017
Internet Engineering Task Force (IETF) J. Schoenwaelder
Request for Comments: 8194 Jacobs University Bremen
Category: Standards Track V. Bajpai
ISSN: 2070-1721 Technical University of Munich
August 2017
A YANG Data Model for LMAP Measurement Agents
LMAP测量代理的YANG数据模型
Abstract
摘要
This document defines a data model for Large-Scale Measurement Platforms (LMAPs). The data model is defined using the YANG data modeling language.
本文件定义了大型测量平台（LMAP）的数据模型。使用YANG数据建模语言定义数据模型。
Status of This Memo
关于下段备忘
This is an Internet Standards Track document.
这是一份互联网标准跟踪文件。
This document is a product of the Internet Engineering Task Force (IETF). It represents the consensus of the IETF community. It has received public review and has been approved for publication by the Internet Engineering Steering Group (IESG). Further information on Internet Standards is available in Section 2 of RFC 7841.
本文件是互联网工程任务组（IETF）的产品。它代表了IETF社区的共识。它已经接受了公众审查，并已被互联网工程指导小组（IESG）批准出版。有关互联网标准的更多信息，请参见RFC 7841第2节。
Information about the current status of this document, any errata, and how to provide feedback on it may be obtained at http://www.rfc-editor.org/info/rfc8194.
有关本文件当前状态、任何勘误表以及如何提供反馈的信息，请访问http://www.rfc-editor.org/info/rfc8194.
Copyright Notice
版权公告
Copyright (c) 2017 IETF Trust and the persons identified as the document authors. All rights reserved.
版权所有（c）2017 IETF信托基金和确定为文件作者的人员。版权所有。
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 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.
本文件受BCP 78和IETF信托有关IETF文件的法律规定的约束(http://trustee.ietf.org/license-info)自本文件出版之日起生效。请仔细阅读这些文件，因为它们描述了您对本文件的权利和限制。从本文件中提取的代码组件必须包括信托法律条款第4.e节中所述的简化BSD许可证文本，并提供简化BSD许可证中所述的无担保。
Table of Contents
目录
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
1.1. Terminology . . . . . . . . . . . . . . . . . . . . . . . 2
1.2. Tree Diagrams . . . . . . . . . . . . . . . . . . . . . . 2
2. Data Model Overview . . . . . . . . . . . . . . . . . . . . . 3
3. Relationship to the Information Model . . . . . . . . . . . . 9
4. YANG Modules . . . . . . . . . . . . . . . . . . . . . . . . 10
4.1. LMAP Common YANG Module . . . . . . . . . . . . . . . . . 10
4.2. LMAP Control YANG Module . . . . . . . . . . . . . . . . 18
4.3. LMAP Report YANG Module . . . . . . . . . . . . . . . . . 40
5. Security Considerations . . . . . . . . . . . . . . . . . . . 45
6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 47
7. References . . . . . . . . . . . . . . . . . . . . . . . . . 48
7.1. Normative References . . . . . . . . . . . . . . . . . . 48
7.2. Informative References . . . . . . . . . . . . . . . . . 49
Appendix A. Example Parameter Extension Module . . . . . . . . . 51
Appendix B. Example Configuration . . . . . . . . . . . . . . . 53
Appendix C. Example Report . . . . . . . . . . . . . . . . . . . 56
Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . . 59
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 59
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
1.1. Terminology . . . . . . . . . . . . . . . . . . . . . . . 2
1.2. Tree Diagrams . . . . . . . . . . . . . . . . . . . . . . 2
2. Data Model Overview . . . . . . . . . . . . . . . . . . . . . 3
3. Relationship to the Information Model . . . . . . . . . . . . 9
4. YANG Modules . . . . . . . . . . . . . . . . . . . . . . . . 10
4.1. LMAP Common YANG Module . . . . . . . . . . . . . . . . . 10
4.2. LMAP Control YANG Module . . . . . . . . . . . . . . . . 18
4.3. LMAP Report YANG Module . . . . . . . . . . . . . . . . . 40
5. Security Considerations . . . . . . . . . . . . . . . . . . . 45
6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 47
7. References . . . . . . . . . . . . . . . . . . . . . . . . . 48
7.1. Normative References . . . . . . . . . . . . . . . . . . 48
7.2. Informative References . . . . . . . . . . . . . . . . . 49
Appendix A. Example Parameter Extension Module . . . . . . . . . 51
Appendix B. Example Configuration . . . . . . . . . . . . . . . 53
Appendix C. Example Report . . . . . . . . . . . . . . . . . . . 56
Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . . 59
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 59
This document defines a data model for Large-Scale Measurement Platforms (LMAPs) [RFC7594]. The data model is defined using the YANG [RFC7950] data modeling language. It is based on the LMAP Information Model [RFC8193].
本文件定义了大型测量平台（LMAP）的数据模型[RFC7594]。数据模型是使用YANG[RFC7950]数据建模语言定义的。它基于LMAP信息模型[RFC8193]。
This document uses the LMAP terminology defined in [RFC7594].
本文件使用[RFC7594]中定义的LMAP术语。
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in BCP 14 [RFC2119] [RFC8174] when, and only when, they appear in all capitals, as shown here.
本文件中的关键词“必须”、“不得”、“必需”、“应”、“不应”、“建议”、“不建议”、“可”和“可选”在所有大写字母出现时（如图所示）应按照BCP 14[RFC2119][RFC8174]所述进行解释。
A simplified graphical representation of the data model is used in this document. The meaning of the symbols in these diagrams is as follows:
本文件中使用了数据模型的简化图形表示。这些图表中符号的含义如下：
o Brackets "[" and "]" enclose list keys.
o 括号“[”和“]”包含列表键。
o Abbreviations before data node names: "rw" means configuration (read-write), "ro" means state data (read-only), and "w" means RPC input data (write-only).
o 数据节点名称前的缩写：“rw”表示配置（读写），“ro”表示状态数据（只读），“w”表示RPC输入数据（只读）。
o Symbols after data node names: "?" means an optional node, "!" means a presence container, and "*" denotes a list and leaf-list.
o 数据节点名称后的符号：“？”表示可选节点，“！”表示状态容器，“*”表示列表和叶列表。
o Parentheses enclose choice and case nodes, and case nodes are also marked with a colon (":").
o 括号括住选项和事例节点，事例节点也用冒号（“：”）标记。
o Ellipsis ("...") stands for contents of subtrees that are not shown.
o 省略号（“…”）表示未显示的子树的内容。
The LMAP framework has three basic elements: Measurement Agents (MAs), Controllers, and Collectors. Measurement Agents initiate the actual measurements, which are called Measurement Tasks in the LMAP terminology. The Controller instructs one or more MAs and communicates the set of Measurement Tasks an MA should perform and when. The Collector accepts Reports from the MAs with the Results from their Measurement Tasks.
LMAP框架有三个基本元素：测量代理（MAs）、控制器和收集器。测量代理启动实际测量，在LMAP术语中称为测量任务。控制器指示一个或多个MA，并告知MA应执行的一组测量任务和时间。收集器接受来自MAs的报告及其测量任务的结果。
The YANG data model for LMAP has been split into three modules:
LMAP的YANG数据模型分为三个模块：
1. The module ietf-lmap-common.yang provides common definitions such as LMAP-specific data types.
1. ietf-lmap-common.yang模块提供通用定义，如lmap特定的数据类型。
2. The module ietf-lmap-control.yang defines the data structures exchanged between a Controller and Measurement Agents.
2. ietf-lmap-control.yang模块定义了控制器和测量代理之间交换的数据结构。
3. The module ietf-lmap-report.yang defines the data structures exchanged between Measurement Agents and Collectors.
3. ietf-lmap-report.yang模块定义了测量代理和采集器之间交换的数据结构。
As shown in Figure 1, a Controller, implementing ietf-lmap-common.yang and ietf-lmap-control.yang as a client, will instruct Measurement Agents, which implement ietf-lmap-common.yang and ietf-lmap-control.yang as servers. A Measurement Agent, implementing ietf-lmap-common.yang and ietf-lmap-report.yang, will send results to a Collector, which implements ietf-lmap-common.yang and ietf-lmap-report.yang as a server.
如图1所示，作为客户端实现ietf-lmap-common.yang和ietf-lmap-control.yang的控制器将指示作为服务器实现ietf-lmap-common.yang和ietf-lmap-control.yang的测量代理。实现ietf-lmap-common.yang和ietf-lmap-report.yang的测量代理将结果发送给收集器，收集器将ietf-lmap-common.yang和ietf-lmap-report.yang作为服务器实现。
+------------------------+
| LMAP Controller |
| |
| Client: |
| ietf-lmap-common.yang |
| ietf-lmap-control.yang |
+------------------------+
+------------------------+ |
| LMAP Measurement Agent | |
| | <- request |
| Server: |<---------------------'
| ietf-lmap-common.yang | response ->
| ietf-lmap-control.yang |
| |
| | request ->
| Client: |----------------------.
| ietf-lmap-common.yang | <- response |
| ietf-lmap-report.yang | |
+------------------------+ v
+------------------------+
| LMAP Collector |
| |
| Server: |
| ietf-lmap-common.yang |
| ietf-lmap-report.yang |
+------------------------+
+------------------------+
| LMAP Controller |
| |
| Client: |
| ietf-lmap-common.yang |
| ietf-lmap-control.yang |
+------------------------+
+------------------------+ |
| LMAP Measurement Agent | |
| | <- request |
| Server: |<---------------------'
| ietf-lmap-common.yang | response ->
| ietf-lmap-control.yang |
| |
| | request ->
| Client: |----------------------.
| ietf-lmap-common.yang | <- response |
| ietf-lmap-report.yang | |
+------------------------+ v
+------------------------+
| LMAP Collector |
| |
| Server: |
| ietf-lmap-common.yang |
| ietf-lmap-report.yang |
+------------------------+
Figure 1: The LMAP Controller, Measurement Agent, and Collector and the YANG Modules They Implement as Client or Server
图1:LMAP控制器、测量代理和收集器以及它们作为客户端或服务器实现的模块
The tree diagram below shows the structure of the control data model.
下面的树形图显示了控制数据模型的结构。
module: ietf-lmap-control
+--rw lmap
+--ro capabilities
| +--ro version string
| +--ro tag* lmap:tag
| +--ro tasks
| +--ro task* [name]
| +--ro name lmap:identifier
| +--ro function* [uri]
| | +--ro uri inet:uri
| | +--ro role* string
| +--ro version? string
| +--ro program? string
+--rw agent
| +--rw agent-id? yang:uuid
| +--rw group-id? string
| +--rw measurement-point? string
| +--rw report-agent-id? boolean
| +--rw report-group-id? boolean
| +--rw report-measurement-point? boolean
| +--rw controller-timeout? uint32
| +--ro last-started yang:date-and-time
+--rw tasks
| +--rw task* [name]
| +--rw name lmap:identifier
| +--rw function* [uri]
| | +--rw uri inet:uri
| | +--rw role* string
| +--rw program? string
| +--rw option* [id]
| | +--rw id lmap:identifier
| | +--rw name? string
| | +--rw value? string
| +--rw tag* lmap:identifier
module: ietf-lmap-control
+--rw lmap
+--ro capabilities
| +--ro version string
| +--ro tag* lmap:tag
| +--ro tasks
| +--ro task* [name]
| +--ro name lmap:identifier
| +--ro function* [uri]
| | +--ro uri inet:uri
| | +--ro role* string
| +--ro version? string
| +--ro program? string
+--rw agent
| +--rw agent-id? yang:uuid
| +--rw group-id? string
| +--rw measurement-point? string
| +--rw report-agent-id? boolean
| +--rw report-group-id? boolean
| +--rw report-measurement-point? boolean
| +--rw controller-timeout? uint32
| +--ro last-started yang:date-and-time
+--rw tasks
| +--rw task* [name]
| +--rw name lmap:identifier
| +--rw function* [uri]
| | +--rw uri inet:uri
| | +--rw role* string
| +--rw program? string
| +--rw option* [id]
| | +--rw id lmap:identifier
| | +--rw name? string
| | +--rw value? string
| +--rw tag* lmap:identifier
+--rw schedules
| +--rw schedule* [name]
| +--rw name lmap:identifier
| +--rw start event-ref
| +--rw (stop)?
| | +--:(end)
| | | +--rw end? event-ref
| | +--:(duration)
| | +--rw duration? uint32
| +--rw execution-mode? enumeration
| +--rw tag* lmap:tag
| +--rw suppression-tag* lmap:tag
| +--ro state enumeration
| +--ro storage yang:gauge64
| +--ro invocations yang:counter32
| +--ro suppressions yang:counter32
| +--ro overlaps yang:counter32
| +--ro failures yang:counter32
| +--ro last-invocation? yang:date-and-time
| +--rw action* [name]
| +--rw name lmap:identifier
| +--rw task task-ref
| +--rw parameters
| | +--rw (extension)?
| +--rw option* [id]
| | +--rw id lmap:identifier
| | +--rw name? string
| | +--rw value? string
| +--rw destination* schedule-ref
| +--rw tag* lmap:tag
| +--rw suppression-tag* lmap:tag
| +--ro state enumeration
| +--ro storage yang:gauge64
| +--ro invocations yang:counter32
| +--ro suppressions yang:counter32
| +--ro overlaps yang:counter32
| +--ro failures yang:counter32
| +--ro last-invocation yang:date-and-time
| +--ro last-completion yang:date-and-time
| +--ro last-status lmap:status-code
| +--ro last-message string
| +--ro last-failed-completion yang:date-and-time
| +--ro last-failed-status lmap:status-code
| +--ro last-failed-message string
+--rw schedules
| +--rw schedule* [name]
| +--rw name lmap:identifier
| +--rw start event-ref
| +--rw (stop)?
| | +--:(end)
| | | +--rw end? event-ref
| | +--:(duration)
| | +--rw duration? uint32
| +--rw execution-mode? enumeration
| +--rw tag* lmap:tag
| +--rw suppression-tag* lmap:tag
| +--ro state enumeration
| +--ro storage yang:gauge64
| +--ro invocations yang:counter32
| +--ro suppressions yang:counter32
| +--ro overlaps yang:counter32
| +--ro failures yang:counter32
| +--ro last-invocation? yang:date-and-time
| +--rw action* [name]
| +--rw name lmap:identifier
| +--rw task task-ref
| +--rw parameters
| | +--rw (extension)?
| +--rw option* [id]
| | +--rw id lmap:identifier
| | +--rw name? string
| | +--rw value? string
| +--rw destination* schedule-ref
| +--rw tag* lmap:tag
| +--rw suppression-tag* lmap:tag
| +--ro state enumeration
| +--ro storage yang:gauge64
| +--ro invocations yang:counter32
| +--ro suppressions yang:counter32
| +--ro overlaps yang:counter32
| +--ro failures yang:counter32
| +--ro last-invocation yang:date-and-time
| +--ro last-completion yang:date-and-time
| +--ro last-status lmap:status-code
| +--ro last-message string
| +--ro last-failed-completion yang:date-and-time
| +--ro last-failed-status lmap:status-code
| +--ro last-failed-message string
+--rw suppressions
| +--rw suppression* [name]
| +--rw name lmap:identifier
| +--rw start? event-ref
| +--rw end? event-ref
| +--rw match* lmap:glob-pattern
| +--rw stop-running? boolean
| +--ro state enumeration
+--rw events
+--rw event* [name]
+--rw name lmap:identifier
+--rw random-spread? uint32
+--rw cycle-interval? uint32
+--rw (event-type)?
+--:(periodic)
| +--rw periodic
| +--rw interval uint32
| +--rw start? yang:date-and-time
| +--rw end? yang:date-and-time
+--:(calendar)
| +--rw calendar
| +--rw month* lmap:month-or-all
| +--rw day-of-month* lmap:day-of-months-or-all
| +--rw day-of-week* lmap:weekday-or-all
| +--rw hour* lmap:hour-or-all
| +--rw minute* lmap:minute-or-all
| +--rw second* lmap:second-or-all
| +--rw timezone-offset? lmap:timezone-offset
| +--rw start? yang:date-and-time
| +--rw end? yang:date-and-time
+--:(one-off)
| +--rw one-off
| +--rw time yang:date-and-time
+--:(immediate)
| +--rw immediate empty
+--:(startup)
| +--rw startup empty
+--:(controller-lost)
| +--rw controller-lost empty
+--:(controller-connected)
+--rw controller-connected empty
+--rw suppressions
| +--rw suppression* [name]
| +--rw name lmap:identifier
| +--rw start? event-ref
| +--rw end? event-ref
| +--rw match* lmap:glob-pattern
| +--rw stop-running? boolean
| +--ro state enumeration
+--rw events
+--rw event* [name]
+--rw name lmap:identifier
+--rw random-spread? uint32
+--rw cycle-interval? uint32
+--rw (event-type)?
+--:(periodic)
| +--rw periodic
| +--rw interval uint32
| +--rw start? yang:date-and-time
| +--rw end? yang:date-and-time
+--:(calendar)
| +--rw calendar
| +--rw month* lmap:month-or-all
| +--rw day-of-month* lmap:day-of-months-or-all
| +--rw day-of-week* lmap:weekday-or-all
| +--rw hour* lmap:hour-or-all
| +--rw minute* lmap:minute-or-all
| +--rw second* lmap:second-or-all
| +--rw timezone-offset? lmap:timezone-offset
| +--rw start? yang:date-and-time
| +--rw end? yang:date-and-time
+--:(one-off)
| +--rw one-off
| +--rw time yang:date-and-time
+--:(immediate)
| +--rw immediate empty
+--:(startup)
| +--rw startup empty
+--:(controller-lost)
| +--rw controller-lost empty
+--:(controller-connected)
+--rw controller-connected empty
The tree diagram below shows the structure of the reporting data model.
下面的树形图显示了报告数据模型的结构。
module: ietf-lmap-report
模块：ietf lmap报告
rpcs:
+---x report
+---w input
+---w date yang:date-and-time
+---w agent-id? yang:uuid
+---w group-id? string
+---w measurement-point? string
+---w result*
+---w schedule? lmap:identifier
+---w action? lmap:identifier
+---w task? lmap:identifier
+---w parameters
| +---w (extension)?
+---w option* [id]
| +---w id lmap:identifier
| +---w name? string
| +---w value? string
+---w tag* lmap:tag
+---w event? yang:date-and-time
+---w start yang:date-and-time
+---w end? yang:date-and-time
+---w cycle-number? lmap:cycle-number
+---w status lmap:status-code
+---w conflict*
| +---w schedule-name? lmap:identifier
| +---w action-name? lmap:identifier
| +---w task-name? lmap:identifier
+---w table*
+---w function* [uri]
| +---w uri inet:uri
| +---w role* string
+---w column* string
+---w row*
+---w value* string
rpcs:
+---x report
+---w input
+---w date yang:date-and-time
+---w agent-id? yang:uuid
+---w group-id? string
+---w measurement-point? string
+---w result*
+---w schedule? lmap:identifier
+---w action? lmap:identifier
+---w task? lmap:identifier
+---w parameters
| +---w (extension)?
+---w option* [id]
| +---w id lmap:identifier
| +---w name? string
| +---w value? string
+---w tag* lmap:tag
+---w event? yang:date-and-time
+---w start yang:date-and-time
+---w end? yang:date-and-time
+---w cycle-number? lmap:cycle-number
+---w status lmap:status-code
+---w conflict*
| +---w schedule-name? lmap:identifier
| +---w action-name? lmap:identifier
| +---w task-name? lmap:identifier
+---w table*
+---w function* [uri]
| +---w uri inet:uri
| +---w role* string
+---w column* string
+---w row*
+---w value* string
The LMAP Information Model [RFC8193] is divided into six aspects. They are mapped into the YANG data model as explained below:
LMAP信息模型[RFC8193]分为六个方面。它们被映射到YANG数据模型中，如下所述：
o Preconfiguration Information: This is not modeled explicitly since bootstrapping information is outside the scope of this data model. Implementations may use some of the Configuration Information also for bootstrapping purposes.
o 预配置信息：由于引导信息不在该数据模型的范围内，因此未对其进行显式建模。实现可能会将一些配置信息用于引导目的。
o Configuration Information: This is modeled in the /lmap/agent subtree, the /lmap/schedules subtree, and the /lmap/tasks subtree described below. Some items have been left out because they are expected to be dealt with by the underlying protocol.
o 配置信息：这在下面描述的/lmap/agent子树、/lmap/schedules子树和/lmap/tasks子树中建模。有些项目被遗漏了，因为它们预期将由基础协议处理。
o Instruction Information: This is modeled in the /lmap/suppressions subtree, the /lmap/schedules subtree, and the /lmap/tasks subtree described below.
o 指令信息：这在下面描述的/lmap/suppressions子树、/lmap/schedules子树和/lmap/tasks子树中建模。
o Logging Information: Some of the Logging Information, in particular 'success/failure/warning messages in response to information updates from the Controller', will be handled by the protocol used to manipulate the LMAP-specific configuration. The LMAP data model defined in this document assumes that runtime Logging Information will be communicated using protocols that do not require a formal data model, e.g., the syslog protocol defined in [RFC5424].
o 日志信息：一些日志信息，特别是“响应控制器信息更新的成功/失败/警告消息”，将由用于操纵LMAP特定配置的协议处理。本文档中定义的LMAP数据模型假设运行时日志信息将使用不需要正式数据模型的协议进行通信，例如[RFC5424]中定义的syslog协议。
o Capability and Status Information: Some of the Capability and Status Information is modeled in the /lmap/capability subtree. The list of supported Tasks is modeled in the /lmap/capabilities/ task list. Status Information about Schedules and Actions is included in the /lmap/schedules subtree. Information about network interfaces can be obtained from the ietf-interfaces YANG data model [RFC7223]. Information about the hardware and the firmware can be obtained from the ietf-system YANG data model [RFC7317]. A device identifier can be obtained from the ietf-hardware YANG data model [YANG-HARDWARE].
o 能力和状态信息：一些能力和状态信息在/lmap/Capability子树中建模。支持的任务列表在/lmap/capabilities/task列表中建模。有关计划和操作的状态信息包含在/lmap/Schedules子树中。有关网络接口的信息可从ietf接口数据模型[RFC7223]获得。有关硬件和固件的信息可从ietf系统数据模型[RFC7317]获得。可以从ietf硬件数据模型[YANG-hardware]中获得设备标识符。
o Reporting Information: This is modeled by the report data model to be implemented by the Collector. Measurement Agents send results to the Collector by invoking an RPC on the Collector.
o 报告信息：由收集器实现的报告数据模型对其进行建模。度量代理通过调用收集器上的RPC将结果发送到收集器。
These six Information Model aspects use a collection of common information objects. These common information objects are represented in the YANG data model as follows:
这六个信息模型方面使用公共信息对象的集合。这些公共信息对象在YANG数据模型中表示如下：
o Schedules: Schedules are modeled in the /lmap/schedules subtree.
o 计划：计划在/lmap/Schedules子树中建模。
o Channels: Channels are not modeled since the NETCONF server configuration data model [NETCONF-CLIENT-SERVER] already provides a mechanism to configure NETCONF server Channels.
o 通道：由于NETCONF服务器配置数据模型[NETCONF-CLIENT-server]已经提供了配置NETCONF服务器通道的机制，因此未对通道进行建模。
o Task Configurations: Configured Tasks are modeled in the /lmap/ tasks subtree.
o 任务配置：配置的任务在/lmap/Tasks子树中建模。
o Event Information: Event definitions are modeled in the /lmap/ events subtree.
o 事件信息：事件定义在/lmap/events子树中建模。
This module imports definitions from [RFC6536], and it references [ISO-8601].
此模块从[RFC6536]导入定义，并引用[ISO-8601]。
<CODE BEGINS> file "ietf-lmap-common@2017-08-08.yang"
module ietf-lmap-common {
<CODE BEGINS> file "ietf-lmap-common@2017-08-08.yang"
module ietf-lmap-common {
yang-version 1.1;
namespace "urn:ietf:params:xml:ns:yang:ietf-lmap-common";
prefix "lmap";
yang-version 1.1;
namespace "urn:ietf:params:xml:ns:yang:ietf-lmap-common";
prefix "lmap";
import ietf-inet-types {
prefix inet;
}
import ietf-inet-types {
prefix inet;
}
organization "IETF Large-Scale Measurement of Broadband Performance Working Group";
组织“IETF宽带性能大规模测量工作组”；
contact
"WG Web: <https://datatracker.ietf.org/wg/lmap>
WG List: <mailto:lmap@ietf.org>
contact
"WG Web: <https://datatracker.ietf.org/wg/lmap>
WG List: <mailto:lmap@ietf.org>
Editor: Juergen Schoenwaelder
<j.schoenwaelder@jacobs-university.de>
Editor: Juergen Schoenwaelder
<j.schoenwaelder@jacobs-university.de>
Editor: Vaibhav Bajpai
<bajpaiv@in.tum.de>";
Editor: Vaibhav Bajpai
<bajpaiv@in.tum.de>";
description "This module provides common definitions used by the data models written for Large-Scale Measurement Platforms (LMAPs). This module defines typedefs and groupings but no schema tree elements.";
description“此模块提供为大规模测量平台（LMAP）编写的数据模型使用的通用定义。此模块定义TypeDef和分组，但不定义架构树元素。”；
revision "2017-08-08" {
description
"Initial version";
reference
"RFC 8194: A YANG Data Model for LMAP Measurement Agents";
}
revision "2017-08-08" {
description
"Initial version";
reference
"RFC 8194: A YANG Data Model for LMAP Measurement Agents";
}
/*
* Typedefs
*/
/*
* Typedefs
*/
typedef identifier {
type string {
length "1..max";
}
description
"A string value used to name something.";
}
typedef identifier {
type string {
length "1..max";
}
description
"A string value used to name something.";
}
typedef tag {
type string {
length "1..max";
}
description
"A tag consists of at least one character.";
}
typedef tag {
type string {
length "1..max";
}
description
"A tag consists of at least one character.";
}
typedef glob-pattern {
type string {
length "1..max";
}
description
'A glob style pattern (following POSIX.2 fnmatch() without
special treatment of file paths):
typedef glob-pattern {
type string {
length "1..max";
}
description
'A glob style pattern (following POSIX.2 fnmatch() without
special treatment of file paths):
* matches a sequence of characters ? matches a single character [seq] matches any character in seq [!seq] matches any character not in seq
* 匹配字符序列？匹配单个字符[seq]匹配seq中的任何字符[！seq]匹配不在seq中的任何字符
A backslash followed by a character matches the following character. In particular:
后跟字符的反斜杠与以下字符匹配。特别地：
\* matches * \? matches ? \\ matches \
\*匹配*\？匹配？\\火柴\
A sequence seq may be a sequence of characters (e.g., [abc]
or a range of characters (e.g., [a-c]).';
}
A sequence seq may be a sequence of characters (e.g., [abc]
or a range of characters (e.g., [a-c]).';
}
typedef wildcard {
type string {
pattern '\*';
}
description
"A wildcard for calendar scheduling entries.";
}
typedef wildcard {
type string {
pattern '\*';
}
description
"A wildcard for calendar scheduling entries.";
}
typedef cycle-number {
type string {
pattern '[0-9]{8}\.[0-9]{6}';
}
description
"A cycle number represented in the format YYYYMMDD.HHMMSS
where YYYY represents the year, MM the month (1..12), DD
the day of the months (01..31), HH the hour (00..23), MM
the minute (00..59), and SS the second (00..59). The cycle
number is using Coordinated Universal Time (UTC).";
}
typedef cycle-number {
type string {
pattern '[0-9]{8}\.[0-9]{6}';
}
description
"A cycle number represented in the format YYYYMMDD.HHMMSS
where YYYY represents the year, MM the month (1..12), DD
the day of the months (01..31), HH the hour (00..23), MM
the minute (00..59), and SS the second (00..59). The cycle
number is using Coordinated Universal Time (UTC).";
}
typedef month {
type enumeration {
enum january {
value 1;
description
"January of the Gregorian calendar.";
}
enum february {
value 2;
description
"February of the Gregorian calendar.";
}
enum march {
value 3;
description
"March of the Gregorian calendar.";
}
enum april {
value 4;
description
"April of the Gregorian calendar.";
}
typedef month {
type enumeration {
enum january {
value 1;
description
"January of the Gregorian calendar.";
}
enum february {
value 2;
description
"February of the Gregorian calendar.";
}
enum march {
value 3;
description
"March of the Gregorian calendar.";
}
enum april {
value 4;
description
"April of the Gregorian calendar.";
}
enum may {
value 5;
description
"May of the Gregorian calendar.";
}
enum june {
value 6;
description
"June of the Gregorian calendar.";
}
enum july {
value 7;
description
"July of the Gregorian calendar.";
}
enum august {
value 8;
description
"August of the Gregorian calendar.";
}
enum september {
value 9;
description
"September of the Gregorian calendar.";
}
enum october {
value 10;
description
"October of the Gregorian calendar.";
}
enum november {
value 11;
description
"November of the Gregorian calendar.";
}
enum december {
value 12;
description
"December of the Gregorian calendar.";
}
}
description
"A type modeling the month in the Gregorian calendar.";
}
enum may {
value 5;
description
"May of the Gregorian calendar.";
}
enum june {
value 6;
description
"June of the Gregorian calendar.";
}
enum july {
value 7;
description
"July of the Gregorian calendar.";
}
enum august {
value 8;
description
"August of the Gregorian calendar.";
}
enum september {
value 9;
description
"September of the Gregorian calendar.";
}
enum october {
value 10;
description
"October of the Gregorian calendar.";
}
enum november {
value 11;
description
"November of the Gregorian calendar.";
}
enum december {
value 12;
description
"December of the Gregorian calendar.";
}
}
description
"A type modeling the month in the Gregorian calendar.";
}
typedef month-or-all {
type union {
type month;
type wildcard;
}
description
"A month or a wildcard indicating all twelve months.";
}
typedef month-or-all {
type union {
type month;
type wildcard;
}
description
"A month or a wildcard indicating all twelve months.";
}
typedef day-of-month {
type uint8 { range "1..31"; }
description
"A day of a month of the Gregorian calendar.";
}
typedef day-of-month {
type uint8 { range "1..31"; }
description
"A day of a month of the Gregorian calendar.";
}
typedef day-of-months-or-all {
type union {
type day-of-month;
type wildcard;
}
description
"A day of a month or a wildcard indicating all days
of a month.";
}
typedef day-of-months-or-all {
type union {
type day-of-month;
type wildcard;
}
description
"A day of a month or a wildcard indicating all days
of a month.";
}
typedef weekday {
type enumeration {
enum monday {
value 1;
description
"Monday of the Gregorian calendar.";
}
enum tuesday {
value 2;
description
"Tuesday of the Gregorian calendar.";
}
enum wednesday {
value 3;
description
"Wednesday of the Gregorian calendar.";
}
enum thursday {
value 4;
description
"Thursday of the Gregorian calendar.";
}
typedef weekday {
type enumeration {
enum monday {
value 1;
description
"Monday of the Gregorian calendar.";
}
enum tuesday {
value 2;
description
"Tuesday of the Gregorian calendar.";
}
enum wednesday {
value 3;
description
"Wednesday of the Gregorian calendar.";
}
enum thursday {
value 4;
description
"Thursday of the Gregorian calendar.";
}
enum friday {
value 5;
description
"Friday of the Gregorian calendar.";
}
enum saturday {
value 6;
description
"Saturday of the Gregorian calendar.";
}
enum sunday {
value 7;
description
"Sunday of the Gregorian calendar.";
}
}
description
"A type modeling the weekdays in the Gregorian calendar.
The numbering follows the ISO 8601 scheme.";
reference
"ISO 8601:2004: Data elements and interchange formats --
Information interchange -- Representation
of dates and times";
}
enum friday {
value 5;
description
"Friday of the Gregorian calendar.";
}
enum saturday {
value 6;
description
"Saturday of the Gregorian calendar.";
}
enum sunday {
value 7;
description
"Sunday of the Gregorian calendar.";
}
}
description
"A type modeling the weekdays in the Gregorian calendar.
The numbering follows the ISO 8601 scheme.";
reference
"ISO 8601:2004: Data elements and interchange formats --
Information interchange -- Representation
of dates and times";
}
typedef weekday-or-all {
type union {
type weekday;
type wildcard;
}
description
"A weekday or a wildcard indicating all seven weekdays.";
}
typedef weekday-or-all {
type union {
type weekday;
type wildcard;
}
description
"A weekday or a wildcard indicating all seven weekdays.";
}
typedef hour {
type uint8 { range "0..23"; }
description
"An hour of a day.";
}
typedef hour {
type uint8 { range "0..23"; }
description
"An hour of a day.";
}
typedef hour-or-all {
type union {
type hour;
type wildcard;
}
description
"An hour of a day or a wildcard indicating all hours
of a day.";
typedef hour-or-all {
type union {
type hour;
type wildcard;
}
description
"An hour of a day or a wildcard indicating all hours
of a day.";
}
}
typedef minute {
type uint8 { range "0..59"; }
description
"A minute of an hour.";
}
typedef minute {
type uint8 { range "0..59"; }
description
"A minute of an hour.";
}
typedef minute-or-all {
type union {
type minute;
type wildcard;
}
description
"A minute of an hour or a wildcard indicating all
minutes of an hour.";
}
typedef minute-or-all {
type union {
type minute;
type wildcard;
}
description
"A minute of an hour or a wildcard indicating all
minutes of an hour.";
}
typedef second {
type uint8 { range "0..59"; }
description
"A second of a minute.";
}
typedef second {
type uint8 { range "0..59"; }
description
"A second of a minute.";
}
typedef second-or-all {
type union {
type second;
type wildcard;
}
description
"A second of a minute or a wildcard indicating all
seconds of a minute.";
}
typedef second-or-all {
type union {
type second;
type wildcard;
}
description
"A second of a minute or a wildcard indicating all
seconds of a minute.";
}
typedef status-code {
type int32;
description
"A status code returned by the execution of a Task. Note
that the actual range is implementation dependent, but it
should be portable to use values in the range 0..127 for
regular exit codes. By convention, 0 indicates successful
termination. Negative values may be used to indicate
abnormal termination due to a signal; the absolute value
may identify the signal number in this case.";
}
typedef status-code {
type int32;
description
"A status code returned by the execution of a Task. Note
that the actual range is implementation dependent, but it
should be portable to use values in the range 0..127 for
regular exit codes. By convention, 0 indicates successful
termination. Negative values may be used to indicate
abnormal termination due to a signal; the absolute value
may identify the signal number in this case.";
}
typedef timezone-offset {
type string {
pattern 'Z|[\+\-]\d{2}:\d{2}';
}
description
"A time zone offset as it is used by the date-and-time type
defined in the ietf-yang-types module. The value Z is
equivalent to +00:00. The value -00:00 indicates an
unknown time-offset.";
reference
"RFC 6991: Common YANG Data Types";
}
typedef timezone-offset {
type string {
pattern 'Z|[\+\-]\d{2}:\d{2}';
}
description
"A time zone offset as it is used by the date-and-time type
defined in the ietf-yang-types module. The value Z is
equivalent to +00:00. The value -00:00 indicates an
unknown time-offset.";
reference
"RFC 6991: Common YANG Data Types";
}
/*
* Groupings
*/
/*
* Groupings
*/
grouping registry-grouping {
description
"This grouping models a list of entries in a registry
that identify functions of a Task.";
grouping registry-grouping {
description
"This grouping models a list of entries in a registry
that identify functions of a Task.";
list function {
key uri;
description
"A list of entries in a registry identifying functions.";
list function {
key uri;
description
"A list of entries in a registry identifying functions.";
leaf uri {
type inet:uri;
description
"A URI identifying an entry in a registry.";
}
leaf uri {
type inet:uri;
description
"A URI identifying an entry in a registry.";
}
leaf-list role {
type string;
description
"A set of roles for the identified registry entry.";
}
}
}
leaf-list role {
type string;
description
"A set of roles for the identified registry entry.";
}
}
}
grouping options-grouping {
description
"A list of options of a Task. Each option is a name/value
pair (where the value may be absent).";
grouping options-grouping {
description
"A list of options of a Task. Each option is a name/value
pair (where the value may be absent).";
list option {
key "id";
list option {
key "id";
ordered-by user;
description
"A list of options passed to the Task. It is a list of
key/value pairs and may be used to model options.
Options may be used to identify the role of a Task
or to pass a Channel name to a Task.";
ordered-by user;
description
"A list of options passed to the Task. It is a list of
key/value pairs and may be used to model options.
Options may be used to identify the role of a Task
or to pass a Channel name to a Task.";
leaf id {
type lmap:identifier;
description
"An identifier uniquely identifying an option. This
identifier is required by YANG to uniquely identify
a name/value pair, but it otherwise has no semantic
value";
}
leaf id {
type lmap:identifier;
description
"An identifier uniquely identifying an option. This
identifier is required by YANG to uniquely identify
a name/value pair, but it otherwise has no semantic
value";
}
leaf name {
type string;
description
"The name of the option.";
}
leaf name {
type string;
description
"The name of the option.";
}
leaf value {
type string;
description
"The value of the option.";
}
}
}
}
<CODE ENDS>
leaf value {
type string;
description
"The value of the option.";
}
}
}
}
<CODE ENDS>
This module imports definitions from [RFC6536], [RFC6991], and the common LMAP module, and it references [RFC7398].
此模块从[RFC6536]、[RFC6991]和通用LMAP模块导入定义，并引用[RFC7398]。
<CODE BEGINS> file "ietf-lmap-control@2017-08-08.yang"
module ietf-lmap-control {
<CODE BEGINS> file "ietf-lmap-control@2017-08-08.yang"
module ietf-lmap-control {
yang-version 1.1;
namespace "urn:ietf:params:xml:ns:yang:ietf-lmap-control";
prefix "lmapc";
yang-version 1.1;
namespace "urn:ietf:params:xml:ns:yang:ietf-lmap-control";
prefix "lmapc";
import ietf-yang-types {
prefix yang;
}
import ietf-netconf-acm {
import ietf-yang-types {
prefix yang;
}
import ietf-netconf-acm {
prefix nacm;
}
import ietf-lmap-common {
prefix lmap;
}
prefix nacm;
}
import ietf-lmap-common {
prefix lmap;
}
organization "IETF Large-Scale Measurement of Broadband Performance Working Group";
组织“IETF宽带性能大规模测量工作组”；
contact
"WG Web: <https://datatracker.ietf.org/wg/lmap>
WG List: <mailto:lmap@ietf.org>
contact
"WG Web: <https://datatracker.ietf.org/wg/lmap>
WG List: <mailto:lmap@ietf.org>
Editor: Juergen Schoenwaelder
<j.schoenwaelder@jacobs-university.de>
Editor: Juergen Schoenwaelder
<j.schoenwaelder@jacobs-university.de>
Editor: Vaibhav Bajpai
<bajpaiv@in.tum.de>";
Editor: Vaibhav Bajpai
<bajpaiv@in.tum.de>";
description "This module defines a data model for controlling Measurement Agents that are part of a Large-Scale Measurement Platform (LMAP). This data model is expected to be implemented by Measurement Agents.";
描述“该模块定义了一个数据模型，用于控制作为大规模测量平台（LMAP）一部分的测量代理。该数据模型预计将由测量代理实现。”；
revision "2017-08-08" {
description
"Initial version";
reference
"RFC 8194: A YANG Data Model for LMAP Measurement Agents";
}
revision "2017-08-08" {
description
"Initial version";
reference
"RFC 8194: A YANG Data Model for LMAP Measurement Agents";
}
/*
* Typedefs
*/
/*
* Typedefs
*/
typedef event-ref {
type leafref {
path "/lmap/events/event/name";
}
description
"This type is used by data models that need to reference
a configured event source.";
}
typedef event-ref {
type leafref {
path "/lmap/events/event/name";
}
description
"This type is used by data models that need to reference
a configured event source.";
}
typedef task-ref {
type leafref {
typedef task-ref {
type leafref {
path "/lmap/tasks/task/name";
}
description
"This type is used by data models that need to reference
a configured Task.";
}
path "/lmap/tasks/task/name";
}
description
"This type is used by data models that need to reference
a configured Task.";
}
typedef schedule-ref {
type leafref {
path "/lmap/schedules/schedule/name";
}
description
"This type is used by data models that need to reference
a configured Schedule.";
}
typedef schedule-ref {
type leafref {
path "/lmap/schedules/schedule/name";
}
description
"This type is used by data models that need to reference
a configured Schedule.";
}
/*
* Groupings
*/
/*
* Groupings
*/
grouping start-end-grouping {
description
"A grouping that provides start and end times for
Event objects.";
leaf start {
type yang:date-and-time;
description
"The date and time when the Event object
starts to create triggers.";
}
leaf end {
type yang:date-and-time;
description
"The date and time when the Event object
stops to create triggers.
grouping start-end-grouping {
description
"A grouping that provides start and end times for
Event objects.";
leaf start {
type yang:date-and-time;
description
"The date and time when the Event object
starts to create triggers.";
}
leaf end {
type yang:date-and-time;
description
"The date and time when the Event object
stops to create triggers.
It is generally a good idea to always configure
an end time and to refresh the end time as needed
to ensure that agents that lose connectivity to
their Controller do not continue executing Schedules
forever.";
}
}
It is generally a good idea to always configure
an end time and to refresh the end time as needed
to ensure that agents that lose connectivity to
their Controller do not continue executing Schedules
forever.";
}
}
/*
* Capability, configuration, and state data nodes
*/
/*
* Capability, configuration, and state data nodes
*/
container lmap {
description
"Configuration and control of a Measurement Agent.";
container lmap {
description
"Configuration and control of a Measurement Agent.";
container capabilities {
config false;
description
"Agent capabilities including a list of supported Tasks.";
container capabilities {
config false;
description
"Agent capabilities including a list of supported Tasks.";
leaf version {
type string;
config false;
mandatory true;
description
"A short description of the software implementing the
Measurement Agent. This should include the version
number of the Measurement Agent software.";
}
leaf version {
type string;
config false;
mandatory true;
description
"A short description of the software implementing the
Measurement Agent. This should include the version
number of the Measurement Agent software.";
}
leaf-list tag {
type lmap:tag;
config false;
description
"An optional unordered set of tags that provide
additional information about the capabilities of
the Measurement Agent.";
}
leaf-list tag {
type lmap:tag;
config false;
description
"An optional unordered set of tags that provide
additional information about the capabilities of
the Measurement Agent.";
}
container tasks {
description
"A list of Tasks that the Measurement Agent supports.";
container tasks {
description
"A list of Tasks that the Measurement Agent supports.";
list task {
key name;
description
"The list of Tasks supported by the Measurement Agent.";
list task {
key name;
description
"The list of Tasks supported by the Measurement Agent.";
leaf name {
type lmap:identifier;
description
"The unique name of a Task capability.";
}
leaf name {
type lmap:identifier;
description
"The unique name of a Task capability.";
}
uses lmap:registry-grouping;
使用lmap：注册表分组；
leaf version {
type string;
leaf version {
type string;
description
"A short description of the software implementing
the Task. This should include the version
number of the Measurement Task software.";
}
description
"A short description of the software implementing
the Task. This should include the version
number of the Measurement Task software.";
}
leaf program {
type string;
description
"The (local) program to invoke in order to execute
the Task.";
}
}
}
}
leaf program {
type string;
description
"The (local) program to invoke in order to execute
the Task.";
}
}
}
}
/*
* Agent Configuration
*/
/*
* Agent Configuration
*/
container agent {
description
"Configuration of parameters affecting the whole
Measurement Agent.";
container agent {
description
"Configuration of parameters affecting the whole
Measurement Agent.";
leaf agent-id {
type yang:uuid;
description
"The agent-id identifies a Measurement Agent with
a very low probability of collision. In certain
deployments, the agent-id may be considered
sensitive, and hence this object is optional.";
}
leaf agent-id {
type yang:uuid;
description
"The agent-id identifies a Measurement Agent with
a very low probability of collision. In certain
deployments, the agent-id may be considered
sensitive, and hence this object is optional.";
}
leaf group-id {
type string;
description
"The group-id identifies a group of Measurement
Agents. In certain deployments, the group-id
may be considered less sensitive than the
agent-id.";
}
leaf group-id {
type string;
description
"The group-id identifies a group of Measurement
Agents. In certain deployments, the group-id
may be considered less sensitive than the
agent-id.";
}
leaf measurement-point {
type string;
description
"The measurement point indicating where the
Measurement Agent is located on a path.";
leaf measurement-point {
type string;
description
"The measurement point indicating where the
Measurement Agent is located on a path.";
reference
"RFC 7398: A Reference Path and Measurement Points
for Large-Scale Measurement of Broadband
Performance";
}
reference
"RFC 7398: A Reference Path and Measurement Points
for Large-Scale Measurement of Broadband
Performance";
}
leaf report-agent-id {
type boolean;
must '. != "true" or ../agent-id' {
description
"An agent-id must exist for this to be set
to true.";
}
default false;
description
"The 'report-agent-id' controls whether the
'agent-id' is reported to Collectors.";
}
leaf report-agent-id {
type boolean;
must '. != "true" or ../agent-id' {
description
"An agent-id must exist for this to be set
to true.";
}
default false;
description
"The 'report-agent-id' controls whether the
'agent-id' is reported to Collectors.";
}
leaf report-group-id {
type boolean;
must '. != "true" or ../group-id' {
description
"A group-id must exist for this to be set
to true.";
}
default false;
description
"The 'report-group-id' controls whether the
'group-id' is reported to Collectors.";
}
leaf report-group-id {
type boolean;
must '. != "true" or ../group-id' {
description
"A group-id must exist for this to be set
to true.";
}
default false;
description
"The 'report-group-id' controls whether the
'group-id' is reported to Collectors.";
}
leaf report-measurement-point {
type boolean;
must '. != "true" or ../measurement-point' {
description
"A measurement-point must exist for this to be
set to true.";
}
default false;
description
"The 'report-measurement-point' controls whether
the 'measurement-point' is reported to Collectors.";
}
leaf report-measurement-point {
type boolean;
must '. != "true" or ../measurement-point' {
description
"A measurement-point must exist for this to be
set to true.";
}
default false;
description
"The 'report-measurement-point' controls whether
the 'measurement-point' is reported to Collectors.";
}
leaf controller-timeout {
type uint32;
units "seconds";
leaf controller-timeout {
type uint32;
units "seconds";
description
"A timer is started after each successful contact
with a Controller. When the timer reaches the
controller-timeout, an event (controller-lost) is
raised indicating that connectivity to the Controller
has been lost.";
}
description
"A timer is started after each successful contact
with a Controller. When the timer reaches the
controller-timeout, an event (controller-lost) is
raised indicating that connectivity to the Controller
has been lost.";
}
leaf last-started {
type yang:date-and-time;
config false;
mandatory true;
description
"The date and time the Measurement Agent last started.";
}
}
leaf last-started {
type yang:date-and-time;
config false;
mandatory true;
description
"The date and time the Measurement Agent last started.";
}
}
/*
* Task Configuration
*/
/*
* Task Configuration
*/
container tasks {
description
"Configuration of LMAP Tasks.";
container tasks {
description
"Configuration of LMAP Tasks.";
list task {
key name;
description
"The list of Tasks configured on the Measurement
Agent. Note that a configured Task MUST resolve to a
Task listed in the capabilities. Attempts to execute
a configured Task that is not listed in the capabilities
result in a runtime execution error.";
list task {
key name;
description
"The list of Tasks configured on the Measurement
Agent. Note that a configured Task MUST resolve to a
Task listed in the capabilities. Attempts to execute
a configured Task that is not listed in the capabilities
result in a runtime execution error.";
leaf name {
type lmap:identifier;
description
"The unique name of a Task.";
}
leaf name {
type lmap:identifier;
description
"The unique name of a Task.";
}
uses lmap:registry-grouping;
使用lmap：注册表分组；
leaf program {
type string;
nacm:default-deny-write;
leaf program {
type string;
nacm:default-deny-write;
description
"The (local) program to invoke in order to execute
the Task. If this leaf is not set, then the system
will try to identify a suitable program based on
the registry information present.";
}
description
"The (local) program to invoke in order to execute
the Task. If this leaf is not set, then the system
will try to identify a suitable program based on
the registry information present.";
}
uses lmap:options-grouping {
description
"The list of Task-specific options.";
}
uses lmap:options-grouping {
description
"The list of Task-specific options.";
}
leaf-list tag {
type lmap:identifier;
description
"A set of Task-specific tags that are reported
together with the measurement results to a Collector.
A tag can be used, for example, to carry the
Measurement Cycle ID.";
}
}
}
leaf-list tag {
type lmap:identifier;
description
"A set of Task-specific tags that are reported
together with the measurement results to a Collector.
A tag can be used, for example, to carry the
Measurement Cycle ID.";
}
}
}
/*
* Schedule Instructions
*/
/*
* Schedule Instructions
*/
container schedules {
description
"Configuration of LMAP Schedules. Schedules control
which Tasks are executed by the LMAP implementation.";
container schedules {
description
"Configuration of LMAP Schedules. Schedules control
which Tasks are executed by the LMAP implementation.";
list schedule {
key name;
description
"Configuration of a particular Schedule.";
list schedule {
key name;
description
"Configuration of a particular Schedule.";
leaf name {
type lmap:identifier;
description
"The locally unique, administratively assigned name
for this Schedule.";
}
leaf name {
type lmap:identifier;
description
"The locally unique, administratively assigned name
for this Schedule.";
}
leaf start {
type event-ref;
mandatory true;
leaf start {
type event-ref;
mandatory true;
description
"The event source controlling the start of the
scheduled Actions.";
}
description
"The event source controlling the start of the
scheduled Actions.";
}
choice stop {
description
"This choice contains optional leafs that control the
graceful forced termination of scheduled Actions.
When the end has been reached, the scheduled Actions
should be forced to terminate the measurements.
This may involve being active some additional time in
order to properly finish the Action's activity (e.g.,
waiting for any messages that are still outstanding).";
choice stop {
description
"This choice contains optional leafs that control the
graceful forced termination of scheduled Actions.
When the end has been reached, the scheduled Actions
should be forced to terminate the measurements.
This may involve being active some additional time in
order to properly finish the Action's activity (e.g.,
waiting for any messages that are still outstanding).";
leaf end {
type event-ref;
description
"The event source controlling the graceful
forced termination of the scheduled Actions.";
}
leaf end {
type event-ref;
description
"The event source controlling the graceful
forced termination of the scheduled Actions.";
}
leaf duration {
type uint32;
units "seconds";
description
"The duration controlling the graceful forced
termination of the scheduled Actions.";
}
}
leaf duration {
type uint32;
units "seconds";
description
"The duration controlling the graceful forced
termination of the scheduled Actions.";
}
}
leaf execution-mode {
type enumeration {
enum sequential {
value 1;
description
"The Actions of the Schedule are executed
sequentially.";
}
enum parallel {
value 2;
description
"The Actions of the Schedule are executed
concurrently.";
}
enum pipelined {
value 3;
leaf execution-mode {
type enumeration {
enum sequential {
value 1;
description
"The Actions of the Schedule are executed
sequentially.";
}
enum parallel {
value 2;
description
"The Actions of the Schedule are executed
concurrently.";
}
enum pipelined {
value 3;
description
"The Actions of the Schedule are executed in a
pipelined mode. Output created by an Action is
passed as input to the subsequent Action.";
}
}
default pipelined;
description
"The execution mode of this Schedule determines in
which order the Actions of the Schedule are executed.";
}
description
"The Actions of the Schedule are executed in a
pipelined mode. Output created by an Action is
passed as input to the subsequent Action.";
}
}
default pipelined;
description
"The execution mode of this Schedule determines in
which order the Actions of the Schedule are executed.";
}
leaf-list tag {
type lmap:tag;
description
"A set of Schedule-specific tags that are reported
together with the measurement results to a Collector.";
}
leaf-list tag {
type lmap:tag;
description
"A set of Schedule-specific tags that are reported
together with the measurement results to a Collector.";
}
leaf-list suppression-tag {
type lmap:tag;
description
"A set of Suppression tags that are used to select
Schedules to be suppressed.";
}
leaf-list suppression-tag {
type lmap:tag;
description
"A set of Suppression tags that are used to select
Schedules to be suppressed.";
}
leaf state {
type enumeration {
enum enabled {
value 1;
description
"The value 'enabled' indicates that the
Schedule is currently enabled.";
}
enum disabled {
value 2;
description
"The value 'disabled' indicates that the
Schedule is currently disabled.";
}
enum running {
value 3;
description
"The value 'running' indicates that the
Schedule is currently running.";
}
enum suppressed {
value 4;
leaf state {
type enumeration {
enum enabled {
value 1;
description
"The value 'enabled' indicates that the
Schedule is currently enabled.";
}
enum disabled {
value 2;
description
"The value 'disabled' indicates that the
Schedule is currently disabled.";
}
enum running {
value 3;
description
"The value 'running' indicates that the
Schedule is currently running.";
}
enum suppressed {
value 4;
description
"The value 'suppressed' indicates that the
Schedule is currently suppressed.";
}
}
config false;
mandatory true;
description
"The current state of the Schedule.";
}
description
"The value 'suppressed' indicates that the
Schedule is currently suppressed.";
}
}
config false;
mandatory true;
description
"The current state of the Schedule.";
}
leaf storage {
type yang:gauge64;
units "bytes";
config false;
mandatory true;
description
"The amount of secondary storage (e.g., allocated in a
file system) holding temporary data allocated to the
Schedule in bytes. This object reports the amount of
allocated physical storage and not the storage used
by logical data records.";
}
leaf storage {
type yang:gauge64;
units "bytes";
config false;
mandatory true;
description
"The amount of secondary storage (e.g., allocated in a
file system) holding temporary data allocated to the
Schedule in bytes. This object reports the amount of
allocated physical storage and not the storage used
by logical data records.";
}
leaf invocations {
type yang:counter32;
config false;
mandatory true;
description
"Number of invocations of this Schedule. This counter
does not include suppressed invocations or invocations
that were prevented due to an overlap with a previous
invocation of this Schedule.";
}
leaf invocations {
type yang:counter32;
config false;
mandatory true;
description
"Number of invocations of this Schedule. This counter
does not include suppressed invocations or invocations
that were prevented due to an overlap with a previous
invocation of this Schedule.";
}
leaf suppressions {
type yang:counter32;
config false;
mandatory true;
description
"Number of suppressed executions of this Schedule.";
}
leaf suppressions {
type yang:counter32;
config false;
mandatory true;
description
"Number of suppressed executions of this Schedule.";
}
leaf overlaps {
type yang:counter32;
config false;
mandatory true;
leaf overlaps {
type yang:counter32;
config false;
mandatory true;
description
"Number of executions prevented due to overlaps with
a previous invocation of this Schedule.";
}
description
"Number of executions prevented due to overlaps with
a previous invocation of this Schedule.";
}
leaf failures {
type yang:counter32;
config false;
mandatory true;
description
"Number of failed executions of this Schedule. A
failed execution is an execution where at least
one Action failed.";
}
leaf failures {
type yang:counter32;
config false;
mandatory true;
description
"Number of failed executions of this Schedule. A
failed execution is an execution where at least
one Action failed.";
}
leaf last-invocation {
type yang:date-and-time;
config false;
description
"The date and time of the last invocation of
this Schedule.";
}
leaf last-invocation {
type yang:date-and-time;
config false;
description
"The date and time of the last invocation of
this Schedule.";
}
list action {
key name;
description
"An Action describes a Task that is invoked by the
Schedule. Multiple Actions are invoked according to
the execution-mode of the Schedule.";
list action {
key name;
description
"An Action describes a Task that is invoked by the
Schedule. Multiple Actions are invoked according to
the execution-mode of the Schedule.";
leaf name {
type lmap:identifier;
description
"The unique identifier for this Action.";
}
leaf name {
type lmap:identifier;
description
"The unique identifier for this Action.";
}
leaf task {
type task-ref;
mandatory true;
description
"The Task invoked by this Action.";
}
leaf task {
type task-ref;
mandatory true;
description
"The Task invoked by this Action.";
}
container parameters {
description
"This container is a placeholder for runtime
parameters defined in Task-specific data models
augmenting the base LMAP control data model.";
container parameters {
description
"This container is a placeholder for runtime
parameters defined in Task-specific data models
augmenting the base LMAP control data model.";
choice extension {
description
"This choice is provided to augment in different
sets of parameters.";
}
}
choice extension {
description
"This choice is provided to augment in different
sets of parameters.";
}
}
uses lmap:options-grouping {
description
"The list of Action-specific options that are
appended to the list of Task-specific options.";
}
uses lmap:options-grouping {
description
"The list of Action-specific options that are
appended to the list of Task-specific options.";
}
leaf-list destination {
type schedule-ref;
description
"A set of Schedules receiving the output produced
by this Action. The output is stored temporarily
since the Destination Schedules will in general
not be running when output is passed to them. The
behavior of an Action passing data to its own
Schedule is implementation specific.
leaf-list destination {
type schedule-ref;
description
"A set of Schedules receiving the output produced
by this Action. The output is stored temporarily
since the Destination Schedules will in general
not be running when output is passed to them. The
behavior of an Action passing data to its own
Schedule is implementation specific.
Data passed to a sequential or pipelined Schedule
is received by the Schedule's first Action. Data
passed to a parallel Schedule is received by all
Actions of the Schedule.";
}
Data passed to a sequential or pipelined Schedule
is received by the Schedule's first Action. Data
passed to a parallel Schedule is received by all
Actions of the Schedule.";
}
leaf-list tag {
type lmap:tag;
description
"A set of Action-specific tags that are reported
together with the measurement results to a
Collector.";
}
leaf-list tag {
type lmap:tag;
description
"A set of Action-specific tags that are reported
together with the measurement results to a
Collector.";
}
leaf-list suppression-tag {
type lmap:tag;
description
"A set of Suppression tags that are used to select
Actions to be suppressed.";
}
leaf-list suppression-tag {
type lmap:tag;
description
"A set of Suppression tags that are used to select
Actions to be suppressed.";
}
leaf state {
type enumeration {
enum enabled {
value 1;
leaf state {
type enumeration {
enum enabled {
value 1;
description
"The value 'enabled' indicates that the
Action is currently enabled.";
}
enum disabled {
value 2;
description
"The value 'disabled' indicates that the
Action is currently disabled.";
}
enum running {
value 3;
description
"The value 'running' indicates that the
Action is currently running.";
}
enum suppressed {
value 4;
description
"The value 'suppressed' indicates that the
Action is currently suppressed.";
}
}
config false;
mandatory true;
description
"The current state of the Action.";
}
description
"The value 'enabled' indicates that the
Action is currently enabled.";
}
enum disabled {
value 2;
description
"The value 'disabled' indicates that the
Action is currently disabled.";
}
enum running {
value 3;
description
"The value 'running' indicates that the
Action is currently running.";
}
enum suppressed {
value 4;
description
"The value 'suppressed' indicates that the
Action is currently suppressed.";
}
}
config false;
mandatory true;
description
"The current state of the Action.";
}
leaf storage {
type yang:gauge64;
units "bytes";
config false;
mandatory true;
description
"The amount of secondary storage (e.g., allocated in a
file system) holding temporary data allocated to the
Schedule in bytes. This object reports the amount of
allocated physical storage and not the storage used
by logical data records.";
}
leaf storage {
type yang:gauge64;
units "bytes";
config false;
mandatory true;
description
"The amount of secondary storage (e.g., allocated in a
file system) holding temporary data allocated to the
Schedule in bytes. This object reports the amount of
allocated physical storage and not the storage used
by logical data records.";
}
leaf invocations {
type yang:counter32;
config false;
mandatory true;
leaf invocations {
type yang:counter32;
config false;
mandatory true;
description
"Number of invocations of this Action. This counter
does not include suppressed invocations or invocations
that were prevented due to an overlap with a previous
invocation of this Action.";
}
description
"Number of invocations of this Action. This counter
does not include suppressed invocations or invocations
that were prevented due to an overlap with a previous
invocation of this Action.";
}
leaf suppressions {
type yang:counter32;
config false;
mandatory true;
description
"Number of suppressed executions of this Action.";
}
leaf suppressions {
type yang:counter32;
config false;
mandatory true;
description
"Number of suppressed executions of this Action.";
}
leaf overlaps {
type yang:counter32;
config false;
mandatory true;
description
"Number of executions prevented due to overlaps with
a previous invocation of this Action.";
}
leaf overlaps {
type yang:counter32;
config false;
mandatory true;
description
"Number of executions prevented due to overlaps with
a previous invocation of this Action.";
}
leaf failures {
type yang:counter32;
config false;
mandatory true;
description
"Number of failed executions of this Action.";
}
leaf failures {
type yang:counter32;
config false;
mandatory true;
description
"Number of failed executions of this Action.";
}
leaf last-invocation {
type yang:date-and-time;
config false;
mandatory true;
description
"The date and time of the last invocation of
this Action.";
}
leaf last-invocation {
type yang:date-and-time;
config false;
mandatory true;
description
"The date and time of the last invocation of
this Action.";
}
leaf last-completion {
type yang:date-and-time;
config false;
mandatory true;
description
"The date and time of the last completion of
this Action.";
leaf last-completion {
type yang:date-and-time;
config false;
mandatory true;
description
"The date and time of the last completion of
this Action.";
}
}
leaf last-status {
type lmap:status-code;
config false;
mandatory true;
description
"The status code returned by the last execution of
this Action.";
}
leaf last-status {
type lmap:status-code;
config false;
mandatory true;
description
"The status code returned by the last execution of
this Action.";
}
leaf last-message {
type string;
config false;
mandatory true;
description
"The status message produced by the last execution
of this Action.";
}
leaf last-message {
type string;
config false;
mandatory true;
description
"The status message produced by the last execution
of this Action.";
}
leaf last-failed-completion {
type yang:date-and-time;
config false;
mandatory true;
description
"The date and time of the last failed completion
of this Action.";
}
leaf last-failed-completion {
type yang:date-and-time;
config false;
mandatory true;
description
"The date and time of the last failed completion
of this Action.";
}
leaf last-failed-status {
type lmap:status-code;
config false;
mandatory true;
description
"The status code returned by the last failed
execution of this Action.";
}
leaf last-failed-status {
type lmap:status-code;
config false;
mandatory true;
description
"The status code returned by the last failed
execution of this Action.";
}
leaf last-failed-message {
type string;
config false;
mandatory true;
description
"The status message produced by the last failed
execution of this Action.";
}
}
}
leaf last-failed-message {
type string;
config false;
mandatory true;
description
"The status message produced by the last failed
execution of this Action.";
}
}
}
}
}
/*
* Suppression Instructions
*/
/*
* Suppression Instructions
*/
container suppressions {
description
"Suppression information to prevent Schedules or
certain Actions from starting.";
container suppressions {
description
"Suppression information to prevent Schedules or
certain Actions from starting.";
list suppression {
key name;
description
"Configuration of a particular Suppression.";
list suppression {
key name;
description
"Configuration of a particular Suppression.";
leaf name {
type lmap:identifier;
description
"The locally unique, administratively assigned name
for this Suppression.";
}
leaf name {
type lmap:identifier;
description
"The locally unique, administratively assigned name
for this Suppression.";
}
leaf start {
type event-ref;
description
"The event source controlling the start of the
Suppression period.";
}
leaf start {
type event-ref;
description
"The event source controlling the start of the
Suppression period.";
}
leaf end {
type event-ref;
description
"The event source controlling the end of the
Suppression period. If not present, Suppression
continues indefinitely.";
}
leaf end {
type event-ref;
description
"The event source controlling the end of the
Suppression period. If not present, Suppression
continues indefinitely.";
}
leaf-list match {
type lmap:glob-pattern;
description
"A set of Suppression match patterns. The Suppression
will apply to all Schedules (and their Actions) that
have a matching value in their suppression-tags
and to all Actions that have a matching value in
their suppression-tags.";
}
leaf-list match {
type lmap:glob-pattern;
description
"A set of Suppression match patterns. The Suppression
will apply to all Schedules (and their Actions) that
have a matching value in their suppression-tags
and to all Actions that have a matching value in
their suppression-tags.";
}
leaf stop-running {
type boolean;
default false;
description
"If 'stop-running' is true, running Schedules and
Actions matching the Suppression will be terminated
when Suppression is activated. If 'stop-running' is
false, running Schedules and Actions will not be
affected if Suppression is activated.";
}
leaf stop-running {
type boolean;
default false;
description
"If 'stop-running' is true, running Schedules and
Actions matching the Suppression will be terminated
when Suppression is activated. If 'stop-running' is
false, running Schedules and Actions will not be
affected if Suppression is activated.";
}
leaf state {
type enumeration {
enum enabled {
value 1;
description
"The value 'enabled' indicates that the
Suppression is currently enabled.";
}
enum disabled {
value 2;
description
"The value 'disabled' indicates that the
Suppression is currently disabled.";
}
enum active {
value 3;
description
"The value 'active' indicates that the
Suppression is currently active.";
}
}
config false;
mandatory true;
description
"The current state of the Suppression.";
}
}
}
leaf state {
type enumeration {
enum enabled {
value 1;
description
"The value 'enabled' indicates that the
Suppression is currently enabled.";
}
enum disabled {
value 2;
description
"The value 'disabled' indicates that the
Suppression is currently disabled.";
}
enum active {
value 3;
description
"The value 'active' indicates that the
Suppression is currently active.";
}
}
config false;
mandatory true;
description
"The current state of the Suppression.";
}
}
}
/*
* Event Instructions
*/
/*
* Event Instructions
*/
container events { description "Configuration of LMAP events.
容器事件{description“配置LMAP事件。
Implementations may be forced to delay acting upon the occurrence of events in the face of local constraints. An Action triggered by an event therefore should not rely on the accuracy provided by the scheduler implementation.";
面对局部约束，实现可能被迫延迟事件发生时的操作。因此，由事件触发的操作不应依赖于计划程序实现提供的准确性。“；
list event {
key name;
description
"The list of event sources configured on the
Measurement Agent.";
list event {
key name;
description
"The list of event sources configured on the
Measurement Agent.";
leaf name {
type lmap:identifier;
description
"The unique name of an event source.";
}
leaf name {
type lmap:identifier;
description
"The unique name of an event source.";
}
leaf random-spread {
type uint32;
units seconds;
description
"This optional leaf adds a random spread to the
computation of the event's trigger time. The
random spread is a uniformly distributed random
number taken from the interval [0:random-spread].";
}
leaf random-spread {
type uint32;
units seconds;
description
"This optional leaf adds a random spread to the
computation of the event's trigger time. The
random spread is a uniformly distributed random
number taken from the interval [0:random-spread].";
}
leaf cycle-interval {
type uint32;
units seconds;
description
"The optional cycle-interval defines the duration
of the time interval in seconds that is used to
calculate cycle numbers. No cycle number is
calculated if the optional cycle-interval does
not exist.";
}
leaf cycle-interval {
type uint32;
units seconds;
description
"The optional cycle-interval defines the duration
of the time interval in seconds that is used to
calculate cycle numbers. No cycle number is
calculated if the optional cycle-interval does
not exist.";
}
choice event-type {
description
"Different types of events are handled by
different branches of this choice. Note that
this choice can be extended via augmentations.";
choice event-type {
description
"Different types of events are handled by
different branches of this choice. Note that
this choice can be extended via augmentations.";
case periodic {
container periodic {
case periodic {
container periodic {
description "A periodic timing object triggers periodically according to a regular interval.";
描述“定期定时对象根据定期间隔定期触发。”；
leaf interval {
type uint32 {
range "1..max";
}
units "seconds";
mandatory true;
description
"The number of seconds between two triggers
generated by this periodic timing object.";
}
uses start-end-grouping;
}
}
leaf interval {
type uint32 {
range "1..max";
}
units "seconds";
mandatory true;
description
"The number of seconds between two triggers
generated by this periodic timing object.";
}
uses start-end-grouping;
}
}
case calendar {
container calendar {
description
"A calendar timing object triggers based on the
current calendar date and time.";
case calendar {
container calendar {
description
"A calendar timing object triggers based on the
current calendar date and time.";
leaf-list month {
type lmap:month-or-all;
min-elements 1;
description
"A set of months at which this calendar timing
will trigger. The wildcard means all months.";
}
leaf-list month {
type lmap:month-or-all;
min-elements 1;
description
"A set of months at which this calendar timing
will trigger. The wildcard means all months.";
}
leaf-list day-of-month {
type lmap:day-of-months-or-all;
min-elements 1;
description
"A set of days of the month at which this
calendar timing will trigger. The wildcard means
all days of a month.";
}
leaf-list day-of-month {
type lmap:day-of-months-or-all;
min-elements 1;
description
"A set of days of the month at which this
calendar timing will trigger. The wildcard means
all days of a month.";
}
leaf-list day-of-week {
type lmap:weekday-or-all;
min-elements 1;
description
"A set of weekdays at which this calendar timing
will trigger. The wildcard means all weekdays.";
}
leaf-list day-of-week {
type lmap:weekday-or-all;
min-elements 1;
description
"A set of weekdays at which this calendar timing
will trigger. The wildcard means all weekdays.";
}
leaf-list hour {
type lmap:hour-or-all;
min-elements 1;
description
"A set of hours at which this calendar timing will
trigger. The wildcard means all hours of a day.";
}
leaf-list hour {
type lmap:hour-or-all;
min-elements 1;
description
"A set of hours at which this calendar timing will
trigger. The wildcard means all hours of a day.";
}
leaf-list minute {
type lmap:minute-or-all;
min-elements 1;
description
"A set of minutes at which this calendar timing
will trigger. The wildcard means all minutes of
an hour.";
}
leaf-list minute {
type lmap:minute-or-all;
min-elements 1;
description
"A set of minutes at which this calendar timing
will trigger. The wildcard means all minutes of
an hour.";
}
leaf-list second {
type lmap:second-or-all;
min-elements 1;
description
"A set of seconds at which this calendar timing
will trigger. The wildcard means all seconds of
a minute.";
}
leaf-list second {
type lmap:second-or-all;
min-elements 1;
description
"A set of seconds at which this calendar timing
will trigger. The wildcard means all seconds of
a minute.";
}
leaf timezone-offset {
type lmap:timezone-offset;
description
"The time zone in which this calendar timing
object will be evaluated. If not present,
the system's local time zone will be used.";
}
uses start-end-grouping;
}
}
leaf timezone-offset {
type lmap:timezone-offset;
description
"The time zone in which this calendar timing
object will be evaluated. If not present,
the system's local time zone will be used.";
}
uses start-end-grouping;
}
}
case one-off {
container one-off {
description
"A one-off timing object triggers exactly once.";
case one-off {
container one-off {
description
"A one-off timing object triggers exactly once.";
leaf time {
type yang:date-and-time;
mandatory true;
description
"This one-off timing object triggers once at
the configured date and time.";
leaf time {
type yang:date-and-time;
mandatory true;
description
"This one-off timing object triggers once at
the configured date and time.";
}
}
}
}
}
}
case immediate {
leaf immediate {
type empty;
mandatory true;
description
"This immediate Event object triggers immediately
when it is configured.";
}
}
case immediate {
leaf immediate {
type empty;
mandatory true;
description
"This immediate Event object triggers immediately
when it is configured.";
}
}
case startup {
leaf startup {
type empty;
mandatory true;
description
"This startup Event object triggers whenever the
Measurement Agent (re)starts.";
}
}
case startup {
leaf startup {
type empty;
mandatory true;
description
"This startup Event object triggers whenever the
Measurement Agent (re)starts.";
}
}
case controller-lost {
leaf controller-lost {
type empty;
mandatory true;
description
"The controller-lost Event object triggers when
the connectivity to the Controller has been lost
for at least 'controller-timeout' seconds.";
}
}
case controller-lost {
leaf controller-lost {
type empty;
mandatory true;
description
"The controller-lost Event object triggers when
the connectivity to the Controller has been lost
for at least 'controller-timeout' seconds.";
}
}
case controller-connected {
leaf controller-connected {
type empty;
mandatory true;
description
"The controller-connected Event object triggers
when the connectivity to the Controller has been
restored after it was lost for at least
'controller-timeout' seconds.";
}
}
}
case controller-connected {
leaf controller-connected {
type empty;
mandatory true;
description
"The controller-connected Event object triggers
when the connectivity to the Controller has been
restored after it was lost for at least
'controller-timeout' seconds.";
}
}
}
}
}
}
}
<CODE ENDS>
}
}
}
}
<CODE ENDS>
This module imports definitions from [RFC6536] and the common LMAP module.
此模块从[RFC6536]和通用LMAP模块导入定义。
<CODE BEGINS> file "ietf-lmap-report@2017-08-08.yang"
module ietf-lmap-report {
<CODE BEGINS> file "ietf-lmap-report@2017-08-08.yang"
module ietf-lmap-report {
yang-version 1.1;
namespace "urn:ietf:params:xml:ns:yang:ietf-lmap-report";
prefix "lmapr";
yang-version 1.1;
namespace "urn:ietf:params:xml:ns:yang:ietf-lmap-report";
prefix "lmapr";
import ietf-yang-types {
prefix yang;
}
import ietf-lmap-common {
prefix lmap;
}
import ietf-yang-types {
prefix yang;
}
import ietf-lmap-common {
prefix lmap;
}
organization "IETF Large-Scale Measurement of Broadband Performance Working Group";
组织“IETF宽带性能大规模测量工作组”；
contact
"WG Web: <https://datatracker.ietf.org/wg/lmap>
WG List: <mailto:lmap@ietf.org>
contact
"WG Web: <https://datatracker.ietf.org/wg/lmap>
WG List: <mailto:lmap@ietf.org>
Editor: Juergen Schoenwaelder
<j.schoenwaelder@jacobs-university.de>
Editor: Juergen Schoenwaelder
<j.schoenwaelder@jacobs-university.de>
Editor: Vaibhav Bajpai
<bajpaiv@in.tum.de>";
Editor: Vaibhav Bajpai
<bajpaiv@in.tum.de>";
description "This module defines a data model for reporting results from Measurement Agents, which are part of a Large-Scale Measurement Platform (LMAP), to result data Collectors. This data model is expected to be implemented by a Collector.";
描述“此模块定义了一个数据模型，用于将测量代理（作为大规模测量平台（LMAP）的一部分）的结果报告给结果数据采集器。此数据模型预计由采集器实现。”；
revision "2017-08-08" {
description
"Initial version";
revision "2017-08-08" {
description
"Initial version";
reference
"RFC 8194: A YANG Data Model for LMAP Measurement Agents";
}
reference
"RFC 8194: A YANG Data Model for LMAP Measurement Agents";
}
rpc report {
description
"The report operation is used by a Measurement Agent to
submit measurement results produced by Measurement Tasks to
a Collector.";
rpc report {
description
"The report operation is used by a Measurement Agent to
submit measurement results produced by Measurement Tasks to
a Collector.";
input {
输入{
leaf date {
type yang:date-and-time;
mandatory true;
description
"The date and time when this result report was sent to
a Collector.";
}
leaf date {
type yang:date-and-time;
mandatory true;
description
"The date and time when this result report was sent to
a Collector.";
}
leaf agent-id {
type yang:uuid;
description
"The agent-id of the agent from which this
report originates.";
}
leaf agent-id {
type yang:uuid;
description
"The agent-id of the agent from which this
report originates.";
}
leaf group-id {
type string;
description
"The group-id of the agent from which this
report originates.";
}
leaf group-id {
type string;
description
"The group-id of the agent from which this
report originates.";
}
leaf measurement-point {
type string;
description
"The measurement-point of the agent from which this
report originates.";
}
leaf measurement-point {
type string;
description
"The measurement-point of the agent from which this
report originates.";
}
list result {
description
"The list of Tasks for which results are reported.";
list result {
description
"The list of Tasks for which results are reported.";
leaf schedule {
type lmap:identifier;
leaf schedule {
type lmap:identifier;
description
"The name of the Schedule that produced the result.";
}
description
"The name of the Schedule that produced the result.";
}
leaf action {
type lmap:identifier;
description
"The name of the Action in the Schedule that produced
the result.";
}
leaf action {
type lmap:identifier;
description
"The name of the Action in the Schedule that produced
the result.";
}
leaf task {
type lmap:identifier;
description
"The name of the Task that produced the result.";
}
leaf task {
type lmap:identifier;
description
"The name of the Task that produced the result.";
}
container parameters {
description
"This container is a placeholder for runtime
parameters defined in Task-specific data models
augmenting the base LMAP report data model.";
container parameters {
description
"This container is a placeholder for runtime
parameters defined in Task-specific data models
augmenting the base LMAP report data model.";
choice extension {
description
"This choice is provided to augment in different
sets of parameters.";
}
}
choice extension {
description
"This choice is provided to augment in different
sets of parameters.";
}
}
uses lmap:options-grouping {
description
"The list of options there were in use when the
measurement was performed. This list must include
both the Task-specific options as well as the
Action-specific options.";
}
uses lmap:options-grouping {
description
"The list of options there were in use when the
measurement was performed. This list must include
both the Task-specific options as well as the
Action-specific options.";
}
leaf-list tag {
type lmap:tag;
description
"A tag contains additional information that is passed
with the result record to the Collector. This is the
joined set of tags defined for the Task object, the
Schedule object, and the Action object. A tag can be
used to carry the Measurement Cycle ID.";
}
leaf-list tag {
type lmap:tag;
description
"A tag contains additional information that is passed
with the result record to the Collector. This is the
joined set of tags defined for the Task object, the
Schedule object, and the Action object. A tag can be
used to carry the Measurement Cycle ID.";
}
leaf event {
type yang:date-and-time;
description
"The date and time of the event that triggered the
Schedule of the Action that produced the reported
result values. The date and time does not include
any added randomization.";
}
leaf event {
type yang:date-and-time;
description
"The date and time of the event that triggered the
Schedule of the Action that produced the reported
result values. The date and time does not include
any added randomization.";
}
leaf start {
type yang:date-and-time;
mandatory true;
description
"The date and time when the Task producing
this result started.";
}
leaf start {
type yang:date-and-time;
mandatory true;
description
"The date and time when the Task producing
this result started.";
}
leaf end {
type yang:date-and-time;
description
"The date and time when the Task producing
this result finished.";
}
leaf end {
type yang:date-and-time;
description
"The date and time when the Task producing
this result finished.";
}
leaf cycle-number {
type lmap:cycle-number;
description
"The optional cycle number is the time closest to
the time reported in the event leaf that is a multiple
of the cycle-interval of the event that triggered the
execution of the Schedule. The value is only present
if the event that triggered the execution of the
Schedule has a defined cycle-interval.";
}
leaf cycle-number {
type lmap:cycle-number;
description
"The optional cycle number is the time closest to
the time reported in the event leaf that is a multiple
of the cycle-interval of the event that triggered the
execution of the Schedule. The value is only present
if the event that triggered the execution of the
Schedule has a defined cycle-interval.";
}
leaf status {
type lmap:status-code;
mandatory true;
description
"The status code returned by the execution of this
Action.";
}
leaf status {
type lmap:status-code;
mandatory true;
description
"The status code returned by the execution of this
Action.";
}
list conflict {
description
"The names of Tasks overlapping with the execution
of the Task that has produced this result.";
list conflict {
description
"The names of Tasks overlapping with the execution
of the Task that has produced this result.";
leaf schedule-name {
type lmap:identifier;
description
"The name of a Schedule that might have impacted
the execution of the Task that has produced this
result.";
}
leaf schedule-name {
type lmap:identifier;
description
"The name of a Schedule that might have impacted
the execution of the Task that has produced this
result.";
}
leaf action-name {
type lmap:identifier;
description
"The name of an Action within the Schedule that
might have impacted the execution of the Task that
has produced this result.";
}
leaf action-name {
type lmap:identifier;
description
"The name of an Action within the Schedule that
might have impacted the execution of the Task that
has produced this result.";
}
leaf task-name {
type lmap:identifier;
description
"The name of the Task executed by an Action within
the Schedule that might have impacted the execution
of the Task that has produced this result.";
}
}
leaf task-name {
type lmap:identifier;
description
"The name of the Task executed by an Action within
the Schedule that might have impacted the execution
of the Task that has produced this result.";
}
}
list table {
description
"A list of result tables.";
list table {
description
"A list of result tables.";
uses lmap:registry-grouping;
使用lmap：注册表分组；
leaf-list column {
type string;
description
"An ordered list of column labels. The order is
determined by the system and must match the order
of the columns in the result rows.";
}
leaf-list column {
type string;
description
"An ordered list of column labels. The order is
determined by the system and must match the order
of the columns in the result rows.";
}
list row {
description
"The rows of a result table.";
list row {
description
"The rows of a result table.";
leaf-list value {
type string;
description
"The value of a cell in the result row.";
}
leaf-list value {
type string;
description
"The value of a cell in the result row.";
}
}
}
}
}
}
}
<CODE ENDS>
}
}
}
}
}
}
<CODE ENDS>
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 Transport Layer Security (TLS) [RFC5246].
本文档中定义的YANG模块旨在通过网络管理协议（如NETCONF[RFC6241]或RESTCONF[RFC8040]）进行访问。最低的NETCONF层是安全传输层，实现安全传输的强制要求是安全Shell（SSH）[RFC6242]。最低的RESTCONF层是HTTPS，实现安全传输的强制要求是传输层安全性（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.
NETCONF访问控制模型[RFC6536]提供了将特定NETCONF或RESTCONF用户的访问限制为所有可用NETCONF或RESTCONF协议操作和内容的预配置子集的方法。
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. These are the subtrees and data nodes and their sensitivity/vulnerability:
此模块中定义了许多可写/可创建/可删除的数据节点（即，默认为config true）。在某些网络环境中，这些数据节点可能被视为敏感或易受攻击。对这些数据节点的写入操作（如编辑配置）如果没有适当的保护，可能会对网络操作产生负面影响。这些是子树和数据节点及其敏感性/漏洞：
/lmap/agent This subtree configures general properties of the Measurement Agent such as its identity, measurement point, or Controller timeout. This subtree should only have write access for the system responsible for configuring the Measurement Agent.
/lmap/agent此子树配置度量代理的常规属性，例如其标识、度量点或控制器超时。此子树应仅对负责配置度量代理的系统具有写访问权限。
/lmap/tasks This subtree configures the Tasks that can be invoked by a Controller. This subtree should only have write access for the system responsible for configuring the Measurement Agent. Care must be taken to not expose Tasks to a Controller that can cause damage to the system or the network.
/lmap/tasks此子树配置可由控制器调用的任务。此子树应仅对负责配置度量代理的系统具有写访问权限。必须注意不要将任务暴露给控制器，以免损坏系统或网络。
/lmap/schedules This subtree is used by a Controller to define the Schedules and Actions that are executed when certain events occur. Unauthorized access can cause unwanted load on the device or network, or it might direct measurement traffic to targets that become victims of an attack.
/lmap/调度控制器使用此子树定义特定事件发生时执行的调度和操作。未经授权的访问可能会在设备或网络上造成不必要的负载，或者可能会将测量流量导向成为攻击受害者的目标。
/lmap/suppressions This subtree is used by a Controller to define Suppressions that can temporarily disable the execution of Schedules or Actions. Unauthorized access can either disable measurements that should normally take place or cause measurements to take place during times when normally no measurements should take place.
/lmap/suppressions控制器使用此子树定义可以临时禁用计划或操作执行的抑制。未经授权的访问可能会禁用通常应进行的测量，或者导致在通常不应进行测量的情况下进行测量。
/lmap/events This subtree is used by a Controller to define events that trigger the execution of Schedules and Actions. Unauthorized access can either disable measurements that should normally take place or cause measurements to take place during times when normally no measurements should take place or at a frequency that is higher than normally expected.
/lmap/events控制器使用此子树定义触发计划和操作执行的事件。未经授权的访问可能会禁用通常应进行的测量，或导致在通常不应进行测量的时间内或以高于正常预期的频率进行测量。
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:
在某些网络环境中，此模块中的某些可读数据节点可能被视为敏感或易受攻击。因此，控制对这些数据节点的读取访问（例如，通过get、get config或通知）非常重要。这些是子树和数据节点及其敏感性/漏洞：
/lmap/agent This subtree provides information about the Measurement Agent. This information may be used to select specific targets for attacks.
/lmap/agent此子树提供有关度量代理的信息。此信息可用于选择攻击的特定目标。
/lmap/capabilities This subtree provides information about the capabilities of the Measurement Agent, including its software version number and the Tasks that it supports. This information may be used to execute targeted attacks against specific implementations.
/lmap/功能此子树提供有关度量代理功能的信息，包括其软件版本号及其支持的任务。此信息可用于对特定实现执行有针对性的攻击。
/lmap/schedules This subtree provides information about the Schedules and their associated Actions executed on the Measurement Agent. This information may be used to check whether attacks against the implementation are effective.
/lmap/计划此子树提供有关计划及其在度量代理上执行的相关操作的信息。此信息可用于检查针对实现的攻击是否有效。
/lmap/suppressions This subtree provides information about the Suppressions that can be active on the Measurement Agent. This information may be used to predict time periods where measurements take place (or do not take place).
/lmap/抑制此子树提供有关测量代理上可激活的抑制的信息。该信息可用于预测测量发生（或不发生）的时间段。
Some of the RPC operations in this YANG module may be considered sensitive or vulnerable in some network environments. It is thus important to control access to these operations. These are the operations and their sensitivity/vulnerability:
在某些网络环境中，此模块中的某些RPC操作可能被视为敏感或易受攻击。因此，控制对这些操作的访问非常重要。这些是操作及其敏感性/脆弱性：
/report The report operation is used to send locally collected measurement results to a remote Collector. Unauthorized access may leak measurement results, including those from passive measurements.
/报告报告操作用于将本地收集的测量结果发送到远程收集器。未经授权的访问可能会泄漏测量结果，包括被动测量的结果。
The data model uses a number of identifiers that are set by the Controller. Implementors may find these identifiers useful for the identification of resources, e.g., to identify objects in a file system providing temporary storage. Since the identifiers used by the YANG data model may allow characters that may be given special interpretation in a specific context, implementations must ensure that identifiers are properly mapped into safe identifiers.
数据模型使用控制器设置的多个标识符。实现者可能会发现这些标识符对于资源的标识很有用，例如，用于标识提供临时存储的文件系统中的对象。由于YANG数据模型使用的标识符可能允许在特定上下文中对字符进行特殊解释，因此实现必须确保标识符正确映射到安全标识符中。
The data model allows specifying options in the form of name/value pairs that are passed to programs. Implementors ought to take care that option names and values are passed literally to programs. In particular, shell expansions that may alter option names and values must not be performed.
数据模型允许以传递给程序的名称/值对的形式指定选项。实现者应该注意将选项名和值直接传递给程序。特别是，不能执行可能改变选项名称和值的shell扩展。
This document registers three URIs in the "IETF XML Registry" [RFC3688]. Following the format in RFC 3688, the following registrations have been made.
本文档在“IETF XML注册表”[RFC3688]中注册了三个URI。按照RFC 3688中的格式，进行了以下注册。
URI: urn:ietf:params:xml:ns:yang:ietf-lmap-common Registrant Contact: The IESG. XML: N/A; the requested URI is an XML namespace.
URI:urn:ietf:params:xml:ns:yang:ietf-lmap共同注册人联系人：IESG。XML：不适用；请求的URI是一个XML命名空间。
URI: urn:ietf:params:xml:ns:yang:ietf-lmap-control Registrant Contact: The IESG. XML: N/A; the requested URI is an XML namespace.
URI:urn:ietf:params:xml:ns:yang:ietf-lmap控制注册人联系人：IESG。XML：不适用；请求的URI是一个XML命名空间。
URI: urn:ietf:params:xml:ns:yang:ietf-lmap-report Registrant Contact: The IESG. XML: N/A; the requested URI is an XML namespace.
URI:urn:ietf:params:xml:ns:yang:ietf-lmap报告注册人联系人：IESG。XML：不适用；请求的URI是一个XML命名空间。
This document registers three YANG modules in the "YANG Module Names" registry [RFC6020].
本文件在“阳模块名称”注册表[RFC6020]中注册了三个阳模块。
Name: ietf-lmap-common
Namespace: urn:ietf:params:xml:ns:yang:ietf-lmap-common
Prefix: lmap
Reference: RFC 8194
Name: ietf-lmap-common
Namespace: urn:ietf:params:xml:ns:yang:ietf-lmap-common
Prefix: lmap
Reference: RFC 8194
Name: ietf-lmap-control
Namespace: urn:ietf:params:xml:ns:yang:ietf-lmap-control
Prefix: lmapc
Reference: RFC 8194
Name: ietf-lmap-control
Namespace: urn:ietf:params:xml:ns:yang:ietf-lmap-control
Prefix: lmapc
Reference: RFC 8194
Name: ietf-lmap-report
Namespace: urn:ietf:params:xml:ns:yang:ietf-lmap-report
Prefix: lmapr
Reference: RFC 8194
Name: ietf-lmap-report
Namespace: urn:ietf:params:xml:ns:yang:ietf-lmap-report
Prefix: lmapr
Reference: RFC 8194
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, DOI 10.17487/RFC2119, March 1997, <https://www.rfc-editor.org/info/rfc2119>.
[RFC2119]Bradner，S.，“RFC中用于表示需求水平的关键词”，BCP 14，RFC 2119，DOI 10.17487/RFC2119，1997年3月<https://www.rfc-editor.org/info/rfc2119>.
[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>.
[RFC5246]Dierks，T.和E.Rescorla，“传输层安全（TLS）协议版本1.2”，RFC 5246，DOI 10.17487/RFC5246，2008年8月<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>.
[RFC6020]Bjorklund，M.，Ed.“YANG-网络配置协议的数据建模语言（NETCONF）”，RFC 6020，DOI 10.17487/RFC6020，2010年10月<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>.
[RFC6241]Enns，R.，Ed.，Bjorklund，M.，Ed.，Schoenwaeld，J.，Ed.，和A.Bierman，Ed.，“网络配置协议（NETCONF）”，RFC 6241，DOI 10.17487/RFC6241，2011年6月<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>.
[RFC6242]Wasserman，M.“在安全外壳上使用NETCONF协议（SSH）”，RFC 6242，DOI 10.17487/RFC6242，2011年6月<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>.
[RFC6536]Bierman，A.和M.Bjorklund，“网络配置协议（NETCONF）访问控制模型”，RFC 6536，DOI 10.17487/RFC6536，2012年3月<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>.
[RFC6991]Schoenwaeld，J.，Ed.，“常见杨数据类型”，RFC 6991，DOI 10.17487/RFC69911913年7月<https://www.rfc-editor.org/info/rfc6991>.
[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>.
[RFC7950]Bjorklund，M.，Ed.“YANG 1.1数据建模语言”，RFC 7950，DOI 10.17487/RFC7950，2016年8月<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>.
[RFC8040]Bierman，A.，Bjorklund，M.，和K.Watsen，“RESTCONF协议”，RFC 8040，DOI 10.17487/RFC8040，2017年1月<https://www.rfc-editor.org/info/rfc8040>.
[RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, May 2017, <https://www.rfc-editor.org/info/rfc8174>.
[RFC8174]Leiba，B.，“RFC 2119关键词中大写与小写的歧义”，BCP 14，RFC 8174，DOI 10.17487/RFC8174，2017年5月<https://www.rfc-editor.org/info/rfc8174>.
[RFC8193] Burbridge, T., Eardley, P., Bagnulo, M., and J. Schoenwaelder, "Information Model for Large-Scale Measurement Platforms (LMAPs)", DOI 10.17487/RFC8193, RFC 8193, August 2017, <http://www.rfc-editor.org/info/rfc8193>.
[RFC8193]Burbridge，T.，Eardley，P.，Bagnulo，M.，和J.Schoenwaeld，“大型测量平台（LMAP）的信息模型”，DOI 10.17487/RFC8193，RFC8193，2017年8月<http://www.rfc-editor.org/info/rfc8193>.
[ISO-8601] International Organization for Standardization, "Data elements and interchange formats -- Information interchange -- Representation of dates and times", ISO Standard 8601:2004, December 2004.
[ISO-8601]国际标准化组织，“数据元素和交换格式——信息交换——日期和时间的表示”，ISO标准8601:2004，2004年12月。
[NETCONF-CLIENT-SERVER] Watsen, K., Wu, G., and J. Schoenwaelder, "NETCONF Client and Server Models", Work in Progress, draft-ietf-netconf-netconf-client-server-04, July 2017.
[NETCONF-CLIENT-SERVER]Watsen，K.，Wu，G.，和J.Schoenwaeld，“NETCONF客户机和服务器模型”，正在进行的工作，草稿-ietf-NETCONF-NETCONF-CLIENT-SERVER-042017年7月。
[RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688, DOI 10.17487/RFC3688, January 2004, <https://www.rfc-editor.org/info/rfc3688>.
[RFC3688]Mealling，M.，“IETF XML注册表”，BCP 81，RFC 3688，DOI 10.17487/RFC3688，2004年1月<https://www.rfc-editor.org/info/rfc3688>.
[RFC5424] Gerhards, R., "The Syslog Protocol", RFC 5424, DOI 10.17487/RFC5424, March 2009, <https://www.rfc-editor.org/info/rfc5424>.
[RFC5424]Gerhards，R.，“系统日志协议”，RFC 5424DOI 10.17487/RFC54242009年3月<https://www.rfc-editor.org/info/rfc5424>.
[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>.
[RFC7223]Bjorklund，M.，“用于接口管理的YANG数据模型”，RFC 7223，DOI 10.17487/RFC7223，2014年5月<https://www.rfc-editor.org/info/rfc7223>.
[RFC7317] Bierman, A. and M. Bjorklund, "A YANG Data Model for System Management", RFC 7317, DOI 10.17487/RFC7317, August 2014, <https://www.rfc-editor.org/info/rfc7317>.
[RFC7317]Bierman，A.和M.Bjorklund，“系统管理的杨数据模型”，RFC 7317，DOI 10.17487/RFC73172014年8月<https://www.rfc-editor.org/info/rfc7317>.
[RFC7398] Bagnulo, M., Burbridge, T., Crawford, S., Eardley, P., and A. Morton, "A Reference Path and Measurement Points for Large-Scale Measurement of Broadband Performance", RFC 7398, DOI 10.17487/RFC7398, February 2015, <https://www.rfc-editor.org/info/rfc7398>.
[RFC7398]Bagnulo，M.，Burbridge，T.，Crawford，S.，Eardley，P.，和A.Morton，“宽带性能大规模测量的参考路径和测量点”，RFC 7398，DOI 10.17487/RFC7398，2015年2月<https://www.rfc-editor.org/info/rfc7398>.
[RFC7594] Eardley, P., Morton, A., Bagnulo, M., Burbridge, T., Aitken, P., and A. Akhter, "A Framework for Large-Scale Measurement of Broadband Performance (LMAP)", RFC 7594, DOI 10.17487/RFC7594, September 2015, <https://www.rfc-editor.org/info/rfc7594>.
[RFC7594]Eardley，P.，Morton，A.，Bagnulo，M.，Burbridge，T.，Aitken，P.，和A.Akhter，“宽带性能的大规模测量框架（LMAP）”，RFC 7594，DOI 10.17487/RFC7594，2015年9月<https://www.rfc-editor.org/info/rfc7594>.
[W3C.REC-xml-20081126] Bray, T., Paoli, J., Sperberg-McQueen, M., Maler, E., and F. Yergeau, "Extensible Markup Language (XML) 1.0 (Fifth Edition)", World Wide Web Consortium Recommendation REC-xml-20081126, November 2008, <http://www.w3.org/TR/2008/REC-xml-20081126>.
[W3C.REC-xml-20081126]Bray，T.，Paoli，J.，Sperberg McQueen，M.，Maler，E.，和F.Yergeau，“可扩展标记语言（xml）1.0（第五版）”，万维网联盟建议REC-xml-20081126，2008年11月<http://www.w3.org/TR/2008/REC-xml-20081126>.
[YANG-HARDWARE] Bierman, A., Bjorklund, M., Dong, J., and D. Romascanu, "A YANG Data Model for Hardware Management", Work in Progress, draft-ietf-netmod-entity-03, March 2017.
[YANG-HARDWARE]Bierman，A.，Bjorklund，M.，Dong，J.，和D.Romascanu，“硬件管理的YANG数据模型”，正在进行的工作，草稿-ietf-netmod-entity-032017年3月。
Sometimes Tasks may require complicated parameters that cannot easily be fit into options, i.e., a list of name/value pairs. In such a situation, it is possible to augment the ietf-lmap-control.yang and ietf-lmap-report.yang data models with definitions for more complex parameters. The following example module demonstrates this idea using the parameters of UDP latency metrics as an example (although UDP latency metric parameters do not really need such an extension module).
有时，任务可能需要复杂的参数，这些参数很难放入选项中，即名称/值对列表。在这种情况下，可以使用更复杂参数的定义来扩充ietf-lmap-control.yang和ietf-lmap-report.yang数据模型。下面的示例模块以UDP延迟度量的参数为例演示了这一思想（尽管UDP延迟度量参数并不真正需要这样的扩展模块）。
module example-ietf-ippm-udp-latency {
模块示例ietf ippm udp延迟{
namespace "urn:example:ietf-ippm-udp-latency";
prefix "ippm-udp-latency";
namespace "urn:example:ietf-ippm-udp-latency";
prefix "ippm-udp-latency";
import ietf-inet-types {
prefix inet;
}
import ietf-lmap-control {
prefix "lmapc";
}
import ietf-lmap-report {
prefix "lmapr";
}
import ietf-inet-types {
prefix inet;
}
import ietf-lmap-control {
prefix "lmapc";
}
import ietf-lmap-report {
prefix "lmapr";
}
grouping ippm-udp-latency-parameter-grouping {
leaf src-ip {
type inet:ip-address;
description
"The source IP address of the UDP measurement traffic.";
}
grouping ippm-udp-latency-parameter-grouping {
leaf src-ip {
type inet:ip-address;
description
"The source IP address of the UDP measurement traffic.";
}
leaf src-port {
type inet:port-number;
description
"The source port number of the UDP measurement traffic.";
}
leaf src-port {
type inet:port-number;
description
"The source port number of the UDP measurement traffic.";
}
leaf dst-ip {
type inet:ip-address;
description
"The destination IP address of the UDP measurement traffic.";
}
leaf dst-ip {
type inet:ip-address;
description
"The destination IP address of the UDP measurement traffic.";
}
leaf dst-port {
type inet:port-number;
description
"The destination port number of the UDP measurement traffic.";
}
leaf dst-port {
type inet:port-number;
description
"The destination port number of the UDP measurement traffic.";
}
leaf poisson-lambda {
type decimal64 {
fraction-digits 4;
}
units "seconds";
default 1.0000;
description
"The average interval for the poisson stream with a resolution
of 0.0001 seconds (0.1 ms).";
}
leaf poisson-lambda {
type decimal64 {
fraction-digits 4;
}
units "seconds";
default 1.0000;
description
"The average interval for the poisson stream with a resolution
of 0.0001 seconds (0.1 ms).";
}
leaf poisson-limit {
type decimal64 {
fraction-digits 4;
}
units "seconds";
default 30.0000;
description
"The upper limit on the poisson distribution with a resolution
of 0.0001 seconds (0.1 ms).";
}
}
leaf poisson-limit {
type decimal64 {
fraction-digits 4;
}
units "seconds";
default 30.0000;
description
"The upper limit on the poisson distribution with a resolution
of 0.0001 seconds (0.1 ms).";
}
}
augment "/lmapc:lmap/lmapc:schedules/lmapc:schedule/lmapc:action"
+ "/lmapc:parameters/lmapc:extension" {
description
"This augmentation adds parameters specific to IP Performance
Metrics (IPPM) and UDP latency metrics to Actions.";
augment "/lmapc:lmap/lmapc:schedules/lmapc:schedule/lmapc:action"
+ "/lmapc:parameters/lmapc:extension" {
description
"This augmentation adds parameters specific to IP Performance
Metrics (IPPM) and UDP latency metrics to Actions.";
case "ietf-ippm-udp-latency" {
uses ippm-udp-latency-parameter-grouping;
}
}
case "ietf-ippm-udp-latency" {
uses ippm-udp-latency-parameter-grouping;
}
}
augment "/lmapr:report/lmapr:input/lmapr:result"
+ "/lmapr:parameters/lmapr:extension" {
description
"This augmentation adds parameters specific to IPPM and
UDP latency metrics to reports.";
augment "/lmapr:report/lmapr:input/lmapr:result"
+ "/lmapr:parameters/lmapr:extension" {
description
"This augmentation adds parameters specific to IPPM and
UDP latency metrics to reports.";
case "ietf-ippm-udp-latency" {
uses ippm-udp-latency-parameter-grouping;
}
}
case "ietf-ippm-udp-latency" {
uses ippm-udp-latency-parameter-grouping;
}
}
}
}
The configuration below is in XML [W3C.REC-xml-20081126].
下面的配置是XML格式的[W3C.REC-XML-20081126]。
<config xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
<lmap xmlns="urn:ietf:params:xml:ns:yang:ietf-lmap-control">
<config xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
<lmap xmlns="urn:ietf:params:xml:ns:yang:ietf-lmap-control">
<agent>
<agent-id>550e8400-e29b-41d4-a716-446655440000</agent-id>
<report-agent-id>true</report-agent-id>
</agent>
<agent>
<agent-id>550e8400-e29b-41d4-a716-446655440000</agent-id>
<report-agent-id>true</report-agent-id>
</agent>
<schedules>
<!-- The Schedule S1 first updates a list of ping targets
and subsequently sends a ping to all targets. -->
<schedule>
<name>S1</name>
<start>E1</start>
<execution-mode>sequential</execution-mode>
<action>
<name>A1</name>
<task>update-ping-targets</task>
</action>
<action>
<name>A2</name>
<task>ping-all-targets</task>
<destination>S3</destination>
</action>
<suppression-tag>measurement:ping</suppression-tag>
</schedule>
<!-- The Schedule S2 executes two traceroutes concurrently. -->
<schedule>
<name>S2</name>
<start>E1</start>
<execution-mode>parallel</execution-mode>
<schedules>
<!-- The Schedule S1 first updates a list of ping targets
and subsequently sends a ping to all targets. -->
<schedule>
<name>S1</name>
<start>E1</start>
<execution-mode>sequential</execution-mode>
<action>
<name>A1</name>
<task>update-ping-targets</task>
</action>
<action>
<name>A2</name>
<task>ping-all-targets</task>
<destination>S3</destination>
</action>
<suppression-tag>measurement:ping</suppression-tag>
</schedule>
<!-- The Schedule S2 executes two traceroutes concurrently. -->
<schedule>
<name>S2</name>
<start>E1</start>
<execution-mode>parallel</execution-mode>
<action>
<name>A1</name>
<task>traceroute</task>
<option>
<id>target</id>
<name>target</name>
<value>2001:db8::1</value>
</option>
<destination>S3</destination>
</action>
<action>
<name>A2</name>
<task>traceroute</task>
<option>
<id>target</id>
<name>target</name>
<value>2001:db8::2</value>
</option>
<destination>S3</destination>
</action>
<suppression-tag>measurement:traceroute</suppression-tag>
</schedule>
<!-- The Schedule S3 sends measurement data to a Collector. -->
<schedule>
<name>S3</name>
<start>E2</start>
<action>
<name>A1</name>
<task>report</task>
<option>
<id>collector</id>
<name>collector</name>
<value>https://collector.example.com/</value>
</option>
</action>
</schedule>
</schedules>
<action>
<name>A1</name>
<task>traceroute</task>
<option>
<id>target</id>
<name>target</name>
<value>2001:db8::1</value>
</option>
<destination>S3</destination>
</action>
<action>
<name>A2</name>
<task>traceroute</task>
<option>
<id>target</id>
<name>target</name>
<value>2001:db8::2</value>
</option>
<destination>S3</destination>
</action>
<suppression-tag>measurement:traceroute</suppression-tag>
</schedule>
<!-- The Schedule S3 sends measurement data to a Collector. -->
<schedule>
<name>S3</name>
<start>E2</start>
<action>
<name>A1</name>
<task>report</task>
<option>
<id>collector</id>
<name>collector</name>
<value>https://collector.example.com/</value>
</option>
</action>
</schedule>
</schedules>
<suppressions>
<!-- Stop all measurements if we got orphaned. -->
<suppression>
<name>orphaned</name>
<start>controller-lost</start>
<end>controller-connected</end>
<match>measurement:*</match>
</suppression>
</suppressions>
<suppressions>
<!-- Stop all measurements if we got orphaned. -->
<suppression>
<name>orphaned</name>
<start>controller-lost</start>
<end>controller-connected</end>
<match>measurement:*</match>
</suppression>
</suppressions>
<tasks>
<!-- configuration of an update-ping-targets task -->
<task>
<name>update-ping-targets</name>
<program>fping-update-targets</program>
</task>
<!-- configuration of a ping-all-targets task -->
<task>
<name>ping-all-targets</name>
<program>fping</program>
</task>
<!-- configuration of a traceroute task -->
<task>
<name>traceroute</name>
<program>mtr</program>
<option>
<id>csv</id>
<name>--csv</name>
</option>
</task>
<!-- configuration of a reporter task -->
<task>
<name>report</name>
<program>lmap-report</program>
</task>
<tasks>
<!-- configuration of an update-ping-targets task -->
<task>
<name>update-ping-targets</name>
<program>fping-update-targets</program>
</task>
<!-- configuration of a ping-all-targets task -->
<task>
<name>ping-all-targets</name>
<program>fping</program>
</task>
<!-- configuration of a traceroute task -->
<task>
<name>traceroute</name>
<program>mtr</program>
<option>
<id>csv</id>
<name>--csv</name>
</option>
</task>
<!-- configuration of a reporter task -->
<task>
<name>report</name>
<program>lmap-report</program>
</task>
<task>
<name>ippm-udp-latency-client</name>
<program>ippm-udp-latency</program>
<function>
<uri>urn:example:tbd</uri>
<role>client</role>
</function>
<tag>active</tag>
</task>
</tasks>
<task>
<name>ippm-udp-latency-client</name>
<program>ippm-udp-latency</program>
<function>
<uri>urn:example:tbd</uri>
<role>client</role>
</function>
<tag>active</tag>
</task>
</tasks>
<events>
<!-- The event E1 triggers every hour during September 2016
with a random spread of one minute. -->
<event>
<name>E1</name>
<random-spread>60</random-spread> <!-- seconds -->
<periodic>
<interval>3600000</interval>
<start>2016-09-01T00:00:00+00:00</start>
<end>2016-11-01T00:00:00+00:00</end>
</periodic>
<events>
<!-- The event E1 triggers every hour during September 2016
with a random spread of one minute. -->
<event>
<name>E1</name>
<random-spread>60</random-spread> <!-- seconds -->
<periodic>
<interval>3600000</interval>
<start>2016-09-01T00:00:00+00:00</start>
<end>2016-11-01T00:00:00+00:00</end>
</periodic>
</event>
<!-- The event E2 triggers on Mondays at 4am UTC -->
<event>
<name>E2</name>
<calendar>
<month>*</month>
<day-of-week>monday</day-of-week>
<day-of-month>*</day-of-month>
<hour>4</hour>
<minute>0</minute>
<second>0</second>
<timezone-offset>+00:00</timezone-offset>
</calendar>
</event>
<!-- The event controller-lost triggers when we lost
connectivity with the Controller. -->
<event>
<name>controller-lost</name>
<controller-lost/>
</event>
<!-- The event contoller-connected triggers when we
established or re-established connectivity with
the Controller. -->
<event>
<name>controller-connected</name>
<controller-connected/>
</event>
</events>
</lmap>
</config>
</event>
<!-- The event E2 triggers on Mondays at 4am UTC -->
<event>
<name>E2</name>
<calendar>
<month>*</month>
<day-of-week>monday</day-of-week>
<day-of-month>*</day-of-month>
<hour>4</hour>
<minute>0</minute>
<second>0</second>
<timezone-offset>+00:00</timezone-offset>
</calendar>
</event>
<!-- The event controller-lost triggers when we lost
connectivity with the Controller. -->
<event>
<name>controller-lost</name>
<controller-lost/>
</event>
<!-- The event contoller-connected triggers when we
established or re-established connectivity with
the Controller. -->
<event>
<name>controller-connected</name>
<controller-connected/>
</event>
</events>
</lmap>
</config>
The report below is in XML [W3C.REC-xml-20081126].
下面的报告是XML格式的[W3C.REC-XML-20081126]。
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0"
message-id="1">
<report xmlns="urn:ietf:params:xml:ns:yang:ietf-lmap-report">
<date>2015-10-28T13:27:42+02:00</date>
<agent-id>550e8400-e29b-41d4-a716-446655440000</agent-id>
<result>
<schedule>S1</schedule>
<action>A1</action>
<task>update-ping-targets</task>
<start>2016-03-21T10:48:55+01:00</start>
<end>2016-03-21T10:48:57+01:00</end>
<status>0</status>
</result>
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0"
message-id="1">
<report xmlns="urn:ietf:params:xml:ns:yang:ietf-lmap-report">
<date>2015-10-28T13:27:42+02:00</date>
<agent-id>550e8400-e29b-41d4-a716-446655440000</agent-id>
<result>
<schedule>S1</schedule>
<action>A1</action>
<task>update-ping-targets</task>
<start>2016-03-21T10:48:55+01:00</start>
<end>2016-03-21T10:48:57+01:00</end>
<status>0</status>
</result>
<result>
<schedule>S1</schedule>
<action>A2</action>
<task>ping-all-targets</task>
<start>2016-03-21T10:48:55+01:00</start>
<end>2016-03-21T10:48:57+01:00</end>
<status>0</status>
<table>
<column>target</column>
<column>rtt</column>
<row>
<value>2001:db8::1</value>
<value>42</value>
</row>
<row>
<value>2001:db8::2</value>
<value>24</value>
</row>
</table>
</result>
<result>
<schedule>S2</schedule>
<action>A1</action>
<task>traceroute</task>
<option>
<id>target</id>
<name>target</name>
<value>2001:db8::1</value>
</option>
<option>
<id>csv</id>
<name>--csv</name>
</option>
<start>2016-03-21T10:48:55+01:00</start>
<end>2016-03-21T10:48:57+01:00</end>
<status>1</status>
<table>
<column>hop</column>
<column>ip</column>
<column>rtt</column>
<row>
<value>1</value>
<value>2001:638:709:5::1</value>
<value>10.5</value>
</row>
<row>
<value>2</value>
<value>?</value>
<result>
<schedule>S1</schedule>
<action>A2</action>
<task>ping-all-targets</task>
<start>2016-03-21T10:48:55+01:00</start>
<end>2016-03-21T10:48:57+01:00</end>
<status>0</status>
<table>
<column>target</column>
<column>rtt</column>
<row>
<value>2001:db8::1</value>
<value>42</value>
</row>
<row>
<value>2001:db8::2</value>
<value>24</value>
</row>
</table>
</result>
<result>
<schedule>S2</schedule>
<action>A1</action>
<task>traceroute</task>
<option>
<id>target</id>
<name>target</name>
<value>2001:db8::1</value>
</option>
<option>
<id>csv</id>
<name>--csv</name>
</option>
<start>2016-03-21T10:48:55+01:00</start>
<end>2016-03-21T10:48:57+01:00</end>
<status>1</status>
<table>
<column>hop</column>
<column>ip</column>
<column>rtt</column>
<row>
<value>1</value>
<value>2001:638:709:5::1</value>
<value>10.5</value>
</row>
<row>
<value>2</value>
<value>?</value>
<value></value>
</row>
</table>
</result>
<result>
<schedule>S2</schedule>
<action>A2</action>
<task>traceroute</task>
<option>
<id>target</id>
<name>target</name>
<value>2001:db8::2</value>
</option>
<option>
<id>csv</id>
<name>--csv</name>
</option>
<start>2016-03-21T10:48:55+01:00</start>
<end>2016-03-21T10:48:57+01:00</end>
<status>1</status>
<table>
<column>hop</column>
<column>ip</column>
<column>rtt</column>
<row>
<value>1</value>
<value>2001:638:709:5::1</value>
<value>11.8</value>
</row>
<row>
<value>2</value>
<value>?</value>
<value></value>
</row>
</table>
</result>
</report>
</rpc>
<value></value>
</row>
</table>
</result>
<result>
<schedule>S2</schedule>
<action>A2</action>
<task>traceroute</task>
<option>
<id>target</id>
<name>target</name>
<value>2001:db8::2</value>
</option>
<option>
<id>csv</id>
<name>--csv</name>
</option>
<start>2016-03-21T10:48:55+01:00</start>
<end>2016-03-21T10:48:57+01:00</end>
<status>1</status>
<table>
<column>hop</column>
<column>ip</column>
<column>rtt</column>
<row>
<value>1</value>
<value>2001:638:709:5::1</value>
<value>11.8</value>
</row>
<row>
<value>2</value>
<value>?</value>
<value></value>
</row>
</table>
</result>
</report>
</rpc>
Acknowledgements
致谢
Several people contributed to this specification by reviewing early draft versions and actively participating in the LMAP Working Group (apologies to those unintentionally omitted): Marcelo Bagnulo, Martin Bjorklund, Trevor Burbridge, Timothy Carey, Alissa Cooper, Philip Eardley, Al Morton, Dan Romascanu, Andrea Soppera, Barbara Stark, and Qin Wu.
一些人通过审查早期草案版本并积极参与LMAP工作组（对无意遗漏的人表示歉意）对此规范做出了贡献：Marcelo Bagnulo、Martin Bjorklund、Trevor Burbridge、Timothy Carey、Alissa Cooper、Philip Eardley、Al Morton、Dan Romascanu、Andrea Soppera、Barbara Stark和秦武。
Juergen Schoenwaelder and Vaibhav Bajpai worked in part on the Leone research project, which received funding from the European Union Seventh Framework Programme [FP7/2007-2013] under grant agreement number 317647.
Juergen Schoenwaeld和Vaibhav Bajpai参与了塞拉利昂研究项目，该项目获得了欧盟第七框架计划[FP7/2007-2013]的资助，资助协议编号为317647。
Juergen Schoenwaelder and Vaibhav Bajpai were partly funded by Flamingo, a Network of Excellence project (ICT-318488) supported by the European Commission under its Seventh Framework Programme.
Juergen Schoenwaeld和Vaibhav Bajpai的部分资金来自Flamingo，这是一个卓越网络项目（ICT-318488），由欧盟委员会在其第七个框架计划下支持。
Authors' Addresses
作者地址
Juergen Schoenwaelder Jacobs University Bremen
不莱梅大学
Email: j.schoenwaelder@jacobs-university.de
Email: j.schoenwaelder@jacobs-university.de
Vaibhav Bajpai Technical University of Munich
慕尼黑工业大学
Email: bajpaiv@in.tum.de
Email: bajpaiv@in.tum.de