draft-ietf-lmap-yang-11.txt   draft-ietf-lmap-yang-12.txt 
Network Working Group J. Schoenwaelder Network Working Group J. Schoenwaelder
Internet-Draft V. Bajpai Internet-Draft V. Bajpai
Intended status: Standards Track Jacobs University Bremen Intended status: Standards Track Jacobs University Bremen
Expires: August 26, 2017 February 22, 2017 Expires: October 23, 2017 April 21, 2017
A YANG Data Model for LMAP Measurement Agents A YANG Data Model for LMAP Measurement Agents
draft-ietf-lmap-yang-11.txt draft-ietf-lmap-yang-12.txt
Abstract Abstract
This document defines a data model for Large-Scale Measurement This document defines a data model for Large-Scale Measurement
Platforms (LMAP). The data model is defined using the YANG data Platforms (LMAP). The data model is defined using the YANG data
modeling language. modeling language.
Status of This Memo Status of This Memo
This Internet-Draft is submitted in full conformance with the This Internet-Draft is submitted in full conformance with the
skipping to change at page 1, line 32 skipping to change at page 1, line 32
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on August 26, 2017. This Internet-Draft will expire on October 23, 2017.
Copyright Notice Copyright Notice
Copyright (c) 2017 IETF Trust and the persons identified as the Copyright (c) 2017 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
skipping to change at page 2, line 22 skipping to change at page 2, line 22
4. YANG Modules . . . . . . . . . . . . . . . . . . . . . . . . 10 4. YANG Modules . . . . . . . . . . . . . . . . . . . . . . . . 10
4.1. LMAP Common YANG Module . . . . . . . . . . . . . . . . . 10 4.1. LMAP Common YANG Module . . . . . . . . . . . . . . . . . 10
4.2. LMAP Control YANG Module . . . . . . . . . . . . . . . . 18 4.2. LMAP Control YANG Module . . . . . . . . . . . . . . . . 18
4.3. LMAP Report YANG Module . . . . . . . . . . . . . . . . . 39 4.3. LMAP Report YANG Module . . . . . . . . . . . . . . . . . 39
5. Security Considerations . . . . . . . . . . . . . . . . . . . 44 5. Security Considerations . . . . . . . . . . . . . . . . . . . 44
6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 46 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 46
7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 47 7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 47
8. References . . . . . . . . . . . . . . . . . . . . . . . . . 48 8. References . . . . . . . . . . . . . . . . . . . . . . . . . 48
8.1. Normative References . . . . . . . . . . . . . . . . . . 48 8.1. Normative References . . . . . . . . . . . . . . . . . . 48
8.2. Informative References . . . . . . . . . . . . . . . . . 48 8.2. Informative References . . . . . . . . . . . . . . . . . 48
Appendix A. Example Parameter Extension Module . . . . . . . . . 49 Appendix A. Example Parameter Extension Module . . . . . . . . . 50
Appendix B. Example Configuration . . . . . . . . . . . . . . . 52 Appendix B. Example Configuration . . . . . . . . . . . . . . . 52
Appendix C. Example Report . . . . . . . . . . . . . . . . . . . 55 Appendix C. Example Report . . . . . . . . . . . . . . . . . . . 55
Appendix D. Change History . . . . . . . . . . . . . . . . . . . 57 Appendix D. Change History . . . . . . . . . . . . . . . . . . . 57
D.1. Non-editorial Changes since -07 . . . . . . . . . . . . . 57 D.1. Non-editorial Changes since -07 . . . . . . . . . . . . . 57
D.2. Non-editorial Changes since -06 . . . . . . . . . . . . . 57 D.2. Non-editorial Changes since -06 . . . . . . . . . . . . . 58
D.3. Non-editorial Changes since -05 . . . . . . . . . . . . . 58 D.3. Non-editorial Changes since -05 . . . . . . . . . . . . . 58
D.4. Non-editorial Changes since -04 . . . . . . . . . . . . . 58 D.4. Non-editorial Changes since -04 . . . . . . . . . . . . . 58
D.5. Non-editorial Changes since -03 . . . . . . . . . . . . . 59 D.5. Non-editorial Changes since -03 . . . . . . . . . . . . . 59
D.6. Non-editorial Changes since -02 . . . . . . . . . . . . . 59 D.6. Non-editorial Changes since -02 . . . . . . . . . . . . . 59
D.7. Non-editorial Changes since -01 . . . . . . . . . . . . . 59 D.7. Non-editorial Changes since -01 . . . . . . . . . . . . . 59
D.8. Non-editorial Changes since -00 . . . . . . . . . . . . . 60 D.8. Non-editorial Changes since -00 . . . . . . . . . . . . . 60
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 60 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 60
1. Introduction 1. Introduction
This document defines a data model for Large-Scale Measurement This document defines a data model for Large-Scale Measurement
Platforms (LMAP) [RFC7594]. The data model is defined using the YANG Platforms (LMAP) [RFC7594]. The data model is defined using the YANG
[RFC7950] data modeling language. It aims to be consistent with the [RFC7950] data modeling language. It is based on the LMAP
LMAP Information Model [I-D.ietf-lmap-information-model]. Information Model [I-D.ietf-lmap-information-model].
1.1. Terminology 1.1. Terminology
This document uses the LMAP terminology defined in [RFC7594]. This document uses the LMAP terminology defined in [RFC7594].
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in [RFC2119]. document are to be interpreted as described in [RFC2119].
1.2. Tree Diagrams 1.2. Tree Diagrams
A simplified graphical representation of the data model is used in A simplified graphical representation of the data model is used in
this document. The meaning of the symbols in these diagrams is as this document. The meaning of the symbols in these diagrams is as
follows: follows:
o Brackets "[" and "]" enclose list keys. o Brackets "[" and "]" enclose list keys.
o Abbreviations before data node names: "rw" means configuration o Abbreviations before data node names: "rw" means configuration
(read-write), "ro" means state data (read-only), and "w" means RPC (read-write), "ro" means state data (read-only), and "w" means RPC
input date (write-only). input data (write-only).
o Symbols after data node names: "?" means an optional node, "!" o Symbols after data node names: "?" means an optional node, "!"
means a presence container, and "*" denotes a list and leaf-list. means a presence container, and "*" denotes a list and leaf-list.
o Parentheses enclose choice and case nodes, and case nodes are also o Parentheses enclose choice and case nodes, and case nodes are also
marked with a colon (":"). marked with a colon (":").
o Ellipsis ("...") stands for contents of subtrees that are not o Ellipsis ("...") stands for contents of subtrees that are not
shown. shown.
skipping to change at page 4, line 11 skipping to change at page 4, line 11
Measurement Agents, which implement ietf-lmap-common.yang and ietf- Measurement Agents, which implement ietf-lmap-common.yang and ietf-
lmap-control.yang as servers. A Measurement Agent, implementing lmap-control.yang as servers. A Measurement Agent, implementing
ietf-lmap-common.yang and ietf-lmap-report.yang, will send results to ietf-lmap-common.yang and ietf-lmap-report.yang, will send results to
a Collector, which implements ietf-lmap-common.yang and ietf-lmap- a Collector, which implements ietf-lmap-common.yang and ietf-lmap-
report.yang as a server. report.yang as a server.
+------------------------+ +------------------------+
| LMAP Controller | | LMAP Controller |
| | | |
| Client: | | Client: |
| ietf-lmap-comman.yang | | ietf-lmap-common.yang |
| ietf-lmap-control.yang | | ietf-lmap-control.yang |
+------------------------+ +------------------------+
+------------------------+ | +------------------------+ |
| LMAP Measurement Agent | | | LMAP Measurement Agent | |
| | <- request | | | <- request |
| Server: |<---------------------' | Server: |<---------------------'
| ietf-lmap-comman.yang | response -> | ietf-lmap-common.yang | response ->
| ietf-lmap-control.yang | | ietf-lmap-control.yang |
| | | |
| | request -> | | request ->
| Client: |----------------------. | Client: |----------------------.
| ietf-lmap-comman.yang | <- response | | ietf-lmap-common.yang | <- response |
| ietf-lmap-report.yang | | | ietf-lmap-report.yang | |
+------------------------+ v +------------------------+ v
+------------------------+ +------------------------+
| LMAP Collector | | LMAP Collector |
| | | |
| Server: | | Server: |
| ietf-lmap-comman.yang | | ietf-lmap-common.yang |
| ietf-lmap-report.yang | | ietf-lmap-report.yang |
+------------------------+ +------------------------+
Figure 1: LMAP Controller, Measurement Agents, and Collector and the Figure 1: LMAP Controller, Measurement Agents, and Collector and the
YANG modules they implement as client or server YANG modules they implement as client or server
The tree diagram below shows the structure of the control data model. The tree diagram below shows the structure of the control data model.
module: ietf-lmap-control module: ietf-lmap-control
+--rw lmap +--rw lmap
skipping to change at page 8, line 45 skipping to change at page 8, line 45
+---w function* [uri] +---w function* [uri]
| +---w uri inet:uri | +---w uri inet:uri
| +---w role* string | +---w role* string
+---w column* string +---w column* string
+---w row* +---w row*
+---w value* string +---w value* string
3. Relationship to the Information Model 3. Relationship to the Information Model
The LMAP information model [I-D.ietf-lmap-information-model] is The LMAP information model [I-D.ietf-lmap-information-model] is
devided into six sections. They are mapped into the YANG data model divided into six aspects. They are mapped into the YANG data model
as explained below: as explained below:
o Pre-Configuration Information: This is not modeled explicitly o Pre-Configuration Information: This is not modeled explicitly
since bootstrapping information is outside the scope of this data since bootstrapping information is outside the scope of this data
model. Implementations may use some of the Configuration model. Implementations may use some of the Configuration
Information also for bootstrapping purposes. Information also for bootstrapping purposes.
o Configuration Information: This is modeled in the /lmap/agent o Configuration Information: This is modeled in the /lmap/agent
subtree, the /lmap/schedules subtree, and the /lmap/tasks subtree subtree, the /lmap/schedules subtree, and the /lmap/tasks subtree
described below. Some items have been left out because they are described below. Some items have been left out because they are
expected to be dealt with by the underlying protocol. expected to be dealt with by the underlying protocol.
o Instruction Information: This is modeled in the /lmap/suppressions o Instruction Information: This is modeled in the /lmap/suppressions
subtree, the /lmap/schedules subtree, and the /lmap/tasks subtree subtree, the /lmap/schedules subtree, and the /lmap/tasks subtree
described below. described below.
o Logging Information: Some of the logging information, in o Logging Information: Some of the logging information, in
particular 'success/failure/warning messages in response to particular 'success/failure/warning messages in response to
information updates from the Controller', will be handled by the information updates from the Controller', will be handled by the
protocol used to manipulate the lmap specific configuration. For protocol used to manipulate the lmap specific configuration. The
the first version of the LMAP data models, it is assumed that LMAP data model defined in this document assumes that runtime
runtime logging information will be dealt with using protocols logging information will be communicated using protocols that do
that do not require a formal data model, e.g., the Syslog protocol not require a formal data model, e.g., the Syslog protocol defined
defined in [RFC5424]. in [RFC5424].
o Capability and Status Information: Some of the capability and o Capability and Status Information: Some of the capability and
status information is modeled in the /lmap/capability subtree. status information is modeled in the /lmap/capability subtree.
The list of supported tasks is modeled in the /lmap/capabilities/ The list of supported tasks is modeled in the /lmap/capabilities/
task list. Status information about schedules and actions is task list. Status information about schedules and actions is
included in the /lmap/schedules subtree. Information about included in the /lmap/schedules subtree. Information about
network interfaces can be obtained from the ietf-interfaces YANG network interfaces can be obtained from the ietf-interfaces YANG
data model [RFC7223]. Information about the hardware and the data model [RFC7223]. Information about the hardware and the
firmware can be obtained from the ietf-system YANG data model firmware can be obtained from the ietf-system YANG data model
[RFC7317]. A device identifier can be obtained from the ietf- [RFC7317]. A device identifier can be obtained from the ietf-
hardware YANG data model [I-D.ietf-netmod-entity]. hardware YANG data model [I-D.ietf-netmod-entity].
o Reporting Information: This is modeled by the report data model to o Reporting Information: This is modeled by the report data model to
be implemented by the Collector. Measurement Agents send results be implemented by the Collector. Measurement Agents send results
to the Collector by invoking an RPC on the Collector. to the Collector by invoking an RPC on the Collector.
These six information model sections use a collection of common These six information model aspects use a collection of common
information objects. These common information objects are information objects. These common information objects are
represented in the YANG data model as follows: represented in the YANG data model as follows:
o Schedules: Schedules are modeled in the /lmap/schedules subtree. o Schedules: Schedules are modeled in the /lmap/schedules subtree.
o Channels: Channels are not modeled since the NETCONF server o Channels: Channels are not modeled since the NETCONF server
configuration data model [I-D.ietf-netconf-netconf-client-server] configuration data model [I-D.ietf-netconf-netconf-client-server]
already provides a mechanism to configure NETCONF server channels. already provides a mechanism to configure NETCONF server channels.
o Task Configurations: Configured tasks are modeled in the /lmap/ o Task Configurations: Configured tasks are modeled in the /lmap/
skipping to change at page 10, line 12 skipping to change at page 10, line 12
o Event Information: Event definitions are modeled in the /lmap/ o Event Information: Event definitions are modeled in the /lmap/
events subtree. events subtree.
4. YANG Modules 4. YANG Modules
4.1. LMAP Common YANG Module 4.1. LMAP Common YANG Module
This module imports definitions from [RFC6536] and it references This module imports definitions from [RFC6536] and it references
[ISO-8601]. [ISO-8601].
<CODE BEGINS> file "ietf-lmap-common@2017-02-22.yang" <CODE BEGINS> file "ietf-lmap-common@2017-04-21.yang"
module ietf-lmap-common { module ietf-lmap-common {
yang-version 1.1; yang-version 1.1;
namespace "urn:ietf:params:xml:ns:yang:ietf-lmap-common"; namespace "urn:ietf:params:xml:ns:yang:ietf-lmap-common";
prefix "lmap"; prefix "lmap";
import ietf-inet-types { import ietf-inet-types {
prefix inet; prefix inet;
} }
skipping to change at page 10, line 42 skipping to change at page 10, line 42
Editor: Vaibhav Bajpai Editor: Vaibhav Bajpai
<v.bajpai@jacobs-university.de>"; <v.bajpai@jacobs-university.de>";
description description
"This module provides common definitions used by the data "This module provides common definitions used by the data
models written for Large-Scale Measurement Platforms (LMAP). models written for Large-Scale Measurement Platforms (LMAP).
This module defines typedefs and groupings but no schema This module defines typedefs and groupings but no schema
tree elements."; tree elements.";
revision "2017-02-22" { revision "2017-04-21" {
description description
"Initial version"; "Initial version";
reference reference
"RFC XXX: A YANG Data Model for LMAP Measurement Agents"; "RFC XXXX: A YANG Data Model for LMAP Measurement Agents";
} }
/* /*
* Typedefs * Typedefs
*/ */
typedef identifier { typedef identifier {
type string { type string {
length "1..max"; length "1..max";
} }
skipping to change at page 18, line 22 skipping to change at page 18, line 22
} }
} }
} }
<CODE ENDS> <CODE ENDS>
4.2. LMAP Control YANG Module 4.2. LMAP Control YANG Module
This module imports definitions from [RFC6536], [RFC6991] and the This module imports definitions from [RFC6536], [RFC6991] and the
common LMAP module and it references [RFC7398]. common LMAP module and it references [RFC7398].
<CODE BEGINS> file "ietf-lmap-control@2017-02-22.yang" <CODE BEGINS> file "ietf-lmap-control@2017-04-21.yang"
module ietf-lmap-control { module ietf-lmap-control {
yang-version 1.1; yang-version 1.1;
namespace "urn:ietf:params:xml:ns:yang:ietf-lmap-control"; namespace "urn:ietf:params:xml:ns:yang:ietf-lmap-control";
prefix "lmapc"; prefix "lmapc";
import ietf-yang-types { import ietf-yang-types {
prefix yang; prefix yang;
} }
import ietf-netconf-acm { import ietf-netconf-acm {
skipping to change at page 19, line 11 skipping to change at page 19, line 11
Editor: Vaibhav Bajpai Editor: Vaibhav Bajpai
<v.bajpai@jacobs-university.de>"; <v.bajpai@jacobs-university.de>";
description description
"This module defines a data model for controlling measurement "This module defines a data model for controlling measurement
agents that are part of a Large-Scale Measurement Platform agents that are part of a Large-Scale Measurement Platform
(LMAP). This data model is expected to be implemented by a (LMAP). This data model is expected to be implemented by a
measurement agent."; measurement agent.";
revision "2017-02-22" { revision "2017-04-21" {
description description
"Initial version"; "Initial version";
reference reference
"RFC XXX: A YANG Data Model for LMAP Measurement Agents"; "RFC XXXX: A YANG Data Model for LMAP Measurement Agents";
} }
/* /*
* Typedefs * Typedefs
*/ */
typedef event-ref { typedef event-ref {
type leafref { type leafref {
path "/lmap/events/event/name"; path "/lmap/events/event/name";
} }
skipping to change at page 39, line 32 skipping to change at page 39, line 32
} }
} }
} }
<CODE ENDS> <CODE ENDS>
4.3. LMAP Report YANG Module 4.3. LMAP Report YANG Module
This module imports definitions from [RFC6536] and the common LMAP This module imports definitions from [RFC6536] and the common LMAP
module. module.
<CODE BEGINS> file "ietf-lmap-report@2017-02-22.yang" <CODE BEGINS> file "ietf-lmap-report@2017-04-21.yang"
module ietf-lmap-report { module ietf-lmap-report {
yang-version 1.1; yang-version 1.1;
namespace "urn:ietf:params:xml:ns:yang:ietf-lmap-report"; namespace "urn:ietf:params:xml:ns:yang:ietf-lmap-report";
prefix "lmapr"; prefix "lmapr";
import ietf-yang-types { import ietf-yang-types {
prefix yang; prefix yang;
} }
import ietf-lmap-common { import ietf-lmap-common {
skipping to change at page 40, line 18 skipping to change at page 40, line 18
Editor: Vaibhav Bajpai Editor: Vaibhav Bajpai
<v.bajpai@jacobs-university.de>"; <v.bajpai@jacobs-university.de>";
description description
"This module defines a data model for reporting results from "This module defines a data model for reporting results from
measurement agents, which are part of a Large-Scale Measurement measurement agents, which are part of a Large-Scale Measurement
Platform (LMAP), to result data collectors. This data model is Platform (LMAP), to result data collectors. This data model is
expected to be implemented by a collector."; expected to be implemented by a collector.";
revision "2017-02-22" { revision "2017-04-21" {
description description
"Initial version"; "Initial version";
reference reference
"RFC XXX: A YANG Data Model for LMAP Measurement Agents"; "RFC XXXX: A YANG Data Model for LMAP Measurement Agents";
} }
rpc report { rpc report {
description description
"The report operation is used by an LMAP measurement agent to "The report operation is used by an LMAP measurement agent to
submit measurement results produced by measurement tasks to submit measurement results produced by measurement tasks to
a collector."; a collector.";
input { input {
skipping to change at page 44, line 32 skipping to change at page 44, line 32
} }
} }
} }
} }
<CODE ENDS> <CODE ENDS>
5. Security Considerations 5. Security Considerations
The YANG module defined in this memo is designed to be accessed via The YANG module defined in this memo is designed to be accessed via
the NETCONF protocol [RFC6241]. The lowest NETCONF layer is the the NETCONF protocol [RFC6241]. The lowest NETCONF layer is the
secure transport layer and the mandatory to implement secure secure transport layer, and the mandatory to implement secure
transport is SSH [RFC6242]. The NETCONF access control model transport is SSH [RFC6242]. The lowest RESTCONF layer is HTTPS, and
[RFC6536] provides the means to restrict access for particular the mandatory-to-implement secure transport is TLS [RFC5246].
NETCONF users to a pre-configured subset of all available NETCONF
protocol operations and content. The NETCONF access control model [RFC6536] provides the means to
restrict access for particular NETCONF or RESTCONF users to a pre-
configured subset of all available NETCONF or RESTCONF protocol
operations and content.
There are a number of data nodes defined in this YANG module which There are a number of data nodes defined in this YANG module which
are writable/creatable/deletable (i.e., config true, which is the are writable/creatable/deletable (i.e., config true, which is the
default). These data nodes may be considered sensitive or vulnerable default). These data nodes may be considered sensitive or vulnerable
in some network environments. Write operations (e.g., edit-config) in some network environments. Write operations (e.g., edit-config)
to these data nodes without proper protection can have a negative to these data nodes without proper protection can have a negative
effect on network operations. These are the subtrees and data nodes effect on network operations. These are the subtrees and data nodes
and their sensitivity/vulnerability: and their sensitivity/vulnerability:
/lmap/agent This subtree configures general properties of /lmap/agent This subtree configures general properties of
skipping to change at page 46, line 47 skipping to change at page 46, line 50
that identifiers are properly mapped into safe identifiers. that identifiers are properly mapped into safe identifiers.
The data model allows to specify options in the form of name value The data model allows to specify options in the form of name value
pairs that are passed to programs. Implementers ought to take care pairs that are passed to programs. Implementers ought to take care
that option names and values are passed literally to programs. In that option names and values are passed literally to programs. In
particular, shell expansions that may alter option names and values particular, shell expansions that may alter option names and values
must not be performed. must not be performed.
6. IANA Considerations 6. IANA Considerations
This document registers a URI in the "IETF XML Registry" [RFC3688]. This document registers three URIs in the "IETF XML Registry"
Following the format in RFC 3688, the following registrations have [RFC3688]. Following the format in RFC 3688, the following
been made. registrations have been made.
URI: urn:ietf:params:xml:ns:yang:ietf-lmap-common URI: urn:ietf:params:xml:ns:yang:ietf-lmap-common
Registrant Contact: The IESG. Registrant Contact: The IESG.
XML: N/A; the requested URI is an XML namespace. XML: N/A; the requested URI is an XML namespace.
URI: urn:ietf:params:xml:ns:yang:ietf-lmap-control URI: urn:ietf:params:xml:ns:yang:ietf-lmap-control
Registrant Contact: The IESG. Registrant Contact: The IESG.
XML: N/A; the requested URI is an XML namespace. XML: N/A; the requested URI is an XML namespace.
URI: urn:ietf:params:xml:ns:yang:ietf-lmap-report URI: urn:ietf:params:xml:ns:yang:ietf-lmap-report
Registrant Contact: The IESG. Registrant Contact: The IESG.
XML: N/A; the requested URI is an XML namespace. XML: N/A; the requested URI is an XML namespace.
This document registers a YANG module in the "YANG Module Names" This document registers three YANG modules in the "YANG Module Names"
registry [RFC6020]. registry [RFC6020].
name: ietf-lmap-common name: ietf-lmap-common
namespace: urn:ietf:params:xml:ns:yang:ietf-lmap-common namespace: urn:ietf:params:xml:ns:yang:ietf-lmap-common
prefix: lmap prefix: lmap
reference: RFC XXXX reference: RFC XXXX
name: ietf-lmap-control name: ietf-lmap-control
namespace: urn:ietf:params:xml:ns:yang:ietf-lmap-control namespace: urn:ietf:params:xml:ns:yang:ietf-lmap-control
prefix: lmapc prefix: lmapc
skipping to change at page 47, line 41 skipping to change at page 47, line 41
namespace: urn:ietf:params:xml:ns:yang:ietf-lmap-report namespace: urn:ietf:params:xml:ns:yang:ietf-lmap-report
prefix: lmapr prefix: lmapr
reference: RFC XXXX reference: RFC XXXX
7. Acknowledgements 7. Acknowledgements
Several people contributed to this specification by reviewing early Several people contributed to this specification by reviewing early
versions and actively participating in the LMAP working group versions and actively participating in the LMAP working group
(apologies to those unintentionally omitted): Marcelo Bagnulo, Martin (apologies to those unintentionally omitted): Marcelo Bagnulo, Martin
Bjorklund, Trevor Burbridge, Timothy Carey, Alissa Cooper, Philip Bjorklund, Trevor Burbridge, Timothy Carey, Alissa Cooper, Philip
Eardley, Al Morton, Dan Romascanu, Andrea Soppera, and Barbara Stark. Eardley, Al Morton, Dan Romascanu, Andrea Soppera, Barbara Stark, and
Qin Wu.
Juergen Schoenwaelder and Vaibhav Bajpai worked in part on the Leone Juergen Schoenwaelder and Vaibhav Bajpai worked in part on the Leone
research project, which received funding from the European Union research project, which received funding from the European Union
Seventh Framework Programme [FP7/2007-2013] under grant agreement Seventh Framework Programme [FP7/2007-2013] under grant agreement
number 317647. number 317647.
Juergen Schoenwaelder and Vaibhav Bajpai were partly funded by Juergen Schoenwaelder and Vaibhav Bajpai were partly funded by
Flamingo, a Network of Excellence project (ICT-318488) supported by Flamingo, a Network of Excellence project (ICT-318488) supported by
the European Commission under its Seventh Framework Programme. the European Commission under its Seventh Framework Programme.
8. References 8. References
8.1. Normative References 8.1. Normative References
[I-D.ietf-lmap-information-model]
Burbridge, T., Eardley, P., Bagnulo, M., and J.
Schoenwaelder, "Information Model for Large-Scale
Measurement Platforms (LMAP)", draft-ietf-lmap-
information-model-16 (work in progress), January 2017.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, DOI 10.17487/ Requirement Levels", BCP 14, RFC 2119, DOI 10.17487/
RFC2119, March 1997, RFC2119, March 1997,
<http://www.rfc-editor.org/info/rfc2119>. <http://www.rfc-editor.org/info/rfc2119>.
[RFC6020] Bjorklund, M., Ed., "YANG - A Data Modeling Language for [RFC6020] Bjorklund, M., Ed., "YANG - A Data Modeling Language for
the Network Configuration Protocol (NETCONF)", RFC 6020, the Network Configuration Protocol (NETCONF)", RFC 6020,
DOI 10.17487/RFC6020, October 2010, DOI 10.17487/RFC6020, October 2010,
<http://www.rfc-editor.org/info/rfc6020>. <http://www.rfc-editor.org/info/rfc6020>.
[RFC6991] Schoenwaelder, J., Ed., "Common YANG Data Types", RFC [RFC6991] Schoenwaelder, J., Ed., "Common YANG Data Types", RFC
6991, DOI 10.17487/RFC6991, July 2013, 6991, DOI 10.17487/RFC6991, July 2013,
<http://www.rfc-editor.org/info/rfc6991>. <http://www.rfc-editor.org/info/rfc6991>.
[RFC7950] Bjorklund, M., Ed., "The YANG 1.1 Data Modeling Language", [RFC7950] Bjorklund, M., Ed., "The YANG 1.1 Data Modeling Language",
RFC 7950, DOI 10.17487/RFC7950, August 2016, RFC 7950, DOI 10.17487/RFC7950, August 2016,
<http://www.rfc-editor.org/info/rfc7950>. <http://www.rfc-editor.org/info/rfc7950>.
8.2. Informative References 8.2. Informative References
[I-D.ietf-lmap-information-model]
Burbridge, T., Eardley, P., Bagnulo, M., and J.
Schoenwaelder, "Information Model for Large-Scale
Measurement Platforms (LMAP)", draft-ietf-lmap-
information-model-16 (work in progress), January 2017.
[I-D.ietf-netconf-netconf-client-server] [I-D.ietf-netconf-netconf-client-server]
Watsen, K., Wu, G., and J. Schoenwaelder, "NETCONF Client Watsen, K., Wu, G., and J. Schoenwaelder, "NETCONF Client
and Server Models", draft-ietf-netconf-netconf-client- and Server Models", draft-ietf-netconf-netconf-client-
server-01 (work in progress), November 2016. server-01 (work in progress), November 2016.
[I-D.ietf-netmod-entity] [I-D.ietf-netmod-entity]
Bierman, A., Bjorklund, M., Dong, J., and D. Romascanu, "A Bierman, A., Bjorklund, M., Dong, J., and D. Romascanu, "A
YANG Data Model for Hardware Management", draft-ietf- YANG Data Model for Hardware Management", draft-ietf-
netmod-entity-02 (work in progress), January 2017. netmod-entity-02 (work in progress), January 2017.
[ISO-8601] [ISO-8601]
International Organization for Standardization, "Data International Organization for Standardization, "Data
elements and interchange formats -- Information elements and interchange formats -- Information
interchange -- Representation of dates and times", ISO interchange -- Representation of dates and times", ISO
Standard 8601:2004, 2004. Standard 8601:2004, 2004.
[RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688, [RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688,
DOI 10.17487/RFC3688, January 2004, DOI 10.17487/RFC3688, January 2004,
<http://www.rfc-editor.org/info/rfc3688>. <http://www.rfc-editor.org/info/rfc3688>.
[RFC5246] Dierks, T. and E. Rescorla, "The Transport Layer Security
(TLS) Protocol Version 1.2", RFC 5246, DOI 10.17487/
RFC5246, August 2008,
<http://www.rfc-editor.org/info/rfc5246>.
[RFC5424] Gerhards, R., "The Syslog Protocol", RFC 5424, DOI 10 [RFC5424] Gerhards, R., "The Syslog Protocol", RFC 5424, DOI 10
.17487/RFC5424, March 2009, .17487/RFC5424, March 2009,
<http://www.rfc-editor.org/info/rfc5424>. <http://www.rfc-editor.org/info/rfc5424>.
[RFC6241] Enns, R., Ed., Bjorklund, M., Ed., Schoenwaelder, J., Ed., [RFC6241] Enns, R., Ed., Bjorklund, M., Ed., Schoenwaelder, J., Ed.,
and A. Bierman, Ed., "Network Configuration Protocol and A. Bierman, Ed., "Network Configuration Protocol
(NETCONF)", RFC 6241, DOI 10.17487/RFC6241, June 2011, (NETCONF)", RFC 6241, DOI 10.17487/RFC6241, June 2011,
<http://www.rfc-editor.org/info/rfc6241>. <http://www.rfc-editor.org/info/rfc6241>.
[RFC6242] Wasserman, M., "Using the NETCONF Protocol over Secure [RFC6242] Wasserman, M., "Using the NETCONF Protocol over Secure
 End of changes. 30 change blocks. 
44 lines changed or deleted 53 lines changed or added

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