]> Jacobs University Bremen

j.schoenwaelder@jacobs-university.de

Jacobs University Bremen

v.bajpai@jacobs-university.de

Operations and Management LMAP YANG RESTCONF This document describes how RESTCONF can be used with a YANG data model for Large-Scale Measurement Platforms (LMAP).

This document discusses how a Controller can use the RESTCONF protocol to configure Large-Scale Measurement of Broadband Performance (LMAP) Measurement Agents . It also discusses how RESTCONF can be used by a Measurement Agent to report measurement results to a Collector. Measurement Agents may be deployed as separate hardware devices or as functions embedded in consumer electronic devices and home routers or as pure software solutions that can be installed on off-the-shelf computing equipment. Measurement Agents receive instructions from a Controller about when and how to conduct what measurements (the measurement schedule) and how and when to report measurement results to a data Collector (the report schedule). Further information about the interaction between Measurement Agents and Controllers and Collectors can be found in . The LMAP information model defines the information exchanged between a Controller and an Measurement Agent and the information exchanged between an Measurement Agent and a Collector. An information model is conceptual and protocol-independent. A concrete YANG data model derived from the conceptual information model is defined in .

This document uses the LMAP terminology defined in . The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in .

The RESTCONF protocol provides a REST-like interface to access and manipulate a so-called unified YANG datastore . The basic idea behind RESTCONF is expose a YANG datastores as a collection of Web resources that can be manipulated using standard HTTP DELETE, PATCH, POST, and PUT methods. The resource hierarchy is derived from the nesting structure of the YANG schema tree, leading to a so-called data model driven REST API. RESTCONF is essentially a convention how to use HTTP over TLS to access a datastore that has a structure defined by a YANG data model. The data is exchanged in XML encoding or JSON encoding. The normal mode of operation is that the RESTCONF client initiates a secure transport to the RESTCONF server. For devices located behind a NAT, a so called 'call-home' mechanism has been defined that enables the RESTCONF server to establish a secure transport to a RESTCONF client. Note that call home only changes the TCP connection establishment, the TLS and HTTP client/server roles do not change. The policy used to call home can be configured through a configuration data model . This model provides a mechanism to configure a list of redundant endpoints and it provides control over call-home policies (e.g, call-home frequency, idle-timers, keep-alive timers).

It is straight-forward to use RESTCONF as a control protocol. The YANG data model derived from the underlying information model translates into a collection of RESTCONF resources that can be manipulated at various levels of granularity using DELETE, PATCH, POST, and PUT methods. An example exchange showing a REST call to create a schedule object is shown in .

For reporting results from the Measurement Agent to a Collector, the Collector is assumed to act as a RESTCONF server. The Measurement Agent pushes results to the Collector by invoking an operation on the Controller.

TBD

This document has no requests for IANA.

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 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.

&rfc2119; &rfc6020; &rfc7223; &rfc7230; &rfc7277; &rfc7317; &rfc7594; &I-D.ietf-lmap-information-model; &I-D.ietf-lmap-yang; &I-D.ietf-netconf-restconf; &I-D.ietf-netconf-call-home; &I-D.ietf-netconf-server-model;

Below is a YANG tree diagram of a part of the data model covering schedules. This is taken from .

Below is an XML representation of instance data conforming to the YANG data model is shown below. Note that some of the strings are references to other portions of the instance data not show here. This is again taken from .

hourly-schedule hourly icmp-latency-hourly icmp-latency-measurement daily sequential ]]>

Below is an example showing how RESTCONF can be used to create the above schedule. The prefix C: indicates the Controller, the prefix M: indicates the Measurement Agent. This example uses a JSON encoding (and note that much of the white-space can be removed, this is only there to help with readability).

Below is an example showing how a Measurement Agent can submit results to a Collector running an RESTCONF server. The prefix C: indicates the Collector, the prefix M: indicates the Measurement Agent.

M: M: 2015-10-28T13:27:42+02:00 M: 550e8400-e29b-41d4-a716-446655440000 M: wireless measurement at the north-pole M: M: icmp-latency-measurement M: M: urn:.... M: M:

M: target M: rtt M:

M: M: 2015-03-25T00:00:55+00:00 M: 192.0.2.1 M: 42 M: M: M: 2015-03-25T00:00:56+00:00 M: 192.0.2.1 M: 42 M: M: M: M: C: HTTP/1.1 200 OK ]]>