draft-ietf-lmap-restconf-02.txt   draft-ietf-lmap-restconf-03.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: September 22, 2016 March 21, 2016 Expires: January 9, 2017 July 8, 2016
Using RESTCONF with LMAP Measurement Agents Using RESTCONF with LMAP Measurement Agents
draft-ietf-lmap-restconf-02.txt draft-ietf-lmap-restconf-03.txt
Abstract Abstract
This document describes how RESTCONF can be used with a YANG data This document describes how RESTCONF can be used with a YANG data
model for Large-Scale Measurement Platforms (LMAP). model for Large-Scale Measurement Platforms (LMAP).
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
provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
skipping to change at page 1, line 31 skipping to change at page 1, line 31
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 September 22, 2016. This Internet-Draft will expire on January 9, 2017.
Copyright Notice Copyright Notice
Copyright (c) 2016 IETF Trust and the persons identified as the Copyright (c) 2016 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 12 skipping to change at page 2, line 12
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License. described in the Simplified BSD License.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
1.1. Terminology . . . . . . . . . . . . . . . . . . . . . . . 2 1.1. Terminology . . . . . . . . . . . . . . . . . . . . . . . 2
2. Overview of RESTCONF . . . . . . . . . . . . . . . . . . . . 3 2. Overview of RESTCONF . . . . . . . . . . . . . . . . . . . . 3
3. RESTCONF as LMAP Control Protocol . . . . . . . . . . . . . . 3 3. RESTCONF as LMAP Control Protocol . . . . . . . . . . . . . . 3
4. RESTCONF as LMAP Report Protocol . . . . . . . . . . . . . . 3 4. RESTCONF as LMAP Report Protocol . . . . . . . . . . . . . . 3
5. Security Considerations . . . . . . . . . . . . . . . . . . . 4 5. RESTCONF Configuration for LMAP . . . . . . . . . . . . . . . 4
6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 4 6. Security Considerations . . . . . . . . . . . . . . . . . . . 4
7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 4 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 4
8. References . . . . . . . . . . . . . . . . . . . . . . . . . 4 8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 4
8.1. Normative References . . . . . . . . . . . . . . . . . . 4 9. References . . . . . . . . . . . . . . . . . . . . . . . . . 4
8.2. Informative References . . . . . . . . . . . . . . . . . 4 9.1. Normative References . . . . . . . . . . . . . . . . . . 4
9.2. Informative References . . . . . . . . . . . . . . . . . 4
Appendix A. Example RESTCONF Control Protocol Exchange . . . . . 5 Appendix A. Example RESTCONF Control Protocol Exchange . . . . . 5
Appendix B. Example RESTCONF Report Protocol Exchange . . . . . 7 Appendix B. Example RESTCONF Report Protocol Exchange . . . . . 7
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 9 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 9
1. Introduction 1. Introduction
This document discusses how a Controller can use the RESTCONF This document discusses how a Controller can use the RESTCONF
protocol [I-D.ietf-netconf-restconf] to configure Large-Scale protocol [I-D.ietf-netconf-restconf] to configure Large-Scale
Measurement of Broadband Performance (LMAP) Measurement Agents Measurement of Broadband Performance (LMAP) Measurement Agents
[RFC7594]. It also discusses how RESTCONF can be used by a [RFC7594]. It also discusses how RESTCONF can be used by a
skipping to change at page 4, line 5 skipping to change at page 4, line 5
An example exchange showing a REST call to create a schedule object An example exchange showing a REST call to create a schedule object
is shown in Appendix A. is shown in Appendix A.
4. RESTCONF as LMAP Report Protocol 4. RESTCONF as LMAP Report Protocol
For reporting results from the Measurement Agent to a Collector, the For reporting results from the Measurement Agent to a Collector, the
Collector is assumed to act as a RESTCONF server. The Measurement Collector is assumed to act as a RESTCONF server. The Measurement
Agent pushes results to the Collector by invoking an operation on the Agent pushes results to the Collector by invoking an operation on the
Controller. Controller.
5. Security Considerations 5. RESTCONF Configuration for LMAP
XXX: This section should explain how an LMAP implementation needs to
be configured to make use of the call-home mechanism and how report
tasks refer to the configuration (if any standardized) needed to
obtain the necessary credentials to report results. This needs to be
worked through in detail.
6. Security Considerations
TBD TBD
6. IANA Considerations 7. IANA Considerations
This document has no requests for IANA. This document has no requests for IANA.
7. Acknowledgements 8. Acknowledgements
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 9. References
8.1. Normative References 9.1. Normative References
[I-D.ietf-lmap-yang] [I-D.ietf-lmap-yang]
Schoenwaelder, J. and V. Bajpai, "A YANG Data Model for Schoenwaelder, J. and V. Bajpai, "A YANG Data Model for
LMAP Measurement Agents", draft-ietf-lmap-yang-03 (work in LMAP Measurement Agents", draft-ietf-lmap-yang-04 (work in
progress), March 2016. progress), March 2016.
[I-D.ietf-netconf-restconf] [I-D.ietf-netconf-restconf]
Bierman, A., Bjorklund, M., and K. Watsen, "RESTCONF Bierman, A., Bjorklund, M., and K. Watsen, "RESTCONF
Protocol", draft-ietf-netconf-restconf-10 (work in Protocol", draft-ietf-netconf-restconf-14 (work in
progress), March 2016. progress), June 2016.
8.2. Informative References 9.2. Informative References
[I-D.ietf-lmap-information-model] [I-D.ietf-lmap-information-model]
Burbridge, T., Eardley, P., Bagnulo, M., and J. Burbridge, T., Eardley, P., Bagnulo, M., and J.
Schoenwaelder, "Information Model for Large-Scale Schoenwaelder, "Information Model for Large-Scale
Measurement Platforms (LMAP)", draft-ietf-lmap- Measurement Platforms (LMAP)", draft-ietf-lmap-
information-model-08 (work in progress), March 2016. information-model-09 (work in progress), March 2016.
[I-D.ietf-netconf-call-home] [I-D.ietf-netconf-call-home]
Watsen, K., "NETCONF Call Home and RESTCONF Call Home", Watsen, K., "NETCONF Call Home and RESTCONF Call Home",
draft-ietf-netconf-call-home-17 (work in progress), draft-ietf-netconf-call-home-17 (work in progress),
December 2015. December 2015.
[I-D.ietf-netconf-server-model] [I-D.ietf-netconf-server-model]
Watsen, K. and J. Schoenwaelder, "NETCONF Server and Watsen, K. and J. Schoenwaelder, "NETCONF Server and
RESTCONF Server Configuration Models", draft-ietf-netconf- RESTCONF Server Configuration Models", draft-ietf-netconf-
server-model-09 (work in progress), March 2016. server-model-09 (work in progress), March 2016.
skipping to change at page 8, line 4 skipping to change at page 8, line 4
M: Content-Type: application/yang.operation+xml M: Content-Type: application/yang.operation+xml
M: M:
M: <input xmlns="urn:ietf:params:xml:ns:yang:ietf-lmap-report"> M: <input xmlns="urn:ietf:params:xml:ns:yang:ietf-lmap-report">
M: <date>2015-10-28T13:27:42+02:00</date> M: <date>2015-10-28T13:27:42+02:00</date>
M: <agent-id>550e8400-e29b-41d4-a716-446655440000</agent-id> M: <agent-id>550e8400-e29b-41d4-a716-446655440000</agent-id>
M: <group-id>wireless measurement at the north-pole</group-id> M: <group-id>wireless measurement at the north-pole</group-id>
M: <result> M: <result>
M: <schedule-name>pinger</schedule-name> M: <schedule-name>pinger</schedule-name>
M: <action-name>fping</action-name> M: <action-name>fping</action-name>
M: <task-name>fping</task-name> M: <task-name>fping</task-name>
M: <start>2016-03-21T10:48:55+01:00</start>
M: <start>2016-03-21T10:48:57+01:00</start>
M: <option> M: <option>
M: <id>display-address</id> M: <id>display-address</id>
M: <name>-A</name> M: <name>-A</name>
M: </option> M: </option>
M: <option> M: <option>
M: <id>display-DNS-lookup</id> M: <id>display-DNS-lookup</id>
M: <name>-d</name> M: <name>-d</name>
M: </option> M: </option>
M: <option> M: <option>
M: <id>number-of-packets</id> M: <id>number-of-packets</id>
skipping to change at page 8, line 31 skipping to change at page 8, line 29
M: <name>-q</name> M: <name>-q</name>
M: </option> M: </option>
M: <option> M: <option>
M: <id>www.example.org</id> M: <id>www.example.org</id>
M: <name>www.example.org</name> M: <name>www.example.org</name>
M: </option> M: </option>
M: <option> M: <option>
M: <id>mail.example.com</id> M: <id>mail.example.com</id>
M: <name>mail.example.com</name> M: <name>mail.example.com</name>
M: </option> M: </option>
M: <start>2016-03-21T10:48:55+01:00</start>
M: <end>2016-03-21T10:48:57+01:00</end>
M: <status>0</status>
M: <table> M: <table>
M: <column>target</column> M: <column>target</column>
M: <column>ip</column> M: <column>ip</column>
M: <column>rtt-1</column> M: <column>rtt-1</column>
M: <column>rtt-2</column> M: <column>rtt-2</column>
M: <column>rtt-3</column> M: <column>rtt-3</column>
M: <column>rtt-4</column> M: <column>rtt-4</column>
M: <column>rtt-5</column> M: <column>rtt-5</column>
M: <row> M: <row>
M: <value>www.example.org</value> M: <value>www.example.org</value>
M: <value>192.0.2.1</value> M: <value>2001:db8::1</value>
M: <value>14.15</value> M: <value>14.15</value>
M: <value>14.14</value> M: <value>14.14</value>
M: <value>14.09</value> M: <value>14.09</value>
M: <value>14.17</value> M: <value>14.17</value>
M: <value>14.51</value> M: <value>14.51</value>
M: </row> M: </row>
M: <row> M: <row>
M: <value>mail.example.org</value> M: <value>mail.example.org</value>
M: <value>192.0.2.2</value> M: <value>2001:db8::2</value>
M: <value>12.24</value> M: <value>12.24</value>
M: <value>11.99</value> M: <value>11.99</value>
M: <value>12.49</value> M: <value>12.49</value>
M: <value>11.87</value> M: <value>11.87</value>
M: <value>12.45</value> M: <value>12.45</value>
M: </row> M: </row>
M: </table> M: </table>
M: </result> M: </result>
M: </input> M: </input>
 End of changes. 17 change blocks. 
23 lines changed or deleted 33 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/