--- 1/draft-ietf-netconf-restconf-03.txt 2015-01-30 18:14:58.051424722 -0800 +++ 2/draft-ietf-netconf-restconf-04.txt 2015-01-30 18:14:58.211428611 -0800 @@ -1,21 +1,21 @@ Network Working Group A. Bierman Internet-Draft YumaWorks Intended status: Standards Track M. Bjorklund -Expires: April 28, 2015 Tail-f Systems +Expires: August 3, 2015 Tail-f Systems K. Watsen Juniper Networks - October 25, 2014 + January 30, 2015 RESTCONF Protocol - draft-ietf-netconf-restconf-03 + draft-ietf-netconf-restconf-04 Abstract This document describes an HTTP-based protocol that provides a programmatic interface for accessing data defined in YANG, using the datastores defined in NETCONF. Status of This Memo This Internet-Draft is submitted in full conformance with the @@ -24,163 +24,166 @@ Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet- Drafts is at http://datatracker.ietf.org/drafts/current/. Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress." - This Internet-Draft will expire on April 28, 2015. + This Internet-Draft will expire on August 3, 2015. Copyright Notice - Copyright (c) 2014 IETF Trust and the persons identified as the + Copyright (c) 2015 IETF Trust and the persons identified as the document authors. All rights reserved. This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info) in effect on the date of 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. Table of Contents 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 4 - 1.1. Secure Transport . . . . . . . . . . . . . . . . . . . . 5 - 1.2. Simple Subset of NETCONF Functionality . . . . . . . . . 5 - 1.3. Data Model Driven API . . . . . . . . . . . . . . . . . . 6 - 1.4. Terminology . . . . . . . . . . . . . . . . . . . . . . . 7 - 1.4.1. NETCONF . . . . . . . . . . . . . . . . . . . . . . . 7 - 1.4.2. HTTP . . . . . . . . . . . . . . . . . . . . . . . . 8 - 1.4.3. YANG . . . . . . . . . . . . . . . . . . . . . . . . 9 - 1.4.4. Terms . . . . . . . . . . . . . . . . . . . . . . . . 9 - 1.4.5. URI Template . . . . . . . . . . . . . . . . . . . . 11 - 1.4.6. Tree Diagrams . . . . . . . . . . . . . . . . . . . . 11 - 2. Resources . . . . . . . . . . . . . . . . . . . . . . . . . . 11 - 2.1. RESTCONF Resource Types . . . . . . . . . . . . . . . . . 12 - 2.2. Resource Discovery . . . . . . . . . . . . . . . . . . . 12 - 2.3. API Resource . . . . . . . . . . . . . . . . . . . . . . 13 - 2.3.1. {+restconf}/data . . . . . . . . . . . . . . . . . . 13 - 2.3.2. {+restconf}/operations . . . . . . . . . . . . . . . 14 - 2.4. Datastore Resource . . . . . . . . . . . . . . . . . . . 14 - 2.4.1. Edit Collision Detection . . . . . . . . . . . . . . 15 - 2.5. Data Resource . . . . . . . . . . . . . . . . . . . . . . 15 - 2.5.1. Encoding YANG Instance Identifiers in the Request URI 16 - 2.5.2. Defaults Handling . . . . . . . . . . . . . . . . . . 18 - 2.6. Collection Resource . . . . . . . . . . . . . . . . . . . 19 - 2.7. Operation Resource . . . . . . . . . . . . . . . . . . . 19 - 2.7.1. Encoding Operation Input Parameters . . . . . . . . . 20 - 2.7.2. Encoding Operation Output Parameters . . . . . . . . 21 - 2.8. Schema Resource . . . . . . . . . . . . . . . . . . . . . 22 - 2.9. Stream Resource . . . . . . . . . . . . . . . . . . . . . 23 - 2.10. Errors Resource . . . . . . . . . . . . . . . . . . . . . 23 - 3. Operations . . . . . . . . . . . . . . . . . . . . . . . . . 23 - 3.1. OPTIONS . . . . . . . . . . . . . . . . . . . . . . . . . 24 - 3.2. HEAD . . . . . . . . . . . . . . . . . . . . . . . . . . 24 - 3.3. GET . . . . . . . . . . . . . . . . . . . . . . . . . . . 25 - 3.4. POST . . . . . . . . . . . . . . . . . . . . . . . . . . 26 - 3.4.1. Create Resource Mode . . . . . . . . . . . . . . . . 26 - 3.4.2. Invoke Operation Mode . . . . . . . . . . . . . . . . 27 - 3.5. PUT . . . . . . . . . . . . . . . . . . . . . . . . . . . 28 - 3.6. PATCH . . . . . . . . . . . . . . . . . . . . . . . . . . 29 - 3.7. DELETE . . . . . . . . . . . . . . . . . . . . . . . . . 30 - 3.8. Query Parameters . . . . . . . . . . . . . . . . . . . . 31 - 3.8.1. Query Parameter URIs . . . . . . . . . . . . . . . . 31 - 3.8.2. The "content" Query Parameter . . . . . . . . . . . . 32 - 3.8.3. The "depth" Query Parameter . . . . . . . . . . . . . 32 - 3.8.4. The "select" Query Parameter . . . . . . . . . . . . 33 - 3.8.5. The "insert" Query Parameter . . . . . . . . . . . . 34 - 3.8.6. The "point" Query Parameter . . . . . . . . . . . . . 34 - 3.8.7. The "limit" Query Parameter . . . . . . . . . . . . . 35 - 3.8.8. The "offset" Query Parameter . . . . . . . . . . . . 35 - 3.8.9. The "filter" Query Parameter . . . . . . . . . . . . 36 - 3.8.10. The "start-time" Query Parameter . . . . . . . . . . 36 - 3.8.11. The "stop-time" Query Parameter . . . . . . . . . . . 37 - 4. Messages . . . . . . . . . . . . . . . . . . . . . . . . . . 38 - 4.1. Request URI Structure . . . . . . . . . . . . . . . . . . 38 - 4.2. RESTCONF Path Resolution . . . . . . . . . . . . . . . . 39 - 4.3. Message Headers . . . . . . . . . . . . . . . . . . . . . 40 - 4.4. Message Encoding . . . . . . . . . . . . . . . . . . . . 41 - 4.5. RESTCONF Meta-Data . . . . . . . . . . . . . . . . . . . 41 - 4.6. Return Status . . . . . . . . . . . . . . . . . . . . . . 42 - 4.7. Message Caching . . . . . . . . . . . . . . . . . . . . . 42 - 5. Notifications . . . . . . . . . . . . . . . . . . . . . . . . 42 - 5.1. Server Support . . . . . . . . . . . . . . . . . . . . . 42 - 5.2. Event Streams . . . . . . . . . . . . . . . . . . . . . . 43 - 5.3. Subscribing to Receive Notifications . . . . . . . . . . 45 - 5.3.1. NETCONF Event Stream . . . . . . . . . . . . . . . . 46 - 5.4. Receiving Event Notifications . . . . . . . . . . . . . . 46 - 6. Error Reporting . . . . . . . . . . . . . . . . . . . . . . . 48 - 6.1. Error Response Message . . . . . . . . . . . . . . . . . 49 - 7. RESTCONF module . . . . . . . . . . . . . . . . . . . . . . . 51 - 8. RESTCONF Monitoring . . . . . . . . . . . . . . . . . . . . . 57 - 8.1. restconf-state/capabilities . . . . . . . . . . . . . . . 58 - 8.2. restconf-state/streams . . . . . . . . . . . . . . . . . 58 - 8.3. RESTCONF Monitoring Module . . . . . . . . . . . . . . . 58 - 9. YANG Module Library . . . . . . . . . . . . . . . . . . . . . 62 - 9.1. modules . . . . . . . . . . . . . . . . . . . . . . . . . 63 - 9.1.1. modules/module . . . . . . . . . . . . . . . . . . . 63 - 9.2. YANG Library Module . . . . . . . . . . . . . . . . . . . 64 - 10. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 68 - 10.1. The "restconf" Relation Type . . . . . . . . . . . . . . 68 - 10.2. YANG Module Registry . . . . . . . . . . . . . . . . . . 68 - 10.3. application/yang Media Sub Types . . . . . . . . . . . . 69 - 10.4. NETCONF Capability URNs . . . . . . . . . . . . . . . . 70 - 11. Security Considerations . . . . . . . . . . . . . . . . . . . 70 - 12. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 71 - 13. References . . . . . . . . . . . . . . . . . . . . . . . . . 71 - 13.1. Normative References . . . . . . . . . . . . . . . . . . 71 - 13.2. Informative References . . . . . . . . . . . . . . . . . 73 - Appendix A. Change Log . . . . . . . . . . . . . . . . . . . . . 73 - A.1. 02 - 03 . . . . . . . . . . . . . . . . . . . . . . . . . 73 - A.2. 01 - 02 . . . . . . . . . . . . . . . . . . . . . . . . . 74 - A.3. 00 - 01 . . . . . . . . . . . . . . . . . . . . . . . . . 75 - A.4. bierman:restconf-04 to ietf:restconf-00 . . . . . . . . . 76 + 1.1. Simple Subset of NETCONF Functionality . . . . . . . . . 5 + 1.2. Data Model Driven API . . . . . . . . . . . . . . . . . . 6 + 1.3. Terminology . . . . . . . . . . . . . . . . . . . . . . . 7 + 1.3.1. NETCONF . . . . . . . . . . . . . . . . . . . . . . . 7 + 1.3.2. HTTP . . . . . . . . . . . . . . . . . . . . . . . . 8 + 1.3.3. YANG . . . . . . . . . . . . . . . . . . . . . . . . 9 + 1.3.4. Terms . . . . . . . . . . . . . . . . . . . . . . . . 9 + 1.3.5. URI Template . . . . . . . . . . . . . . . . . . . . 11 + 1.3.6. Tree Diagrams . . . . . . . . . . . . . . . . . . . . 11 + 2. Transport Protocol Requirements . . . . . . . . . . . . . . . 11 + 2.1. Integrity and Confidentiality . . . . . . . . . . . . . . 11 + 2.2. HTTPS with X.509v3 Certificates . . . . . . . . . . . . . 12 + 2.3. Certificate Validation . . . . . . . . . . . . . . . . . 12 + 2.4. Authenticated Server Identity . . . . . . . . . . . . . . 12 + 2.5. Authenticated Client Identity . . . . . . . . . . . . . . 12 + 3. Resources . . . . . . . . . . . . . . . . . . . . . . . . . . 13 + 3.1. Root Resource Discovery . . . . . . . . . . . . . . . . . 14 + 3.2. RESTCONF Resource Types . . . . . . . . . . . . . . . . . 15 + 3.3. API Resource . . . . . . . . . . . . . . . . . . . . . . 15 + 3.3.1. {+restconf}/data . . . . . . . . . . . . . . . . . . 16 + 3.3.2. {+restconf}/operations . . . . . . . . . . . . . . . 17 + 3.4. Datastore Resource . . . . . . . . . . . . . . . . . . . 17 + 3.4.1. Edit Collision Detection . . . . . . . . . . . . . . 18 + 3.5. Data Resource . . . . . . . . . . . . . . . . . . . . . . 19 + 3.5.1. Encoding Data Resource Identifiers in the Request URI 19 + 3.5.2. Defaults Handling . . . . . . . . . . . . . . . . . . 22 + 3.6. Operation Resource . . . . . . . . . . . . . . . . . . . 22 + 3.6.1. Encoding Operation Input Parameters . . . . . . . . . 23 + 3.6.2. Encoding Operation Output Parameters . . . . . . . . 24 + 3.7. Schema Resource . . . . . . . . . . . . . . . . . . . . . 24 + 3.8. Event Stream Resource . . . . . . . . . . . . . . . . . . 25 + 3.9. Errors Media Type . . . . . . . . . . . . . . . . . . . . 26 + 4. Operations . . . . . . . . . . . . . . . . . . . . . . . . . 26 + 4.1. OPTIONS . . . . . . . . . . . . . . . . . . . . . . . . . 27 + 4.2. HEAD . . . . . . . . . . . . . . . . . . . . . . . . . . 27 + 4.3. GET . . . . . . . . . . . . . . . . . . . . . . . . . . . 27 + 4.4. POST . . . . . . . . . . . . . . . . . . . . . . . . . . 28 + 4.4.1. Create Resource Mode . . . . . . . . . . . . . . . . 29 + 4.4.2. Invoke Operation Mode . . . . . . . . . . . . . . . . 30 + 4.5. PUT . . . . . . . . . . . . . . . . . . . . . . . . . . . 31 + 4.6. PATCH . . . . . . . . . . . . . . . . . . . . . . . . . . 32 + 4.6.1. Plain Patch . . . . . . . . . . . . . . . . . . . . . 32 - Appendix B. Open Issues . . . . . . . . . . . . . . . . . . . . 76 - Appendix C. Example YANG Module . . . . . . . . . . . . . . . . 76 - C.1. example-jukebox YANG Module . . . . . . . . . . . . . . . 77 - Appendix D. RESTCONF Message Examples . . . . . . . . . . . . . 82 - D.1. Resource Retrieval Examples . . . . . . . . . . . . . . . 82 - D.1.1. Retrieve the Top-level API Resource . . . . . . . . . 82 - D.1.2. Retrieve The Server Module Information . . . . . . . 83 - D.1.3. Retrieve The Server Capability Information . . . . . 84 - D.2. Edit Resource Examples . . . . . . . . . . . . . . . . . 85 - D.2.1. Create New Data Resources . . . . . . . . . . . . . . 85 - D.2.2. Detect Resource Entity Tag Change . . . . . . . . . . 86 - D.3. Query Parameter Examples . . . . . . . . . . . . . . . . 87 - D.3.1. "content" Parameter . . . . . . . . . . . . . . . . . 87 - D.3.2. "depth" Parameter . . . . . . . . . . . . . . . . . . 90 - D.3.3. "select" Parameter . . . . . . . . . . . . . . . . . 93 - D.3.4. "insert" Parameter . . . . . . . . . . . . . . . . . 94 - D.3.5. "point" Parameter . . . . . . . . . . . . . . . . . . 95 - D.3.6. "limit" Parameter . . . . . . . . . . . . . . . . . . 95 - D.3.7. "offset" Parameter . . . . . . . . . . . . . . . . . 96 - D.3.8. "filter" Parameter . . . . . . . . . . . . . . . . . 97 - D.3.9. "start-time" Parameter . . . . . . . . . . . . . . . 98 - D.3.10. "stop-time" Parameter . . . . . . . . . . . . . . . . 98 - Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 98 + 4.7. DELETE . . . . . . . . . . . . . . . . . . . . . . . . . 33 + 4.8. Query Parameters . . . . . . . . . . . . . . . . . . . . 34 + 4.8.1. Query Parameter URIs . . . . . . . . . . . . . . . . 35 + 4.8.2. The "defaults" Protocol Capability URI . . . . . . . 35 + 4.8.3. The "content" Query Parameter . . . . . . . . . . . . 36 + 4.8.4. The "depth" Query Parameter . . . . . . . . . . . . . 36 + 4.8.5. The "fields" Query Parameter . . . . . . . . . . . . 37 + 4.8.6. The "insert" Query Parameter . . . . . . . . . . . . 38 + 4.8.7. The "point" Query Parameter . . . . . . . . . . . . . 38 + 4.8.8. The "filter" Query Parameter . . . . . . . . . . . . 39 + 4.8.9. The "start-time" Query Parameter . . . . . . . . . . 40 + 4.8.10. The "stop-time" Query Parameter . . . . . . . . . . . 40 + 4.8.11. The "with-defaults" Query Parameter . . . . . . . . . 41 + 5. Messages . . . . . . . . . . . . . . . . . . . . . . . . . . 42 + 5.1. Request URI Structure . . . . . . . . . . . . . . . . . . 42 + 5.2. Message Headers . . . . . . . . . . . . . . . . . . . . . 43 + 5.3. Message Encoding . . . . . . . . . . . . . . . . . . . . 44 + 5.4. RESTCONF Meta-Data . . . . . . . . . . . . . . . . . . . 45 + 5.5. Return Status . . . . . . . . . . . . . . . . . . . . . . 45 + 5.6. Message Caching . . . . . . . . . . . . . . . . . . . . . 45 + 6. Notifications . . . . . . . . . . . . . . . . . . . . . . . . 46 + 6.1. Server Support . . . . . . . . . . . . . . . . . . . . . 46 + 6.2. Event Streams . . . . . . . . . . . . . . . . . . . . . . 46 + 6.3. Subscribing to Receive Notifications . . . . . . . . . . 48 + 6.3.1. NETCONF Event Stream . . . . . . . . . . . . . . . . 49 + 6.4. Receiving Event Notifications . . . . . . . . . . . . . . 49 + 7. Error Reporting . . . . . . . . . . . . . . . . . . . . . . . 51 + 7.1. Error Response Message . . . . . . . . . . . . . . . . . 52 + 8. RESTCONF module . . . . . . . . . . . . . . . . . . . . . . . 55 + 9. RESTCONF Monitoring . . . . . . . . . . . . . . . . . . . . . 61 + 9.1. restconf-state/capabilities . . . . . . . . . . . . . . . 62 + 9.2. restconf-state/streams . . . . . . . . . . . . . . . . . 62 + 9.3. RESTCONF Monitoring Module . . . . . . . . . . . . . . . 62 + 10. YANG Module Library . . . . . . . . . . . . . . . . . . . . . 66 + 10.1. modules . . . . . . . . . . . . . . . . . . . . . . . . 66 + 10.1.1. modules/module . . . . . . . . . . . . . . . . . . . 67 + 11. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 67 + 11.1. The "restconf" Relation Type . . . . . . . . . . . . . . 67 + 11.2. YANG Module Registry . . . . . . . . . . . . . . . . . . 67 + 11.3. application/yang Media Sub Types . . . . . . . . . . . . 68 + 11.4. RESTCONF Capability URNs . . . . . . . . . . . . . . . . 69 + 12. Security Considerations . . . . . . . . . . . . . . . . . . . 70 + 13. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 71 + 14. References . . . . . . . . . . . . . . . . . . . . . . . . . 71 + 14.1. Normative References . . . . . . . . . . . . . . . . . . 71 + 14.2. Informative References . . . . . . . . . . . . . . . . . 74 + Appendix A. Change Log . . . . . . . . . . . . . . . . . . . . . 74 + A.1. 03 - 04 . . . . . . . . . . . . . . . . . . . . . . . . . 74 + A.2. 02 - 03 . . . . . . . . . . . . . . . . . . . . . . . . . 75 + A.3. 01 - 02 . . . . . . . . . . . . . . . . . . . . . . . . . 76 + A.4. 00 - 01 . . . . . . . . . . . . . . . . . . . . . . . . . 76 + A.5. bierman:restconf-04 to ietf:restconf-00 . . . . . . . . . 77 + Appendix B. Open Issues . . . . . . . . . . . . . . . . . . . . 77 + Appendix C. Example YANG Module . . . . . . . . . . . . . . . . 78 + C.1. example-jukebox YANG Module . . . . . . . . . . . . . . . 78 + Appendix D. RESTCONF Message Examples . . . . . . . . . . . . . 84 + D.1. Resource Retrieval Examples . . . . . . . . . . . . . . . 84 + D.1.1. Retrieve the Top-level API Resource . . . . . . . . . 84 + D.1.2. Retrieve The Server Module Information . . . . . . . 85 + D.1.3. Retrieve The Server Capability Information . . . . . 86 + D.2. Edit Resource Examples . . . . . . . . . . . . . . . . . 87 + D.2.1. Create New Data Resources . . . . . . . . . . . . . . 87 + D.2.2. Detect Resource Entity Tag Change . . . . . . . . . . 88 + D.3. Query Parameter Examples . . . . . . . . . . . . . . . . 89 + D.3.1. "content" Parameter . . . . . . . . . . . . . . . . . 89 + D.3.2. "depth" Parameter . . . . . . . . . . . . . . . . . . 92 + D.3.3. "fields" Parameter . . . . . . . . . . . . . . . . . 95 + D.3.4. "insert" Parameter . . . . . . . . . . . . . . . . . 96 + D.3.5. "point" Parameter . . . . . . . . . . . . . . . . . . 97 + D.3.6. "filter" Parameter . . . . . . . . . . . . . . . . . 97 + D.3.7. "start-time" Parameter . . . . . . . . . . . . . . . 98 + D.3.8. "stop-time" Parameter . . . . . . . . . . . . . . . . 98 + D.3.9. "with-defaults" Parameter . . . . . . . . . . . . . . 98 + Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 100 1. Introduction - There is a need for standard mechanisms to allow WEB applications to + There is a need for standard mechanisms to allow Web applications to access the configuration data, operational data, data-model specific protocol operations, and notification events within a networking device, in a modular and extensible manner. - This document describes an HTTP [RFC2616] based protocol called + This document describes an HTTP [RFC7230] based protocol called RESTCONF, for accessing data defined in YANG [RFC6020], using datastores defined in NETCONF [RFC6241]. The NETCONF protocol defines configuration datastores and a set of Create, Retrieve, Update, Delete (CRUD) operations that can be used to access these datastores. The YANG language defines the syntax and semantics of datastore content, operational data, protocol operations, and notification events. RESTCONF uses HTTP operations to provide CRUD operations on a NETCONF datastore containing YANG- defined data. Since NETCONF protocol operations are not relevant, @@ -191,197 +194,201 @@ be retrieved with the GET method. Resources representing configuration data can be modified with the DELETE, PATCH, POST, and PUT methods. Data is encoded with either XML [W3C.REC-xml-20081126] or JSON [RFC7158]. Data-model specific protocol operations defined with the YANG "rpc" statement can be invoked with the POST method. Data-model specific notification events defined with the YANG "notification" statement can be accessed. -1.1. Secure Transport - - RESTCONF relies on TLS [RFC2246] to provide privacy and data - integrity for its HTTP operations. More specifically, RESTCONF - requires HTTP over TLS (HTTPS) [RFC2818]. To ensure security, - RESTCONF clients MUST verify the RESTCONF server's X.509 certificate - using the path validation algorithm defined in section 6 of - [RFC5280]. Devices that do not support TLS will be unable to - implement RESTCONF. - -1.2. Simple Subset of NETCONF Functionality +1.1. Simple Subset of NETCONF Functionality The framework and meta-model used for an HTTP-based API does not need to mirror those used by the NETCONF protocol, but it needs to be - compatible with NETCONF. A simplified framework and protocol is - needed that utilizes the three NETCONF datastores (candidate, - running, startup), but hides the complexity of multiple datastores - from the client. + compatible with NETCONF. Instead, a simplified framework and + protocol is needed that co-exists with the three NETCONF datastores + (candidate, running, startup), but hides the complexity of multiple + datastores from the client. A simplified transaction model is needed that allows basic CRUD operations on a hierarchy of conceptual resources. This represents a limited subset of the transaction capabilities of the NETCONF protocol. + The HTTP POST, PUT, PATCH, and DELETE methods are used to edit data + resources represented by YANG data models. These basic edit + operations allow the running configuration to be altered in an all- + or-none fashion. This is similar to the "rollback-on-error" + capability in NETCONF. Edits are usually applied to one data + resource instance at a time. + Applications that require more complex transaction capabilities might consider NETCONF instead of RESTCONF. The following transaction features are not directly provided in RESTCONF: o datastore locking (full or partial) o candidate datastore o startup datastore o validate operation o confirmed-commit procedure RESTCONF is not intended to replace NETCONF, but rather provide an additional simplified interface that follows REST principles and is compatible with a resource-oriented device abstraction. The following figure shows the system components: +-----------+ +-----------------+ - | WEB app | <-------> | | + | Web app | <-------> | | +-----------+ HTTP | network device | | | +-----------+ | +-----------+ | | NMS app | <-------> | | datastore | | +-----------+ NETCONF | +-----------+ | +-----------------+ -1.3. Data Model Driven API +1.2. Data Model Driven API RESTCONF combines the simplicity of the HTTP protocol with the predictability and automation potential of a schema-driven API. Using YANG, a client can predict all resource endpoints, much like using URI Templates [RFC6570], but in a more holistic manner. This strategy obviates the need for responses provided by the server to contain HATEOAS links, originally described in Roy Fielding's doctoral dissertation [rest-dissertation]. - A REST client using HATEOAS principles would not use any data - modeling language to define the application-specific content of the - API. The client would discover each new child resource as it - traverses the URIs returned as Location IDs to discover the server - capabilities. This approach has 3 significant weaknesses with - regards to control of complex networking devices: + In contrast, a REST client using HATEOAS principles would not use any + data modeling language to define the application-specific content of + the API. The client would need to discover each new child resource + as it traverses the URIs to discover the server capabilities. This + approach has the following significant weaknesses with regards to + control of complex networking devices: o inefficient performance: configuration APIs will be quite complex and may require thousands of protocol messages to discover all the schema information. Typically the data type information has to be passed in the protocol messages, which is also wasteful overhead. o no data model richness: without a data model, the schema-level semantics and validation constraints are not available to the application. o no tool automation: API automation tools need some sort of content schema to function. Such tools can automate various programming and documentation tasks related to specific data models. - Data model modules such as YANG modules serve as an "API contract" - that will be honored by the server. An application designer can code - to the data model, knowing in advance important details about the - exact protocol operations and datastore content a conforming server + Data models such as YANG modules serve as an "API contract" that will + be honored by the server. An application designer can code to the + data model, knowing in advance important details about the exact + protocol operations and datastore content a conforming server implementation will support. RESTCONF provides the YANG module capability information supported by the server, in case the client wants to use it. The URIs for custom protocol operations and datastore content are predictable, based on the YANG module definitions. Operational experience with CLI and SNMP indicates that operators learn the 'location' of specific service or device related data and do not expect such information to be arbitrary and discovered each time the client opens a management session to a server. The RESTCONF protocol operates on a conceptual datastore defined with the YANG data modeling language. The server lists each YANG module - it supports under "/modules" defined in the "ietf-yang-library" YANG - module. + it supports using the "ietf-yang-library" YANG module, defined in + [I-D.ietf-netconf-yang-library]. The conceptual datastore contents, data-model-specific operations and - notification events are identified by this set of YANG module - resources. All RESTCONF content identified as either a data - resource, operation resource, or event stream resource is defined - with the YANG language. + notification events are identified by this set of YANG modules. All + RESTCONF content identified as either a data resource, operation + resource, or event stream resource is defined with the YANG language. The classification of data as configuration or non-configuration is derived from the YANG "config" statement. Data ordering behavior is derived from the YANG "ordered-by" statement. The RESTCONF datastore editing model is simple and direct, similar to the behavior of the ":writable-running" capability in NETCONF. Each RESTCONF edit of a datastore resource is activated upon successful completion of the transaction. -1.4. Terminology +1.3. Terminology The keywords "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]. -1.4.1. NETCONF +1.3.1. NETCONF The following terms are defined in [RFC6241]: o candidate configuration datastore o client - o configuration data + o configuration data o datastore o configuration datastore o protocol operation o running configuration datastore o server o startup configuration datastore o state data o user -1.4.2. HTTP - - The following terms are defined in [RFC2616]: +1.3.2. HTTP - o entity tag + The following terms are defined in [RFC3986]: o fragment - o header line + o path - o message body + o query - o method + The following terms are defined in [RFC7230]: - o path + o header - o query + o message-body - o request + o request-line o request URI - o response body + o status-line + + The following terms are defined in [RFC7231]: + + o method + + o request o resource -1.4.3. YANG + The following terms are defined in [RFC7232]: + + o entity tag + +1.3.3. YANG The following terms are defined in [RFC6020]: o container o data node o key leaf o leaf @@ -393,68 +400,72 @@ o presence container (or P-container) o RPC operation (now called protocol operation) o non-presence container (or NP-container) o ordered-by system o ordered-by user -1.4.4. Terms +1.3.4. Terms The following terms are used within this document: o API resource: a resource with the media type "application/ - yang.api+xml" or "application/yang.api+json". API resources can - only be edited by the server. - - o collection resource: a resource with the media type "application/ - yang.collection+xml" or "application/yang.collection+json". - Contains a set of data resources. + yang.api+xml" or "application/yang.api+json". o data resource: a resource with the media type "application/ yang.data+xml" or "application/yang.data+json". Containers, leafs, list entries and anyxml nodes can be data resources. o datastore resource: a resource with the media type "application/ yang.datastore+xml" or "application/yang.datastore+json". - Represents a configuration datastore. + Represents a datastore. - o edit operation: a RESTCONF operation on a data resource using the - POST, PUT, PATCH, or DELETE method. + o edit operation: a RESTCONF operation on a data resource using + either a POST, PUT, PATCH, or DELETE method. o event stream resource: This resource represents an SSE (Server- Sent Events) event stream. The content consists of text using the media type "text/event-stream", as defined by the HTML5 specification. Each event represents one message generated by the server. It contains a conceptual system or data- model specific event that is delivered within a notification event stream. Also called a "stream resource". + o media-type: HTTP uses Internet media types [RFC2046] in the + Content-Type and Accept header fields in order to provide open and + extensible data typing and type negotiation. + o operation: the conceptual RESTCONF operation for a message, - derived from the HTTP method, request URI, headers, and message + derived from the HTTP method, request URI, headers, and message- body. o operation resource: a resource with the media type "application/ yang.operation+xml" or "application/yang.operation+json". o patch: a generic PATCH request on the target datastore or data - resource. The media type of the message body content will + resource. The media type of the message-body content will identify the patch type in use. - o plain patch: a PATCH request where the media type is "application/ - yang.data+xml" or "application/yang.data+json". + o plain patch: a specific PATCH request type that can be used for + simple merge operations. o query parameter: a parameter (and its value if any), encoded within the query component of the request URI. + o RESTCONF capability: An optional RESTCONF protocol feature + supported by the server, which is identified by an IANA registered + NETCONF Capability URI, and advertised with an entry in the + "capability" leaf-list in Section 9.3. + o retrieval request: a request using the GET or HEAD methods. o target resource: the resource that is associated with a particular message, identified by the "path" component of the request URI. o unified datastore: A conceptual representation of the device running configuration. The server will hide all NETCONF datastore details for edit operations, such as the ":candidate" and ":startup" capabilities. @@ -463,191 +474,309 @@ the client with the GET method. o stream list: the set of data resource instances that describe the event stream resources available from the server. This information is defined in the "ietf-restconf-monitoring" module as the "stream" list. It can be retrieved using the target resource "{+restconf}/data/ietf-restconf-monitoring:restconf-state/streams/ stream". The stream list contains information about each stream, such as the URL to retrieve the event stream data. -1.4.5. URI Template +1.3.5. URI Template Throughout this document, the URI template [RFC6570] syntax "{+restconf}" is used to refer to the RESTCONF API entry point - outside of an example. See @path-resolution@ for details. + outside of an example. See Section 3.1 for details. - All of the examples in this document assume "/restconf" as the - discovered RESTCONF API root path. + For simplicity, all of the examples in this document assume + "/restconf" as the discovered RESTCONF API root path. -1.4.6. Tree Diagrams +1.3.6. Tree Diagrams 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 Abbreviations before data node names: "rw" means configuration data (read-write) and "ro" state data (read-only). o Symbols after data node names: "?" means an optional node, "!" means a presence container, and "*" denotes a list and leaf-list. o Parentheses enclose choice and case nodes, and case nodes are also marked with a colon (":"). o Ellipsis ("...") stands for contents of subtrees that are not shown. -2. Resources +2. Transport Protocol Requirements + +2.1. Integrity and Confidentiality + + HTTP [RFC7230] is an application layer protocol that may be layered + on any reliable transport-layer protocol. RESTCONF is defined on top + of HTTP, but due to the sensitive nature of the information conveyed, + RESTCONF requires that the transport-layer protocol provides both + data integrity and confidentiality, such as are provided by the TLS + protocol [RFC5246]. + +2.2. HTTPS with X.509v3 Certificates + + Given the nearly ubiquitous support for HTTP over TLS [RFC7230], + RESTCONF implementations MUST support the "https" URI scheme, which + has the IANA assigned default port 443. Consistent with the + exclusive use of X.509v3 certificates for NETCONF over TLS + [draft-ietf-netconf-rfc5539bis-07], use of certificates in RESTCONF + is also limited to X.509v3 certificates. + +2.3. Certificate Validation + + When presented an X.509 certificate, the RESTCONF peer MUST use X.509 + certificate path validation [RFC5280] to verify the integrity of the + certificate. The presented X.509 certificate MAY also be considered + valid if it matches a locally configured certificate fingerprint. If + X.509 certificate path validation fails and the presented X.509 + certificate does not match a locally configured certificate + fingerprint, the connection MUST be terminated as defined in + [RFC5246]. + +2.4. Authenticated Server Identity + + The RESTCONF client MUST carefully examine the certificate presented + by the RESTCONF server to determine if it meets the client's + expectations. If the RESTCONF client has external information as to + the expected identity of the RESTCONF server, the hostname check MAY + be omitted. Otherwise, the RESTCONF client MUST check its + understanding of the RESTCONF server hostname against the server's + identity as presented in the server certificate message. Matching is + performed according to the rules and guidelines defined in [RFC6125]. + If the match fails, the RESTCONF client MUST either ask for explicit + user confirmation or terminate the connection with an indication that + the RESTCONF server's identity is suspect. + +2.5. Authenticated Client Identity + + The RESTCONF server MUST authenticate the client access to any + protected resource using HTTP Authentication [RFC7235]. If the + RESTCONF client is not authenticated to access a resource, the server + MUST send a response with status code 401 (Unauthorized) and a WWW- + Authenticate header field containing at least one challenge + applicable to the target resource. The RESTCONF server MAY advertise + support for any number of authentication schemes but, in order to + ensure interoperability, the RESTCONF server MUST advertise at least + one of the following authentication schemes: + + o Basic [draft-ietf-httpauth-basicauth-update-03] + o Digest [draft-ietf-httpauth-digest-09] + + o ClientCertificate [draft-thomson-httpbis-cant-01] + + These authentication schemes are selected due to their similarity to + authentication schemes supported by NETCONF. In particular, the + Basic and Digest authentication schemes both directly provide an + identity and verification of a shared secret, much like NETCONF over + SSH, when using the SSH "password" authentication method [RFC4252]. + Similarly, the ClientCertificate authentication scheme is much like + NETCONF over TLS's use of X.509 client-certificates. When using the + ClientCertificate authentication scheme, the RESTCONF server MUST + verify the identity of the RESTCONF client using the algorithm + defined in section 7 of [draft-ietf-netconf-rfc5539bis-07]. + + The RESTCONF client identity determined from any HTTP authentication + scheme is hereafter known as the "RESTCONF username" and subject to + the NETCONF Access Control Module (NACM) [RFC6536]. + +3. Resources The RESTCONF protocol operates on a hierarchy of resources, starting - with the top-level API resource itself. Each resource represents a - manageable component within the device. + with the top-level API resource itself (Section 3.1). Each resource + represents a manageable component within the device. A resource can be considered a collection of conceptual data and the set of allowed methods on that data. It can contain nested child resources. The child resource types and methods allowed on them are data-model specific. A resource has its own media type identifier, represented by the "Content-Type" header in the HTTP response message. A resource can contain zero or more nested resources. A resource can be created and deleted independently of its parent resource, as long as the parent resource exists. - All RESTCONF resources are defined in this document except datastore - contents, protocol operations, and notification events. The syntax - and semantics for these resource types are defined in YANG modules. + All RESTCONF resources are defined in this document except specific + datastore contents, protocol operations, and notification events. + The syntax and semantics for these resource types are defined in YANG + modules. The RESTCONF resources are accessed via a set of URIs defined in this document. The set of YANG modules supported by the server will determine the data model specific operations, top-level data node resources, and notification event messages supported by the server. - The resources used in the RESTCONF protocol are identified by the - "path" component in the request URI. Each operation is performed on - a target resource. + The RESTCONF protocol does not include a resource discovery + mechanism. Instead, the definitions within the YANG modules + advertised by the server are used to construct a predictable + operation or data resource identifier. -2.1. RESTCONF Resource Types +3.1. Root Resource Discovery + + In line with the best practices defined by [RFC7320], RESTCONF + enables deployments to specify where the RESTCONF API is located. + When first connecting to a RESTCONF server, a RESTCONF client MUST + determine the root of the RESTCONF API. The client discovers this by + getting the "/.well-known/host-meta" resource ([RFC6415]) and using + the element containing the "restconf" attribute : + + Request + ------- + GET /.well-known/host-meta users HTTP/1.1 + Host: example.com + Accept: application/xrd+xml + + Response + -------- + HTTP/1.1 200 OK + Content-Type: application/xrd+xml + Content-Length: nnn + + + + + + Once discovering the RESTCONF API root, the client MUST prepend it to + any subsequent request to a RESTCONF resource. For instance, using + the "/restconf" path discovered above, the client can now determine + the operations supported by the the server; e.g. in this example a + custom "play" operation is supported: + + Request + ------- + GET /restconf/operations HTTP/1.1 + Host: example.com + Accept: application/yang.api+json + + Response + -------- + HTTP/1.1 200 OK + Date: Mon, 23 Apr 2012 17:01:00 GMT + Server: example-server + Cache-Control: no-cache + Pragma: no-cache + Last-Modified: Sun, 22 Apr 2012 01:00:14 GMT + Content-Type: application/yang.api+json + + { "operations" : { "play" : [ null ] } } + +3.2. RESTCONF Resource Types The RESTCONF protocol defines a set of application specific media types to identify each of the available resource types. The following resource types are defined in RESTCONF: - +------------+-----------------------------+ + +-----------+---------------------------------+ | Resource | Media Type | - +------------+-----------------------------+ - | API | application/yang.api | - | Collection | application/yang.collection | - | Datastore | application/yang.datastore | - | Data | application/yang.data | - | Errors | application/yang.errors | - | Operation | application/yang.operation | + +-----------+---------------------------------+ + | API | application/yang.api+xml | + | | application/yang.api+json | + | Datastore | application/yang.datastore+xml | + | | application/yang.datastore+json | + | Data | application/yang.data+xml | + | | application/yang.data+json | + | Errors | application/yang.errors+xml | + | | application/yang.errors+json | + | Operation | application/yang.operation+xml | + | | application/yang.operation+json | | Schema | application/yang | - +------------+-----------------------------+ + +-----------+---------------------------------+ RESTCONF Media Types -2.2. Resource Discovery - - A client SHOULD start by retrieving the top-level API resource, using - the entry point URI defined in Section 4.2. - - The RESTCONF protocol does not include a resource discovery - mechanism. Instead, the definitions within the YANG modules - advertised by the server are used to construct a predictable - operation or data resource identifier. - - The "depth" query parameter (see Section 3.8.3) can be used to - control how many descendant levels should be included when retrieving - child resources. This parameter can be used with the GET method to - discover child resources within a particular resource. - -2.3. API Resource +3.3. API Resource The API resource contains the state and access points for the - RESTCONF features. It is the top-level resource and has the media - type "application/yang.api+xml" or "application/yang.api+json". + RESTCONF features. It is the top-level resource located at + {+restconf} and has the media type "application/yang.api+xml" or + "application/yang.api+json". - YANG Tree Diagram for "application/yang.api" Resource Type: + YANG Tree Diagram for an API Resource: +--rw restconf +--rw data +--rw operations - The "restconf" grouping definition in the "ietf-restconf" module - defined in Section 7 is used to specify the structure and syntax of - the conceptual child resources within the API resource. + The "application/yang.api" restconf-media-type extension in the + "ietf-restconf" module defined in Section 8 is used to specify the + structure and syntax of the conceptual child resources within the API + resource. This resource has the following child resources: +----------------+--------------------------------+ | Child Resource | Description | +----------------+--------------------------------+ | data | Contains all data resources | | operations | Data-model specific operations | +----------------+--------------------------------+ RESTCONF API Resource -2.3.1. {+restconf}/data +3.3.1. {+restconf}/data This mandatory resource represents the combined configuration and operational data resources that can be accessed by a client. It cannot be created or deleted by the client. The datastore resource - type is defined in Section 2.4. + type is defined in Section 3.4. Example: This example request by the client would retrieve only the non- configuration data nodes that exist within the "library" resource, - using the "content" query parameter (see Section 3.8.2). + using the "content" query parameter (see Section 4.8.3). GET /restconf/data/example-jukebox:jukebox/library ?content=nonconfig HTTP/1.1 Host: example.com - Accept: application/yang.data+json, - application/yang.errors+json + Accept: application/yang.data+json The server might respond: HTTP/1.1 200 OK Date: Mon, 23 Apr 2012 17:01:30 GMT Server: example-server Cache-Control: no-cache Pragma: no-cache Content-Type: application/yang.data+json { "example-jukebox:library" : { "artist-count" : 42, "album-count" : 59, "song-count" : 374 } } -2.3.2. {+restconf}/operations +3.3.2. {+restconf}/operations This optional resource is a container that provides access to the data-model specific protocol operations supported by the server. The server MAY omit this resource if no data-model specific operations are advertised. Any data-model specific operations defined in the YANG modules advertised by the server MAY be available as child nodes of this resource. - Operation resources are defined in Section 2.7. + Operation resources are defined in Section 3.6. -2.4. Datastore Resource +3.4. Datastore Resource The "{+restconf}/data" subtree represents the datastore resource type, which is a collection of configuration and operational data nodes. A "unified datastore" interface is used to simplify resource editing for the client. The RESTCONF unified datastore is a conceptual interface to the native configuration datastores that are present on the device. @@ -660,60 +789,74 @@ persistence are handled by the server and not controlled by the client. A datastore resource can only be written directly with the PATCH method. Only the configuration data resources within the datastore resource can be edited directly with all methods. Each RESTCONF edit of a datastore resource is saved to non-volatile storage in an implementation-specific matter by the server. There is no guarantee that configuration changes are saved immediately, or - that the saved configuration is always a mirror of the running - configuration. + that the saved configuration is always a mirror of the NETCONF + running datastore, if the server also supports NETCONF. -2.4.1. Edit Collision Detection +3.4.1. Edit Collision Detection Two "edit collision detection" mechanisms are provided in RESTCONF, for datastore and data resources. -2.4.1.1. Timestamp +3.4.1.1. Timestamp - The last change time is maintained and the "Last-Modified" and "Date" - headers are returned in the response for a retrieval request. The - "If-Unmodified-Since" header can be used in edit operation requests - to cause the server to reject the request if the resource has been - modified since the specified timestamp. + The last change time is maintained and the "Last-Modified" + ([RFC7232], section 2.2) header is returned in the response for a + retrieval request. The "If-Unmodified-Since" header can be used in + edit operation requests to cause the server to reject the request if + the resource has been modified since the specified timestamp. - The server MUST maintain a last-modified timestamp for this resource, - and return the "Last-Modified" header when this resource is retrieved - with the GET or HEAD methods. Only changes to configuration data - resources within the datastore affect this timestamp. + The server MUST maintain a last-modified timestamp for the top-level + {+restconf}/data resource and SHOULD maintain last-modified + timestamps for descendant resources. For all resources, the server + MUST return the "Last-Modified" header when the resource is retrieved + with the GET or HEAD methods. If the server does not maintain a + timestamp for a resource, it MUST return the timestamp of the + resource's ancestor, a process that may recurse up to the top-level + {+restconf}/data resource. Only changes to configuration data + resources within the datastore affect the timestamp. -2.4.1.2. Entity tag +3.4.1.2. Entity tag - A unique opaque string is maintained and the "ETag" header is - returned in the response for a retrieval request. The "If-Match" - header can be used in edit operation requests to cause the server to - reject the request if the resource entity tag does not match the - specified value. + A unique opaque string is maintained and the "ETag" ([RFC7232], + section 2.3) header is returned in the response for a retrieval + request. The "If-Match" header can be used in edit operation + requests to cause the server to reject the request if the resource + entity tag does not match the specified value. - The server MUST maintain a resource entity tag for this resource, and - return the "ETag" header when this resource is retrieved with the GET - or HEAD methods. The resource entity tag MUST be changed to a new - previously unused value if changes to any configuration data - resources within the datastore are made. + The server MUST maintain an entity tag for the top-level + {+restconf}/data resource and SHOULD maintain entity tags for + descendant resources. For all resources, the server MUST return the + "ETag" header when the resource is retrieved with the GET or HEAD + methods. If the server does not maintain an entity tag for a + resource, it MUST return the entity tag of the resource's ancestor, a + process that may recurse up to the top-level {+restconf}/data + resource. Only changes to configuration data resources within the + datastore affect the entity tag. -2.5. Data Resource +3.5. Data Resource A data resource represents a YANG data node that is a descendant node - of a datastore resource. Containers, leafs, list entries and anyxml - nodes are data resources. + of a datastore resource. Each YANG-defined data node can be uniquely + targeted by the request-line of an HTTP operation. Containers, + leafs, list entries and anyxml nodes are data resources. + + The representation maintained for each data resource is the YANG + defined subtree for that node. HTTP operations on a data resource + affect both the targeted data node and all its descendants, if any. For configuration data resources, the server MAY maintain a last- modified timestamp for the resource, and return the "Last-Modified" header when it is retrieved with the GET or HEAD methods. If maintained, the resource timestamp MUST be set to the current time whenever the resource or any configuration resource within the resource is altered. For configuration data resources, the server MAY maintain a resource entity tag for the resource, and return the "ETag" header when it is @@ -721,58 +864,42 @@ maintained, the resource entity tag MUST be updated whenever the resource or any configuration resource within the resource is altered. A data resource can be retrieved with the GET method. Data resources are accessed via the "{+restconf}/data" entry point. This sub-tree is used to retrieve and edit data resources. A configuration data resource can be altered by the client with some or all of the edit operations, depending on the target resource and - the specific operation. Refer to Section 3 for more details on edit + the specific operation. Refer to Section 4 for more details on edit operations. The resource definition version for a data resource is identified by the revision date of the YANG module containing the YANG definition - for the data resource, specified in the "{+restconf}/modules" sub- - tree. + for the data resource. -2.5.1. Encoding YANG Instance Identifiers in the Request URI +3.5.1. Encoding Data Resource Identifiers in the Request URI In YANG, data nodes are named with an absolute XPath expression, defined in [XPath] , starting from the document root to the target - resource. In RESTCONF, URL encoded Location header expressions are - used instead. - - The YANG "instance-identifier" (i-i) data type is represented in - RESTCONF with the path expression format defined in this section. - - +-------+-------------------------------------------+ - | Name | Comments | - +-------+-------------------------------------------+ - | point | Insertion point is always a full i-i | - | path | Request URI path is a full or partial i-i | - +-------+-------------------------------------------+ - - RESTCONF instance-identifier Type Conversion - - The "path" component of the request URI contains the absolute path - expression that identifies the target resource. + resource. In RESTCONF, URL encoded path expressions are used + instead. A predictable location for a data resource is important, since applications will code to the YANG data model module, which uses static naming and defines an absolute path location for all data nodes. A RESTCONF data resource identifier is not an XPath expression. It is encoded from left to right, starting with the top-level data node, - according to the "api-path" rule in Section 2.5.1.1. The node name + according to the "api-path" rule in Section 3.5.1.1. The node name of each ancestor of the target resource node is encoded in order, ending with the node name for the target resource. If a data node in the path expression is a YANG list node, then the key values for the list (if any) MUST be encoded according to the following rules. o The key leaf values for a data resource representing a YANG list MUST be encoded using one path segment [RFC3986]. @@ -785,138 +912,131 @@ specified in the YANG "key" statement, with a comma separating them. o All the components in the "key" statement MUST be encoded. Partial instance identifiers are not supported. o Quoted strings are supported in the key leaf values. Quoted strings MUST be used to express empty strings. (example: list=foo,'',baz). - o The "list-instance" ABNF rule defined in Section 2.5.1.1 + o The "list-instance" ABNF rule defined in Section 3.5.1.1 represents the syntax of a list instance identifier. o Resource URI values returned in Location headers for data resources MUST identify the module name, even if there are no conflicting local names when the resource is created. This ensures the correct resource will be identified even if the server loads a new module that the old client does not know about. Examples: container top { list list1 { key "key1 key2 key3"; ... list list2 { key "key4 key5"; ... leaf X { type string; } } } + } For the above YANG definition, URI with key leaf values will be encoded as follows (line wrapped for display purposes only): /restconf/data/example-top:top/list1=key1val,key2val,key3val3/ list2=key4val,key5val/X -2.5.1.1. ABNF For Data Resource Identifiers +3.5.1.1. ABNF For Data Resource Identifiers The "api-path" ABNF syntax is used to construct RESTCONF path identifiers: api-path = "/" | ("/" api-identifier 0*("/" (api-identifier | list-instance ))) - api-identifier = [module-name ":"] identifier + api-identifier = [module-name ":"] identifier ;; note 1 module-name = identifier list-instance = api-identifier "=" key-value ["," key-value]* key-value = string string = ;; An identifier MUST NOT start with ;; (('X'|'x') ('M'|'m') ('L'|'l')) identifier = (ALPHA / "_") *(ALPHA / DIGIT / "_" / "-" / ".") -2.5.2. Defaults Handling + Note 1: The syntax for "api-identifier" MUST conform to the JSON + identifier encoding rules in section 4 of + [I-D.ietf-netmod-yang-json]. - NETCONF has a rather complex model for handling default values for - leafs. RESTCONF attempts to avoid this complexity by restricting the - operations that can be applied to a resource. Applications that - require full control of defaults might consider NETCONF instead of - RESTCONF. +3.5.2. Defaults Handling + + RESTCONF requires that a server report its default handling mode (see + Section 4.8.2 for details). If the optional "with-defaults" query + parameter is supported by the server, a client may use it to control + retrieval of default values (see Section 4.8.11 for details). If the target of a GET method is a data node that represents a leaf that has a default value, and the leaf has not been given a value yet, the server MUST return the default value that is in use by the server. If the target of a GET method is a data node that represents a container or list that has any child resources with default values, for the child resources that have not been given value yet, the - server MAY return the default values that are in use by the server. - -2.6. Collection Resource - - A collection resource contains a set of data resources. It is used - to represent a all instances or a subset of all instances in a YANG - list or leaf-list. - - A collection resource can be retrieved with the GET method, - optionally with the query parameters "limit" (Section 3.8.7) and - "offset" (Section 3.8.8). - - The "ietf-restconf" YANG module contains the "collection" grouping - which specifies the syntax of a collection resource. + server MAY return the default values that are in use by the server, + in accordance with its reported default handing mode and query + parameters passed by the client. -2.7. Operation Resource +3.6. Operation Resource - An operation resource represents an protocol operation defined with + An operation resource represents a protocol operation defined with the YANG "rpc" statement. All operation resources share the same module namespace as any top- level data resources, so the name of an operation resource cannot conflict with the name of a top-level data resource defined within the same module. If 2 different YANG modules define the same "rpc" identifier, then the module name MUST be used in the request URI. For example, if "module-A" and "module-B" both defined a "reset" operation, then invoking the operation from "module-A" would be requested as follows: POST /restconf/operations/module-A:reset HTTP/1.1 Server example.com Any usage of an operation resource from the same module, with the same name, refers to the same "rpc" statement definition. This behavior can be used to design protocol operations that perform the same general function on different resource types. - If the "rpc" statement has an "input" section, then a message body + If the "rpc" statement has an "input" section, then a message-body MAY be sent by the client in the request, otherwise the request - message MUST NOT include a message body. If the "rpc" statement has - an "output" section, then a message body MAY be sent by the server in - the response. Otherwise the server MUST NOT include a message body - in the response message, and MUST send a "204 No Content" Status-Line - instead. + message MUST NOT include a message-body. If the "rpc" statement has + an "output" section, then a message-body MAY be sent by the server in + the response, otherwise the response message MUST NOT include a + message-body in the response message, and MUST send a "204 No + Content" status-line instead. -2.7.1. Encoding Operation Input Parameters +3.6.1. Encoding Operation Input Parameters If the "rpc" statement has an "input" section, then the "input" node - is provided in the message body, corresponding to the YANG data + is provided in the message-body, corresponding to the YANG data definition statements within the "input" section. Example: The following YANG definition is used for the examples in this section. rpc reboot { input { leaf delay { @@ -942,24 +1062,24 @@ "language" : "en-US" } } The server might respond: HTTP/1.1 204 No Content Date: Mon, 25 Apr 2012 11:01:00 GMT Server: example-server -2.7.2. Encoding Operation Output Parameters +3.6.2. Encoding Operation Output Parameters If the "rpc" statement has an "output" section, then the "output" - node is provided in the message body, corresponding to the YANG data + node is provided in the message-body, corresponding to the YANG data definition statements within the "output" section. Example: The following YANG definition is used for the examples in this section. rpc get-reboot-info { output { leaf reboot-time { @@ -968,108 +1088,108 @@ } leaf message { type string; } leaf language { type string; } } } The client might send the following POST request message: POST /restconf/operations/example-ops:get-reboot-info HTTP/1.1 Host: example.com - Accept: application/yang.operation+json, - application/yang.errors+json + Accept: application/yang.operation+json The server might respond: HTTP/1.1 200 OK Date: Mon, 25 Apr 2012 11:10:30 GMT Server: example-server Content-Type: application/yang.operation+json { "example-ops:output" : { "reboot-time" : 30, "message" : "Going down for system maintenance", "language" : "en-US" } } -2.8. Schema Resource +3.7. Schema Resource - If the server supports the "schema" leaf within the API then the - client can retrieve the YANG schema text for the associated YANG - module or submodule, using the GET method. First the client needs to - retrieve the URL for retrieving the schema. + The server can optionally support retrieval of the YANG modules it + supports. To retrieve a YANG module, a client first needs to get the + URL for retrieving the schema. The client might send the following GET request message: GET /restconf/data/ietf-yang-library:modules/module= example-jukebox,2014-07-03/schema HTTP/1.1 Host: example.com - Accept: application/yang.data+json, - application/yang.errors+json + Accept: application/yang.data+json The server might respond: HTTP/1.1 200 OK Date: Mon, 25 Apr 2012 11:10:30 GMT Server: example-server Content-Type: application/yang.data+json { "ietf-yang-library:schema": - "http://example.com/mymodules/example-jukebox/2014-07-03" + "https://example.com/mymodules/example-jukebox/2014-07-03" } Next the client needs to retrieve the actual YANG schema. The client might send the following GET request message: - GET http://example.com/mymodules/example-jukebox/2014-07-03 + GET https://example.com/mymodules/example-jukebox/2014-07-03 HTTP/1.1 Host: example.com - Accept: application/yang, application/yang.errors+json + Accept: application/yang The server might respond: module example-jukebox { namespace "http://example.com/ns/example-jukebox"; prefix "jbox"; // rest of YANG module content deleted... } -2.9. Stream Resource +3.8. Event Stream Resource - A "stream" resource represents a source for system generated event - notifications. Each stream is created and modified by the server - only. A client can retrieve a stream resource or initiate a long- - poll server sent event stream, using the procedure specified in - Section 5.3. + An "event stream" resource represents a source for system generated + event notifications. Each stream is created and modified by the + server only. A client can retrieve a stream resource or initiate a + long-poll server sent event stream, using the procedure specified in + Section 6.3. A notification stream functions according to the NETCONF Notifications specification [RFC5277]. The available streams can be retrieved from the stream list, which specifies the syntax and semantics of a stream resource. -2.10. Errors Resource +3.9. Errors Media Type - An "errors" resource is a collection of error information that is - sent as the message body in a server response message, if an error - occurs while processing a request message. + An "errors" media type is a collection of error information that is + sent as the message-body in a server response message, if an error + occurs while processing a request message. It is not considered a + resource type because no instances can be retrieved with a GET + request. - The "ietf-restconf" YANG module contains the "errors" grouping which - specifies the syntax and semantics of an errors resource. RESTCONF - error handling behavior is defined in Section 6. + The "ietf-restconf" YANG module contains the "application/ + yang.errors" restconf-media-type extension which specifies the syntax + and semantics of an "errors" media type. RESTCONF error handling + behavior is defined in Section 7. -3. Operations +4. Operations The RESTCONF protocol uses HTTP methods to identify the CRUD operation requested for a particular resource. The following table shows how the RESTCONF operations relate to NETCONF protocol operations: +----------+-------------------------------------+ | RESTCONF | NETCONF | +----------+-------------------------------------+ @@ -1079,92 +1199,94 @@ | POST | (operation="create") | | PUT | (operation="replace") | | PATCH | (operation="merge") | | DELETE | (operation="delete") | +----------+-------------------------------------+ Table 1: CRUD Methods in RESTCONF The NETCONF "remove" operation attribute is not supported by the HTTP DELETE method. The resource must exist or the DELETE method will - fail. The PATCH method is equivalent to a "merge" operation for a - plain patch. + fail. The PATCH method is equivalent to a "merge" operation when + using a plain patch (see Section 4.6.1), other media-types may + provide more granular control. Access control mechanisms may be used to limit what operations can be used. In particular, RESTCONF is compatible with the NETCONF Access Control Model (NACM) [RFC6536], as there is a specific mapping between RESTCONF and NETCONF operations, defined in Table 1. The resource path needs to be converted internally by the server to the corresponding YANG instance-identifier. Using this information, the server can apply the NACM access control rules to RESTCONF messages. The server MUST NOT allow any operation to any resources that the client is not authorized to access. Implementation of all methods (except PATCH) are defined in - [RFC2616]. This section defines the RESTCONF protocol usage for each + [RFC7231]. This section defines the RESTCONF protocol usage for each HTTP method. -3.1. OPTIONS +4.1. OPTIONS The OPTIONS method is sent by the client to discover which methods - are supported by the server for a specific resource. If supported, - it SHOULD be implemented for all media types. + are supported by the server for a specific resource (e.g., GET, POST, + DELETE, etc.). The server SHOULD implement this method, however the same information could be extracted from the YANG modules and the RESTCONF protocol specification. If the PATCH method is supported, then the "Accept-Patch" header MUST - be supported, as defined in [RFC5789]. + be supported and returned in the response to the OPTIONS request, as + defined in [RFC5789]. -3.2. HEAD +4.2. HEAD The HEAD method is sent by the client to retrieve just the headers that would be returned for the comparable GET method, without the - response body. It is supported for all resource types, except - operation resources. + response message-body. It is supported for all resource types, + except operation resources. The request MUST contain a request URI that contains at least the entry point component. The same query parameters supported by the GET method are supported by the HEAD method. The access control behavior is enforced as if the method was GET instead of HEAD. The server MUST respond the same as if the method - was GET instead of HEAD, except that no response body is included. + was GET instead of HEAD, except that no response message-body is + included. -3.3. GET +4.3. GET The GET method is sent by the client to retrieve data and meta-data for a resource. It is supported for all resource types, except operation resources. The request MUST contain a request URI that contains at least the entry point component. The server MUST NOT return any data resources for which the user does not have read privileges. If the user is not authorized to read the target resource, an error response containing a "403 Forbidden" or - "404 Not Found" Status-Line is returned to the client. + "404 Not Found" status-line is returned to the client. If the user is authorized to read some but not all of the target resource, the unauthorized content is omitted from the response - message body, and the authorized content is returned to the client. + message-body, and the authorized content is returned to the client. Example: The client might request the response headers for a JSON representation of the "library" resource: GET /restconf/data/example-jukebox:jukebox/ library/artist=Foo%20Fighters/album HTTP/1.1 Host: example.com - Accept: application/yang.data+json, - application/yang.errors+json + Accept: application/yang.data+json The server might respond: HTTP/1.1 200 OK Date: Mon, 23 Apr 2012 17:02:40 GMT Server: example-server Content-Type: application/yang.data+json Cache-Control: no-cache Pragma: no-cache ETag: a74eefc993a2b @@ -1173,93 +1295,95 @@ { "example-jukebox:album" : [ { "name" : "Wasting Light", "genre" : "example-jukebox:alternative", "year" : 2011 } ] } -3.4. POST +4.4. POST The POST method is sent by the client to create a data resource or invoke an operation resource. The server uses the target resource media type to determine how to process the request. +-----------+------------------------------------------------+ | Type | Description | +-----------+------------------------------------------------+ | Datastore | Create a top-level configuration data resource | | Data | Create a configuration data child resource | | Operation | Invoke a protocol operation | +-----------+------------------------------------------------+ Resource Types that Support POST -3.4.1. Create Resource Mode +4.4.1. Create Resource Mode If the target resource type is a datastore or data resource, then the - POST is treated as a request to create a resource or child resource. - The message body is expected to contain the content of a child - resource to create within the parent (target resource). + POST is treated as a request to create a top-level resource or child + resource, respectively. The message-body is expected to contain the + content of a child resource to create within the parent (target + resource). The data-model for the child tree is the subtree is + defined by YANG for the child resource. The "insert" and "point" query parameters are supported by the POST method for datastore and data resource types, as specified in the - YANG definition in Section 7. + YANG definition in Section 8. - If the POST method succeeds, a "201 Created" Status-Line is returned - and there is no response message body. A "Location" header + If the POST method succeeds, a "201 Created" status-line is returned + and there is no response message-body. A "Location" header identifying the child resource that was created MUST be present in the response in this case. If the user is not authorized to create the target resource, an error - response containing a "403 Forbidden" or "404 Not Found" Status-Line + response containing a "403 Forbidden" or "404 Not Found" status-line is returned to the client. All other error responses are handled - according to the procedures defined in Section 6. + according to the procedures defined in Section 7. Example: To create a new "jukebox" resource, the client might send: POST /restconf/data HTTP/1.1 Host: example.com Content-Type: application/yang.data+json { "example-jukebox:jukebox" : [null] } If the resource is created, the server might respond as follows: HTTP/1.1 201 Created Date: Mon, 23 Apr 2012 17:01:00 GMT Server: example-server - Location: http://example.com/restconf/data/example-jukebox:jukebox + Location: https://example.com/restconf/data/example-jukebox:jukebox Last-Modified: Mon, 23 Apr 2012 17:01:00 GMT ETag: b3a3e673be2 Refer to Appendix D.2.1 for more resource creation examples. -3.4.2. Invoke Operation Mode +4.4.2. Invoke Operation Mode If the target resource type is an operation resource, then the POST - method is treated as a request to invoke that operation. The message - body (if any) is processed as the operation input parameters. Refer - to Section 2.7 for details on operation resources. + method is treated as a request to invoke that operation. The + message-body (if any) is processed as the operation input parameters. + Refer to Section 3.6 for details on operation resources. - If the POST request succeeds, a "200 OK" Status-Line is returned if - there is a response message body, and a "204 No Content" Status-Line - is returned if there is no response message body. + If the POST request succeeds, a "200 OK" status-line is returned if + there is a response message-body, and a "204 No Content" status-line + is returned if there is no response message-body. If the user is not authorized to invoke the target operation, an error response containing a "403 Forbidden" or "404 Not Found" - Status-Line is returned to the client. All other error responses are - handled according to the procedures defined in Section 6. + status-line is returned to the client. All other error responses are + handled according to the procedures defined in Section 7. Example: In this example, the client is invoking the "play" operation defined in the "example-jukebox" YANG module. A client might send a "play" request as follows: POST /restconf/operations/example-jukebox:play HTTP/1.1 Host: example.com @@ -1271,50 +1395,50 @@ "song-number" : 2 } } The server might respond: HTTP/1.1 204 No Content Date: Mon, 23 Apr 2012 17:50:00 GMT Server: example-server -3.5. PUT +4.5. PUT The PUT method is sent by the client to create or replace the target resource. The only target resource media type that supports PUT is the data - resource. The message body is expected to contain the content used + resource. The message-body is expected to contain the content used to create or replace the target resource. - The "insert" (Section 3.8.5) and "point" (Section 3.8.6) query + The "insert" (Section 4.8.6) and "point" (Section 4.8.7) query parameters are supported by the PUT method for data resources. - Consistent with [RFC2616], if the PUT request creates a new resource, - a "201 Created" Status-Line is returned. If an existing resource is + Consistent with [RFC7231], if the PUT request creates a new resource, + a "201 Created" status-line is returned. If an existing resource is modified, either "200 OK" or "204 No Content" are returned. If the user is not authorized to create or replace the target resource an error response containing a "403 Forbidden" or "404 Not - Found" Status-Line is returned to the client. All other error + Found" status-line is returned to the client. All other error responses are handled according to the procedures defined in - Section 6. + Section 7. Example: An "album" child resource defined in the "example-jukebox" YANG module is replaced or created if it does not already exist. To replace the "album" resource contents, the client might send as - follows. Note that the request URI header line is wrapped for - display purposes only: + follows. Note that the request-line is wrapped for display purposes + only: PUT /restconf/data/example-jukebox:jukebox/ library/artist=Foo%20Fighters/album=Wasting%20Light HTTP/1.1 Host: example.com Content-Type: application/yang.data+json { "example-jukebox:album" : { "name" : "Wasting Light", "genre" : "example-jukebox:alternative", @@ -1323,56 +1447,71 @@ } If the resource is updated, the server might respond: HTTP/1.1 204 No Content Date: Mon, 23 Apr 2012 17:04:00 GMT Server: example-server Last-Modified: Mon, 23 Apr 2012 17:04:00 GMT ETag: b27480aeda4c -3.6. PATCH +4.6. PATCH RESTCONF uses the HTTP PATCH method defined in [RFC5789] to provide an extensible framework for resource patching mechanisms. It is optional to implement by the server. Each patch type needs a unique media type. Zero or more PATCH media types MAY be supported by the - server. + server. The media types supported by a server can be discovered by + the client by sending an OPTIONS request (see Section 4.1). - A plain patch is used to create or update a child resource within the - target resource. If the target resource instance does not exist, the - server MUST NOT create it. + If the target resource instance does not exist, the server MUST NOT + create it. - If the PATCH request succeeds, a "200 OK" Status-Line is returned if - there is a message body, and "204 No Content" is returned if no - response message body is sent. + If the PATCH request succeeds, a "200 OK" status-line is returned if + there is a message-body, and "204 No Content" is returned if no + response message-body is sent. If the user is not authorized to alter the target resource an error - response containing a "403 Forbidden" or "404 Not Found" Status-Line + response containing a "403 Forbidden" or "404 Not Found" status-line is returned to the client. All other error responses are handled - according to the procedures defined in Section 6. + according to the procedures defined in Section 7. + +4.6.1. Plain Patch + + The plain patch mechanism merges the contents of the message body + with the target resource. If the target resource is a datastore + resource (see Section 3.4), the message body MUST be either + application/yang.datastore+xml or application/yang.datastore+json. + If then the target resource is a data resource (see Section 3.5), + then the message body MUST be either application/yang.data+xml or + application/yang.data+json. + + Plain patch can used to create or update, but not delete, a child + resource within the target resource. Please see + [I-D.ietf-netconf-yang-patch] for an alternate media-type supporting + more granular control. Example: To replace just the "year" field in the "album" resource (instead of replacing the entire resource with the PUT method), the client might - send a plain patch as follows. Note that the request URI header line - is wrapped for display purposes only: + send a plain patch as follows. Note that the request-line is wrapped + for display purposes only: PATCH /restconf/data/example-jukebox:jukebox/ library/artist=Foo%20Fighters/album=Wasting%20Light HTTP/1.1 Host: example.com + If-Match: b8389233a4c Content-Type: application/yang.data+json { "example-jukebox:album" : { - "genre" : "example-jukebox:rock", "year" : 2011 } } If the field is updated, the server might respond: HTTP/1.1 204 No Content Date: Mon, 23 Apr 2012 17:49:30 GMT Server: example-server Last-Modified: Mon, 23 Apr 2012 17:49:30 GMT @@ -1380,113 +1519,148 @@ The XML encoding for the same request might be: PATCH /restconf/data/example-jukebox:jukebox/ library/artist=Foo%20Fighters/album=Wasting%20Light HTTP/1.1 Host: example.com If-Match: b8389233a4c Content-Type: application/yang.data+xml - example-jukebox:rock 2011 -3.7. DELETE +4.7. DELETE The DELETE method is used to delete the target resource. If the - DELETE request succeeds, a "204 No Content" Status-Line is returned, - and there is no response message body. + DELETE request succeeds, a "204 No Content" status-line is returned, + and there is no response message-body. If the user is not authorized to delete the target resource then an error response containing a "403 Forbidden" or "404 Not Found" - Status-Line is returned to the client. All other error responses are - handled according to the procedures defined in Section 6. + status-line is returned to the client. All other error responses are + handled according to the procedures defined in Section 7. Example: To delete a resource such as the "album" resource, the client might send: DELETE /restconf/data/example-jukebox:jukebox/ library/artist=Foo%20Fighters/album=Wasting%20Light HTTP/1.1 Host: example.com If the resource is deleted, the server might respond: HTTP/1.1 204 No Content Date: Mon, 23 Apr 2012 17:49:40 GMT Server: example-server -3.8. Query Parameters +4.8. Query Parameters Each RESTCONF operation allows zero or more query parameters to be present in the request URI. The specific parameters that are allowed depends on the resource type, and sometimes the specific target resource used, in the request. - +------------+----------+-------------------------------------------+ + +---------------+---------+-----------------------------------------+ | Name | Methods | Description | - +------------+----------+-------------------------------------------+ + +---------------+---------+-----------------------------------------+ | content | GET | Select config and/or non-config data | | | | resources | | depth | GET | Request limited sub-tree depth in the | | | | reply content | - | filter | GET | Boolean notification filter for event- | + | fields | GET | Request a subset of the target resource | + | | | contents | + | filter | GET | Boolean notification filter for event | | | | stream resources | | insert | POST, | Insertion mode for user-ordered data | | | PUT | resources | - | limit | GET | Number of entries to return for | - | | | collection resources | - | offset | GET | Starting point for collection resources | | point | POST, | Insertion point for user-ordered data | | | PUT | resources | - | select | GET | Request a subset of the target resource | - | | | contents | - | start-time | GET | Replay buffer start time for event-stream | - | | | resources | - | stop-time | GET | Replay buffer stop time for event-stream | - | | | resources | - +------------+----------+-------------------------------------------+ + | start-time | GET | Replay buffer start time for event | + | | | stream resources | + | stop-time | GET | Replay buffer stop time for event | + | | | stream resources | + | with-defaults | GET | Control retrieval of default values | + +---------------+---------+-----------------------------------------+ RESTCONF Query Parameters Query parameters can be given in any order. Each parameter can appear at most once in a request URI. A default value may apply if the parameter is missing. Refer to Appendix D.3 for examples of query parameter usage. If vendors define additional query parameters, they SHOULD use a prefix (such as the enterprise or organization name) for query parameter names in order to avoid collisions with other parameters. -3.8.1. Query Parameter URIs +4.8.1. Query Parameter URIs - A new set of NETCONF Capability URNs are defined to identify the - specific query parameters supported by the server. + A new set of RESTCONF Capability URIs are defined to identify the + specific query parameters and protocol features supported by the + server. - +---------+-------------------------------------------------+ + +--------------+----------------------------------------------------+ | Name | URI | - +---------+-------------------------------------------------+ - | content | urn:ietf:params:restconf:capability:content:1.0 | + +--------------+----------------------------------------------------+ + | defaults | urn:ietf:params:restconf:capability:defaults:1.0 | | depth | urn:ietf:params:restconf:capability:depth:1.0 | + | fields | urn:ietf:params:restconf:capability:fields:1.0 | | filter | urn:ietf:params:restconf:capability:filter:1.0 | | insert | urn:ietf:params:restconf:capability:insert:1.0 | - | page | urn:ietf:params:restconf:capability:page:1.0 | - | select | urn:ietf:params:restconf:capability:select:1.0 | | replay | urn:ietf:params:restconf:capability:replay:1.0 | - +---------+-------------------------------------------------+ + | with- | urn:ietf:params:restconf:capability:with- | + | defaults | defaults:1.0 | + +--------------+----------------------------------------------------+ RESTCONF Query Parameter URIs -3.8.2. The "content" Query Parameter +4.8.2. The "defaults" Protocol Capability URI + + This URI identifies the defaults handling mode that is used by the + server for processing default leafs in the unified datastore. A + parameter named "basic-mode" is required for this capability URI. + The "basic-mode" definitions are specified in the "With-Defaults + Capability for NETCONF" [RFC6243]. + + This protocol capability URI MUST be supported by the server, and the + MUST be listed in the "capability" leaf-list in Section 9.3. + + +------------+------------------------------------------------------+ + | Value | Description | + +------------+------------------------------------------------------+ + | report-all | No data nodes are considered default | + | trim | Values set to the YANG default-stmt value are | + | | default | + | explicit | Values set by the client are never considered | + | | default | + +------------+------------------------------------------------------+ + If the "basic-mode" is set to "report-all" then the server MUST + adhere to the defaults handling behavior defined in section 2.1 of + [RFC6243]. + + If the "basic-mode" is set to "trim" then the server MUST adhere to + the defaults handling behavior defined in section 2.2 of [RFC6243]. + + If the "basic-mode" is set to "explicit" then the server MUST adhere + to the defaults handling behavior defined in section 2.3 of + [RFC6243]. + + Example: (split for display purposes only) + + urn:ietf:params:restconf:capability:defaults:1.0? + basic-mode=explicit + +4.8.3. The "content" Query Parameter The "content" parameter controls how descendant nodes of the requested data nodes will be processed in the reply. The allowed values are: +-----------+-----------------------------------------------------+ | Value | Description | +-----------+-----------------------------------------------------+ | config | Return only configuration descendant data nodes | @@ -1496,25 +1670,23 @@ This parameter is only allowed for GET methods on datastore and data resources. A 400 Bad Request error is returned if used for other methods or resource types. The default value is determined by the "config" statement value of the requested data nodes. If the "config" value is "false", then the default for the "content" parameter is "nonconfig". If "config" is "true" then the default for the "content" parameter is "config". - If this query parameter is supported by the server, then the - "content" query parameter URI MUST be listed in the "capability" - leaf-list in Section 8.3. + This query parameter MUST be supported by the server. -3.8.3. The "depth" Query Parameter +4.8.4. The "depth" Query Parameter The "depth" parameter is used to specify the number of nest levels returned in a response for a GET method. The first nest-level consists of the requested data node itself. Any child nodes which are contained within a parent node have a depth value that is 1 greater than its parent. The value of the "depth" parameter is either an integer between 1 and 65535, or the string "unbounded". "unbounded" is the default. @@ -1522,58 +1694,58 @@ data resources. A 400 Bad Request error is returned if it used for other methods or resource types. By default, the server will include all sub-resources within a retrieved resource, which have the same resource type as the requested resource. Only one level of sub-resources with a different media type than the target resource will be returned. If this query parameter is supported by the server, then the "depth" query parameter URI MUST be listed in the "capability" leaf-list in - Section 8.3. + Section 9.3. -3.8.4. The "select" Query Parameter +4.8.5. The "fields" Query Parameter - The "select" query parameter is used to optionally identify data + The "fields" query parameter is used to optionally identify data nodes within the target resource to be retrieved in a GET method. The client can use this parameter to retrieve a subset of all nodes in a resource. - A value of the "select" query parameter matches the following rule: + A value of the "fields" query parameter matches the following rule: - select-expr = path '(' select-expr / '*' ')' / - path ';' select-expr / + fields-expr = path '(' fields-expr / '*' ')' / + path ';' fields-expr / path path = api-identifier [ '/' path ] - "api-identifier" is defined in Section 2.5.1.1. + "api-identifier" is defined in Section 3.5.1.1. ";" is used to select multiple nodes. For example, to retrieve only - the "genre" and "year" of an album, use: "select=genre;year". + the "genre" and "year" of an album, use: "fields=genre;year". Parentheses are used to specify sub-selectors of a node. For example, to retrieve only the "label" and "catalogue-number" of an - album, use: "select=admin(label;catalogue-number)". + album, use: "fields=admin(label;catalogue-number)". "/" is used in a path to retrieve a child node of a node. For example, to retrieve only the "label" of an album, use: - "select=admin/label". + "fields=admin/label". This parameter is only allowed for GET methods on api, datastore, and data resources. A 400 Bad Request error is returned if used for other methods or resource types. - If this query parameter is supported by the server, then the "select" + If this query parameter is supported by the server, then the "fields" query parameter URI MUST be listed in the "capability" leaf-list in - Section 8.3. + Section 9.3. -3.8.5. The "insert" Query Parameter +4.8.6. The "insert" Query Parameter The "insert" parameter is used to specify how a resource should be inserted within a user-ordered list. The allowed values are: +--------+----------------------------------------------------------+ | Value | Description | +--------+----------------------------------------------------------+ | first | Insert the new data as the new first entry. | @@ -1590,77 +1762,49 @@ also only supported if the target resource is a data resource, and that data represents a YANG list or leaf-list that is ordered by the user. If the values "before" or "after" are used, then a "point" query parameter for the insertion parameter MUST also be present, or a 400 Bad Request error is returned. If this query parameter is supported by the server, then the "insert" query parameter URI MUST be listed in the "capability" leaf-list in - Section 8.3. The "point" query parameter MUST also be supported by + Section 9.3. The "point" query parameter MUST also be supported by the server. -3.8.6. The "point" Query Parameter +4.8.7. The "point" Query Parameter The "point" parameter is used to specify the insertion point for a data resource that is being created or moved within a user ordered list or leaf-list. The value of the "point" parameter is of type "data-resource-identifier", defined in the "ietf-restconf" YANG - module Section 7. + module Section 8. This parameter is only supported for the POST and PUT methods. It is also only supported if the target resource is a data resource, and that data represents a YANG list or leaf-list that is ordered by the user. If the "insert" query parameter is not present, or has a value other than "before" or "after", then a 400 Bad Request error is returned. This parameter contains the instance identifier of the resource to be used as the insertion point for a POST or PUT method. If the server includes the "insert" query parameter URI in the - "capability" leaf-list in Section 8.3, then the "point" query - parameter MUST be supported. - -3.8.7. The "limit" Query Parameter - - The "limit" parameter is used to restrict the number of data - resources to return in response to GET requests on collection - resources. - - The value of the "limit" parameter is either an integer greater than - or equal to 1, or the string "unbounded". The string "unbounded" is - the default value. - - If the server includes the "page" query parameter URI in the - "capability" leaf-list in Section 8.3, then the "limit" query - parameter MUST be supported. - -3.8.8. The "offset" Query Parameter - - The "offset" parameter is used to specify the first data resource to - return in response to GET requests on collection resources. - Resources instances are numbered with consecutive integers from 1 to - the number of resource instances. - - The value of the "offset" parameter is an integer greater than or - equal to 1. The default value is 1. - - If the server includes the "page" query parameter URI in the - "capability" leaf-list in Section 8.3, then the "offset" query + "capability" leaf-list in Section 9.3, then the "point" query parameter MUST be supported. -3.8.9. The "filter" Query Parameter +4.8.8. The "filter" Query Parameter The "filter" parameter is used to indicate which subset of all possible events are of interest. If not present, all events not precluded by other parameters will be sent. This parameter is only allowed for GET methods on a text/event-stream data resource. A 400 Bad Request error is returned if used for other methods or resource types. The format of this parameter is an XPath 1.0 expression, and is @@ -1678,23 +1822,23 @@ o The context node is the root node. The filter is used as defined in [RFC5277], section 3.6. If the boolean result of the expression is true when applied to the conceptual "notification" document root, then the notification event is delivered to the client. If this query parameter is supported by the server, then the "filter" query parameter URI MUST be listed in the "capability" leaf-list in - Section 8.3. + Section 9.3. -3.8.10. The "start-time" Query Parameter +4.8.9. The "start-time" Query Parameter The "start-time" parameter is used to trigger the notification replay feature and indicate that the replay should start at the time specified. If the stream does not support replay, per the "replay-support" attribute returned by stream list entry for the stream resource, then the server MUST return the HTTP error code 400 Bad Request. The value of the "start-time" parameter is of type "date-and-time", defined in the "ietf-yang" YANG module [RFC6991]. @@ -1704,62 +1848,108 @@ methods or resource types. If this parameter is not present, then a replay subscription is not being requested. It is not valid to specify start times that are later than the current time. If the value specified is earlier than the log can support, the replay will begin with the earliest available notification. If this query parameter is supported by the server, then the "replay" query parameter URI MUST be listed in the "capability" leaf-list in - Section 8.3. The "stop-time" query parameter MUST also be supported + Section 9.3. The "stop-time" query parameter MUST also be supported by the server. If the "replay-support" leaf is present in the "stream" entry - (defined in Section 8.3) then the server MUST support the + (defined in Section 9.3) then the server MUST support the "start-time" and "stop-time" query parameters for that stream. -3.8.11. The "stop-time" Query Parameter +4.8.10. The "stop-time" Query Parameter The "stop-time" parameter is used with the replay feature to indicate the newest notifications of interest. This parameter MUST be used with and have a value later than the "start-time" parameter. The value of the "stop-time" parameter is of type "date-and-time", defined in the "ietf-yang" YANG module [RFC6991]. This parameter is only allowed for GET methods on a text/event-stream data resource. A 400 Bad Request error is returned if used for other methods or resource types. If this parameter is not present, the notifications will continue until the subscription is terminated. Values in the future are valid. If this query parameter is supported by the server, then the "replay" query parameter URI MUST be listed in the "capability" leaf-list in - Section 8.3. The "start-time" query parameter MUST also be supported + Section 9.3. The "start-time" query parameter MUST also be supported by the server. If the "replay-support" leaf is present in the "stream" entry - (defined in Section 8.3) then the server MUST support the + (defined in Section 9.3) then the server MUST support the "start-time" and "stop-time" query parameters for that stream. -4. Messages +4.8.11. The "with-defaults" Query Parameter + + The "with-defaults" parameter is used to specify how information + about default data nodes should be returned in response to GET + requests on data resources. + + If the server supports this capability, then it MUST implement the + behavior in section 4.5.1 of [RFC6243], except applied to the + RESTCONF GET operation, instead of the NETCONF operations. + + +-------------------+-----------------------------------------------+ + | Value | Description | + +-------------------+-----------------------------------------------+ + | report-all | All data nodes are reported | + | trim | Data nodes set to the YANG default are not | + | | reported | + | explicit | Data nodes set by the client are not reported | + | report-all-tagged | All data nodes are reported and defaults are | + | | tagged | + +-------------------+-----------------------------------------------+ + + If the "with-defaults" parameter is set to "report-all" then the + server MUST adhere to the defaults reporting behavior defined in + section 3.1 of [RFC6243]. + + If the "with-defaults" parameter is set to "trim" then the server + MUST adhere to the defaults reporting behavior defined in section 3.2 + of [RFC6243]. + + If the "with-defaults" parameter is set to "explicit" then the server + MUST adhere to the defaults reporting behavior defined in section 3.3 + of [RFC6243]. + + If the "with-defaults" parameter is set to "report-all-tagged" then + the server MUST adhere to the defaults reporting behavior defined in + section 3.4 of [RFC6243]. + + If the "with-defaults" parameter is not present then the server MUST + adhere to the defaults reporting behavior defined in its "basic-mode" + parameter for the "defaults" protocol capability URI, defined in + Section 4.8.2. + + If the server includes the "with-defaults" query parameter URI in the + "capability" leaf-list in Section 9.3, then the "with-defaults" query + parameter MUST be supported. + +5. Messages The RESTCONF protocol uses HTTP entities for messages. A single HTTP message corresponds to a single protocol method. Most messages can perform a single task on a single resource, such as retrieving a resource or editing a resource. The exception is the PATCH method, which allows multiple datastore edits within a single message. -4.1. Request URI Structure +5.1. Request URI Structure Resources are represented with URIs following the structure for generic URIs in [RFC3986]. A RESTCONF operation is derived from the HTTP method and the request URI, using the following conceptual fields: //?# ^ ^ ^ ^ ^ @@ -1768,111 +1958,62 @@ M M O O I M=mandatory, O=optional, I=ignored replaced by client with real values o method: the HTTP method identifying the RESTCONF operation requested by the client, to act upon the target resource specified in the request URI. RESTCONF operation details are described in - Section 3. + Section 4. o entry: the root of the RESTCONF API configured on this HTTP server, discovered by getting the ".well-known/host-meta" - resource, as described in Section 4.2. + resource, as described in Section 3.1. o resource: the path expression identifying the resource that is being accessed by the operation. If this field is not present, then the target resource is the API itself, represented by the media type "application/yang.api". o query: the set of parameters associated with the RESTCONF message. These have the familiar form of "name=value" pairs. All query parameters are optional to implement by the server and optional to use by the client. Each query parameter is identified by a URI. The server MUST list the query parameter URIs it supports in the - "capabilities" list defined in Section 8.3. + "capabilities" list defined in Section 9.3. There is a specific set of parameters defined, although the server MAY choose to support query parameters not defined in this document. The contents of the any query parameter value MUST be encoded according to [RFC2396], section 3.4. Any reserved characters MUST be encoded with escape sequences, according to [RFC2396], section 2.4. o fragment: This field is not used by the RESTCONF protocol. When new resources are created by the client, a "Location" header is returned, which identifies the path of the newly created resource. The client MUST use this exact path identifier to access the resource once it has been created. The "target" of an operation is a resource. The "path" field in the request URI represents the target resource for the operation. -4.2. RESTCONF Path Resolution - - In line the best practices defined by [get-off-my-lawn], RESTCONF - enables deployments to specify where the RESTCONF API is located. - When first connecting to a RESTCONF server, a RESTCONF client MUST - determine the root of the RESTCONF API. The client discovers this by - getting the "/.well-known/host-meta" resource ([RFC6415]) and using - the element containing the "restconf" attribute : - - Request - ------- - GET /.well-known/host-meta users HTTP/1.1 - Host: example.com - Accept: application/xrd+xml - - Response - -------- - HTTP/1.1 200 OK - Content-Type: application/xrd+xml - Content-Length: nnn - - - - - - Once discovering the RESTCONF API root, the client MUST prepend it to - any subsequent request to a RESTCONF resource. For instance, using - the "/restconf" path discovered above, the client can now determine - the operations supported by the the server: - - Request - ------- - GET /restconf/operations HTTP/1.1 - Host: example.com - Accept: application/yang.api+json, - application/yang.errors+json - - Response - -------- - HTTP/1.1 200 OK - Date: Mon, 23 Apr 2012 17:01:00 GMT - Server: example-server - Cache-Control: no-cache - Pragma: no-cache - Last-Modified: Sun, 22 Apr 2012 01:00:14 GMT - Content-Type: application/yang.api+json - - { "operations" : { "play" : [ null ] } } - -4.3. Message Headers +5.2. Message Headers There are several HTTP header lines utilized in RESTCONF messages. Messages are not limited to the HTTP headers listed in this section. HTTP defines which header lines are required for particular circumstances. Refer to each operation definition section in - Section 3 for examples on how particular headers are used. + Section 4 for examples on how particular headers are used. There are some request headers that are used within RESTCONF, usually applied to data resources. The following tables summarize the headers most relevant in RESTCONF message requests: +---------------------+---------------------------------------------+ | Name | Description | +---------------------+---------------------------------------------+ | Accept | Response Content-Types that are acceptable | | Content-Type | The media type of the request body | @@ -1888,183 +2029,181 @@ RESTCONF Request Headers The following tables summarize the headers most relevant in RESTCONF message responses: +---------------+---------------------------------------------------+ | Name | Description | +---------------+---------------------------------------------------+ | Allow | Valid actions when 405 error returned | | Cache-Control | The cache control parameters for the response | - | Content-Type | The media type of the response body | + | Content-Type | The media type of the response message-body | | Date | The date and time the message was sent | | ETag | An identifier for a specific version of a | | | resource | | Last-Modified | The last modified date and time of a resource | | Location | The resource identifier for a newly created | | | resource | +---------------+---------------------------------------------------+ RESTCONF Response Headers -4.4. Message Encoding +5.3. Message Encoding - RESTCONF messages are encoded in HTTP according to RFC 2616. The + RESTCONF messages are encoded in HTTP according to [RFC7230]. The "utf-8" character set is used for all messages. RESTCONF message - content is sent in the HTTP message body. + content is sent in the HTTP message-body. Content is encoded in either JSON or XML format. A server MUST support XML encoding and MAY support JSON encoding. XML encoding rules for data nodes are defined in [RFC6020]. The same encoding rules are used for all XML content. JSON encoding rules are defined - in [I-D.ietf-netmod-json]. This encoding is valid JSON, but also has - special encoding rules to identify module namespaces and provide - consistent type processing of YANG data. + in [I-D.ietf-netmod-yang-json]. This encoding is valid JSON, but + also has special encoding rules to identify module namespaces and + provide consistent type processing of YANG data. Request input content encoding format is identified with the Content- - Type header. This field MUST be present if a message body is sent by + Type header. This field MUST be present if a message-body is sent by the client. Response output content encoding format is identified with the Accept header in the request, or if is not specified, the request input encoding format is used. If there was no request input, then the default output encoding is XML. File extensions encoded in the request are not used to identify format encoding. -4.5. RESTCONF Meta-Data +5.4. RESTCONF Meta-Data The RESTCONF protocol needs to retrieve the same meta-data that is used in the NETCONF protocol. Information about default leafs, last- modified timestamps, etc. are commonly used to annotate representations of the datastore contents. This meta-data is not defined in the YANG schema because it applies to the datastore, and is common across all data nodes. This information is encoded as attributes in XML. JSON encoding of meta-data is defined in [I-D.lhotka-netmod-yang-metadata]. -4.6. Return Status +5.5. Return Status Each message represents some sort of resource access. An HTTP - "Status-Line" header line is returned for each request. If a 4xx or - 5xx range status code is returned in the Status-Line, then the error + "status-line" header line is returned for each request. If a 4xx or + 5xx range status code is returned in the status-line, then the error information will be returned in the response, according to the format - defined in Section 6.1. + defined in Section 7.1. -4.7. Message Caching +5.6. Message Caching Since the datastore contents change at unpredictable times, responses from a RESTCONF server generally SHOULD NOT be cached. The server SHOULD include a "Cache-Control" header in every response that specifies whether the response should be cached. A "Pragma" header specifying "no-cache" MAY also be sent in case the "Cache-Control" header is not supported. Instead of using HTTP caching, the client SHOULD track the "ETag" and/or "Last-Modified" headers returned by the server for the datastore resource (or data resource if the server supports it). A retrieval request for a resource can include the "If-None-Match" and/ or "If-Modified-Since" headers, which will cause the server to return - a "304 Not Modified" Status-Line if the resource has not changed. + a "304 Not Modified" status-line if the resource has not changed. The client MAY use the HEAD method to retrieve just the message headers, which SHOULD include the "ETag" and "Last-Modified" headers, if this meta-data is maintained for the target resource. -5. Notifications +6. Notifications The RESTCONF protocol supports YANG-defined event notifications. The solution preserves aspects of NETCONF Event Notifications [RFC5277] while utilizing the Server-Sent Events [W3C.CR-eventsource-20121211] transport strategy. -5.1. Server Support +6.1. Server Support A RESTCONF server is not required to support RESTCONF notifications. Clients may determine if a server supports RESTCONF notifications by using the HTTP operation OPTIONS, HEAD, or GET on the stream list. - The server does not support RESTCONF notifications if an HTTP error code is returned (e.g., 404 Not Found). -5.2. Event Streams +6.2. Event Streams A RESTCONF server that supports notifications will populate a stream resource for each notification delivery service access point. A RESTCONF client can retrieve the list of supported event streams from a RESTCONF server using the GET operation on the stream list. The "restconf-state/streams" container definition in the - "ietf-restconf-monitoring" module (defined in Section 8.3) is used to + "ietf-restconf-monitoring" module (defined in Section 9.3) is used to specify the structure and syntax of the conceptual child resources within the "streams" resource. For example: The client might send the following request: GET /restconf/data/ietf-restconf-monitoring:restconf-state/ streams HTTP/1.1 Host: example.com - Accept: application/yang.data+xml, - application/yang.errors+xml + Accept: application/yang.data+xml The server might send the following response: HTTP/1.1 200 OK Content-Type: application/yang.api+xml NETCONF default NETCONF event stream true 2007-07-08T00:00:00Z xml - http://example.com/streams/NETCONF + https://example.com/streams/NETCONF json - http://example.com/streams/NETCONF-JSON + https://example.com/streams/NETCONF-JSON SNMP SNMP notifications false xml - http://example.com/streams/SNMP + https://example.com/streams/SNMP syslog-critical Critical and higher severity true 2007-07-01T00:00:00Z xml - http://example.com/streams/syslog-critical + https://example.com/streams/syslog-critical -5.3. Subscribing to Receive Notifications +6.3. Subscribing to Receive Notifications RESTCONF clients can determine the URL for the subscription resource (to receive notifications) by sending an HTTP GET request for the "events" leaf with the stream list entry. The value returned by the server can be used for the actual notification subscription. The client will send an HTTP GET request for the URL returned by the server with the "Accept" type "text/event-stream". The server will treat the connection as an event stream, using the @@ -2073,31 +2212,30 @@ The server MAY support query parameters for a GET method on this resource. These parameters are specific to each notification stream. For example: The client might send the following request: GET /restconf/data/ietf-restconf-monitoring:restconf-state/ streams/stream=NETCONF/encoding=xml/events HTTP/1.1 Host: example.com - Accept: application/yang.data+xml, - application/yang.errors+xml + Accept: application/yang.data+xml The server might send the following response: HTTP/1.1 200 OK Content-Type: application/yang.api+xml - http://example.com/streams/NETCONF + https://example.com/streams/NETCONF The RESTCONF client can then use this URL value to start monitoring the event stream: GET /streams/NETCONF HTTP/1.1 Host: example.com Accept: text/event-stream Cache-Control: no-cache Connection: keep-alive @@ -2105,53 +2243,58 @@ A RESTCONF client MAY request the server compress the events using the HTTP header field "Accept-Encoding". For instance: GET /streams/NETCONF HTTP/1.1 Host: example.com Accept: text/event-stream Cache-Control: no-cache Connection: keep-alive Accept-Encoding: gzip, deflate -5.3.1. NETCONF Event Stream +6.3.1. NETCONF Event Stream The server SHOULD support the "NETCONF" notification stream defined in [RFC5277]. For this stream, RESTCONF notification subscription requests MAY specify parameters indicating the events it wishes to receive. These query parameters are optional to implement, and only available if the server supports them. +------------+---------+-------------------------+ | Name | Section | Description | +------------+---------+-------------------------+ - | start-time | 3.8.10 | replay event start time | - | stop-time | 3.8.11 | replay event stop time | - | filter | 3.8.9 | boolean content filter | + | start-time | 4.8.9 | replay event start time | + | stop-time | 4.8.10 | replay event stop time | + | filter | 4.8.8 | boolean content filter | +------------+---------+-------------------------+ NETCONF Stream Query Parameters The semantics and syntax for these query parameters are defined in the sections listed above. The YANG encoding MUST be converted to URL-encoded string for use in the request URI. - Refer to Appendix D.3.8 for filter parameter examples. + Refer to Appendix D.3.6 for filter parameter examples. -5.4. Receiving Event Notifications +6.4. Receiving Event Notifications RESTCONF notifications are encoded according to the definition of the event stream. The NETCONF stream defined in [RFC5277] is encoded in XML format. The structure of the event data is based on the "notification" element definition in section 4 of [RFC5277]. It MUST conform to the - "notification" YANG container definition in Section 7. + schema for the "notification" element in section 4 of [RFC5277], + except the XML namespace for this element is defined as: + + urn:ietf:params:xml:ns:yang:ietf-restconf + + For JSON encoding purposes, the module name is "ietf-restconf". An example SSE notification encoded using XML: data: data: 2013-12-21T00:01:00Z data: data: fault data: data: Ethernet0 @@ -2197,39 +2340,39 @@ and, if it does, RESTCONF clients SHOULD use it. A RESTCONF server SHOULD NOT send the "event" or "id" fields, as there are no meaningful values that could be used for them that would not be redundant to the contents of the notification itself. RESTCONF servers that do not send the "id" field also do not need to support the HTTP header "Last-Event-Id". RESTCONF servers that do send the "id" field MUST still support the "startTime" query parameter as the preferred means for a client to specify where to restart the event stream. -6. Error Reporting +7. Error Reporting - HTTP Status-Lines are used to report success or failure for RESTCONF + HTTP status-lines are used to report success or failure for RESTCONF operations. The element returned in NETCONF error responses contains some useful information. This error information is adapted for use in RESTCONF, and error information is returned for "4xx" class of status codes. The following table summarizes the return status codes used specifically by RESTCONF operations: +---------------------------+---------------------------------------+ | Status-Line | Description | +---------------------------+---------------------------------------+ | 100 Continue | POST accepted, 201 should follow | - | 200 OK | Success with response body | + | 200 OK | Success with response message-body | | 201 Created | POST to create a resource success | | 202 Accepted | POST to create a resource accepted | - | 204 No Content | Success without response body | + | 204 No Content | Success without response message-body | | 304 Not Modified | Conditional operation not done | | 400 Bad Request | Invalid request message | | 403 Forbidden | Access to resource denied | | 404 Not Found | Resource target or resource node not | | | found | | 405 Method Not Allowed | Method not allowed for target | | | resource | | 409 Conflict | Resource or lock in use | | 412 Precondition Failed | Conditional method is false | | 413 Request Entity Too | too-big error | @@ -2269,54 +2412,70 @@ | data-exists | 409 | | data-missing | 409 | | operation-not-supported | 501 | | operation-failed | 500 | | partial-operation | 500 | | malformed-message | 400 | +-------------------------+-------------+ Mapping from error-tag to status code -6.1. Error Response Message +7.1. Error Response Message When an error occurs for a request message on a data resource or an operation resource, and a "4xx" class of status codes (except for status code "403 Forbidden"), then the server SHOULD send a response - body containing the information described by the "errors" container - definition within the YANG module Section 7. The Content-Type of - this response message MUST be application/yang.errors. + message-body containing the information described by the "errors" + container definition within the YANG module Section 8. The Content- + Type of this response message MUST be application/yang.errors (see + example below). + + The client MAY specify the desired encoding for error messages by + specifying the appropriate media-type in the Accept header. If no + error media is specified, the server MUST assume that "application/ + yang.errors+xml" was specified. All of the examples in this + document, except for the one below, assume the default XML encoding + will be returned if there is an error. YANG Tree Diagram for Data: +--ro errors +--ro error +--ro error-type enumeration +--ro error-tag string +--ro error-app-tag? string +--ro (error-node)? | +--:(error-path) | | +--ro error-path? instance-identifier | +--:(error-urlpath) | +--ro error-urlpath? data-resource-identifier +--ro error-message? string +--ro error-info The semantics and syntax for RESTCONF error messages are defined in - the "errors" YANG grouping in Section 7. + the "application/yang.errors" restconf-media-type extension in + Section 8. Examples: The following example shows an error returned for an "lock-denied" - error on a datastore resource. + error that can occur if a NETCONF client has locked a datastore. The + RESTCONF client is attempting to delete a data resource. Note that + an Accept header is used to specify the desired encoding for the + error message. This example's use of the Accept header is especially + notable since the DELETE method typically doesn't return a message- + body and hence Accept headers are typically not passed. - POST /restconf/operations/example-ops:lock-datastore HTTP/1.1 + DELETE /restconf/data/example-jukebox:jukebox/ + library/artist=Foo%20Fighters/album=Wasting%20Light HTTP/1.1 Host: example.com + Accept: application/yang.errors+json The server might respond: HTTP/1.1 409 Conflict Date: Mon, 23 Apr 2012 17:11:00 GMT Server: example-server Content-Type: application/yang.errors+json { "ietf-restconf:errors": { @@ -2342,112 +2501,178 @@ HTTP/1.1 409 Conflict Date: Mon, 23 Apr 2012 17:11:00 GMT Server: example-server Content-Type: application/yang.errors+json { "ietf-restconf:errors": { "error": { "error-type": "protocol", "error-tag": "data-exists", - "error-urlpath": "http://example.com/restconf/data/ + "error-urlpath": "https://example.com/restconf/data/ example-jukebox:jukebox", "error-message": "Data already exists, cannot create new resource" } } } -7. RESTCONF module - - The "ietf-restconf" module defines conceptual definitions within - groupings, which are not meant to be implemented as datastore - contents by a server. The "restconf" container is not intended to be - implemented as a top-level data node (under the "/restconf/data" - entry point). +8. RESTCONF module - The "ietf-yang-types" module from [RFC6991] is used by this module - for some type definitions. + The "ietf-restconf" module defines conceptual definitions within an + extension and two groupings, which are not meant to be implemented as + datastore contents by a server. E.g., the "restconf" container is + not intended to be implemented as a top-level data node (under the + "/restconf/data" entry point). RFC Ed.: update the date below with the date of RFC publication and remove this note. - file "ietf-restconf@2014-10-25.yang" + file "ietf-restconf@2015-01-30.yang" module ietf-restconf { namespace "urn:ietf:params:xml:ns:yang:ietf-restconf"; prefix "rc"; - import ietf-yang-types { prefix yang; } - organization "IETF NETCONF (Network Configuration) Working Group"; contact "WG Web: WG List: - WG Chair: Bert Wijnen - - WG Chair: Mehmet Ersue + WG Chair: Mahesh Jethanandani + + Editor: Andy Bierman Editor: Martin Bjorklund Editor: Kent Watsen "; description "This module contains conceptual YANG specifications - for the message and error content that is used in - RESTCONF protocol messages. A conceptual container - representing the RESTCONF API nodes is also defined - for the media type application/yang.api. + for basic RESTCONF media type definitions used in + RESTCONF protocol messages. Note that the YANG definitions within this module do not represent configuration data of any kind. - The YANG grouping statements provide a normative syntax - for XML and JSON message encoding purposes. + The 'restconf-media-type' YANG extension statement + provides a normative syntax for XML and JSON message + encoding purposes. - Copyright (c) 2014 IETF Trust and the persons identified as + Copyright (c) 2015 IETF Trust and the persons identified as authors of the code. All rights reserved. Redistribution and use in source and binary forms, with or without modification, is permitted pursuant to, and subject to the license terms contained in, the Simplified BSD License set forth in Section 4.c of the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info). This version of this YANG module is part of RFC XXXX; see the RFC itself for full legal notices."; // RFC Ed.: replace XXXX with actual RFC number and remove this // note. // RFC Ed.: remove this note - // Note: extracted from draft-ietf-netconf-restconf-03.txt + // Note: extracted from draft-ietf-netconf-restconf-04.txt // RFC Ed.: update the date below with the date of RFC publication // and remove this note. - revision 2014-10-25 { + revision 2015-01-30 { description "Initial revision."; reference "RFC XXXX: RESTCONF Protocol."; } + extension restconf-media-type { + argument media-type-id { + yin-element true; + } + description + "This extension is used to specify a YANG data structure which + represents a conceptual RESTCONF media type template. + Data definition statements within this extension specify + the 'generic syntax' for the specific media type. + + YANG is mapped to specific encoding formats outside the + scope of this extension statement. RFC 6020 defines XML + encoding rules for all RESTCONF media types that use + the '+xml' suffix. draft-ietf-netmod-yang-json defines + JSON encoding rules for all RESTCONF media types that + use the '+json' suffix. + + The 'media-type-id' parameter value identifies the media type + that is being defined. It contains the string associated + with the generic media type, i.e., no suffix is specified. + + This extension is ignored unless it appears as a top-level + statement. It SHOULD contain data definition statements + that result in exactly one container data node definition. + This allows compliant translation to an XML instance + document for each media type. + + The module name and namespace value for the YANG module using + the extension statement is assigned to instance document data + conforming to the data definition statements within + this extension. + + The sub-statements of this extension MUST follow the + 'data-def-stmt' rule in the YANG ABNF. + + The XPath document root is the extension statement itself, + such that the child nodes of the document root are + represented by the data-def-stmt sub-statements within + this extension. This conceptual document is the context + for the following YANG statements: + + - must-stmt + - when-stmt + - path-stmt + - min-elements-stmt + - max-elements-stmt + - mandatory-stmt + - unique-stmt + - ordered-by + - instance-identifier data type + + The following data-def-stmt sub-statements have special + meaning when used within a restconf-resource extension + statement. + + - The list-stmt is not required to have a key-stmt defined. + - The if-feature-stmt is ignored if present. + - The config-stmt is ignored if present. + - The available identity values for any 'identityref' + leaf or leaf-list nodes is limited to the module + containing this extension statement, and the modules + imported into that module. + "; + } + rc:restconf-media-type "application/yang.errors" { + uses errors; + } + + rc:restconf-media-type "application/yang.api" { + uses restconf; + } + typedef data-resource-identifier { type string { length "1 .. max"; } description "Contains a Data Resource Identifier formatted string to identify a specific data resource instance. The document root for all data resources is a datastore resource container. Each top-level YANG data nodes supported by the server will be represented @@ -2598,72 +2822,25 @@ POST /restconf/operations/show-log-errors leaf show-log-errors { type empty; } "; } } // container restconf } // grouping restconf - grouping collection { - description - "Conceptual container representing the - application/yang.collection resource type."; - - container collection { - description - "Container representing the application/yang.collection - resource type."; - } - } // grouping collection - - grouping notification { - description - "Contains the notification message wrapper definition."; - - container notification { - description - "RESTCONF notification message wrapper."; - - leaf event-time { - type yang:date-and-time; - mandatory true; - description - "The time the event was generated by the - event source."; - reference - "RFC 5277, section 4, element."; - } - - /* The YANG-specific notification container is encoded - * after the 'event-time' element. The format - * corresponds to the notificationContent element - * in RFC 5277, section 4. For example: - * - * module example-one { - * ... - * notification event1 { ... } - * - * } - * - * Encoded as element 'event1' in the namespace - * for module 'example-one'. - */ - } - } // grouping notification - } -8. RESTCONF Monitoring +9. RESTCONF Monitoring The "ietf-restconf-monitoring" module provides information about the RESTCONF protocol capabilities and notification event streams available from the server. Implementation is mandatory for RESTCONF servers, if any protocol capabilities or notification event streams are supported. YANG Tree Diagram for "ietf-restconf-monitoring" module: +--ro restconf-state @@ -2672,114 +2849,114 @@ +--ro streams +--ro stream* [name] +--ro name string +--ro description? string +--ro replay-support? boolean +--ro replay-log-creation-time? yang:date-and-time +--ro encoding* [type] +--ro type string +--ro events inet:uri -8.1. restconf-state/capabilities +9.1. restconf-state/capabilities This mandatory container holds the RESTCONF protocol capability URIs supported by the server. The server MUST maintain a last-modified timestamp for this container, and return the "Last-Modified" header when this data node is retrieved with the GET or HEAD methods. The server SHOULD maintain an entity-tag for this container, and return the "ETag" header when this data node is retrieved with the GET or HEAD methods. -8.2. restconf-state/streams +9.2. restconf-state/streams This optional container provides access to the notification event streams supported by the server. The server MAY omit this container if no notification event streams are supported. The server will populate this container with a stream list entry for each stream type it supports. Each stream contains a leaf called "events" which contains a URI that represents an event stream resource. - Stream resources are defined in Section 2.9. Notifications are - defined in Section 5. + Stream resources are defined in Section 3.8. Notifications are + defined in Section 6. -8.3. RESTCONF Monitoring Module +9.3. RESTCONF Monitoring Module The "ietf-restconf-monitoring" module defines monitoring information for the RESTCONF protocol. The "ietf-yang-types" and "ietf-inet-types" modules from [RFC6991] are used by this module for some type definitions. RFC Ed.: update the date below with the date of RFC publication and remove this note. - file "ietf-restconf-monitoring@2014-10-25.yang" + file "ietf-restconf-monitoring@2015-01-30.yang" module ietf-restconf-monitoring { namespace "urn:ietf:params:xml:ns:yang:ietf-restconf-monitoring"; prefix "rcmon"; import ietf-yang-types { prefix yang; } import ietf-inet-types { prefix inet; } organization "IETF NETCONF (Network Configuration) Working Group"; contact "WG Web: WG List: - WG Chair: Bert Wijnen - - WG Chair: Mehmet Ersue + WG Chair: Mahesh Jethanandani + + Editor: Andy Bierman Editor: Martin Bjorklund Editor: Kent Watsen "; description "This module contains monitoring information for the RESTCONF protocol. - Copyright (c) 2014 IETF Trust and the persons identified as + Copyright (c) 2015 IETF Trust and the persons identified as authors of the code. All rights reserved. Redistribution and use in source and binary forms, with or without modification, is permitted pursuant to, and subject to the license terms contained in, the Simplified BSD License set forth in Section 4.c of the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info). This version of this YANG module is part of RFC XXXX; see the RFC itself for full legal notices."; // RFC Ed.: replace XXXX with actual RFC number and remove this // note. // RFC Ed.: remove this note - // Note: extracted from draft-ietf-netconf-restconf-03.txt + // Note: extracted from draft-ietf-netconf-restconf-04.txt // RFC Ed.: update the date below with the date of RFC publication // and remove this note. - revision 2014-10-25 { + revision 2015-01-30 { description "Initial revision."; reference "RFC XXXX: RESTCONF Protocol."; } container restconf-state { config false; description "Contains RESTCONF protocol monitoring information."; @@ -2876,344 +3053,118 @@ } } } } } } -9. YANG Module Library +10. YANG Module Library - The "ietf-yang-library" module provides information about the YANG + The "ietf-yang-library" module defined in + [I-D.ietf-netconf-yang-library] provides information about the YANG modules and submodules used by the RESTCONF server. Implementation is mandatory for RESTCONF servers. All YANG modules and submodules used by the server MUST be identified in the YANG module library. - YANG Tree Diagram for "ietf-yang-library" module: - - +--ro modules - +--ro module-set-id? string - +--ro module* [name revision] - +--ro name yang:yang-identifier - +--ro revision union - +--ro schema? inet:uri - +--ro namespace inet:uri - +--ro feature* yang:yang-identifier - +--ro deviation* yang:yang-identifier - +--ro conformance boolean - +--ro submodules - +--ro submodule* [name revision] - +--ro name yang:yang-identifier - +--ro revision union - +--ro schema? inet:uri - -9.1. modules +10.1. modules This mandatory container holds the identifiers for the YANG data model modules supported by the server. The server MUST maintain a last-modified timestamp for this container, and return the "Last-Modified" header when this data node is retrieved with the GET or HEAD methods. The server SHOULD maintain an entity-tag for this container, and return the "ETag" header when this data node is retrieved with the GET or HEAD methods. -9.1.1. modules/module +10.1.1. modules/module This mandatory list contains one entry for each YANG data model module supported by the server. There MUST be an instance of this list for every YANG module that is used by the server. - The contents of the "module" list are defined in the "module" YANG - list statement in Section 9.2. + The contents of this list are defined in the "module" YANG list + statement in [I-D.ietf-netconf-yang-library]. The server MAY maintain a last-modified timestamp for each instance of this list entry, and return the "Last-Modified" header when this data node is retrieved with the GET or HEAD methods. If not supported then the timestamp for the parent "modules" container MAY be used instead. The server MAY maintain an entity-tag for each instance of this list entry, and return the "ETag" header when this data node is retrieved with the GET or HEAD methods. If not supported then the timestamp for the parent "modules" container MAY be used instead. -9.2. YANG Library Module - - The "ietf-yang-library" module defines monitoring information for the - YANG modules used by a RESTCONF server. - - The "ietf-yang-types" and "ietf-inet-types" modules from [RFC6991] - are used by this module for some type definitions. - - RFC Ed.: update the date below with the date of RFC publication and - remove this note. - - file "ietf-yang-library@2014-10-25.yang" - - module ietf-yang-library { - namespace "urn:ietf:params:xml:ns:yang:ietf-yang-library"; - prefix "yanglib"; - - import ietf-yang-types { prefix yang; } - import ietf-inet-types { prefix inet; } - - organization - "IETF NETCONF (Network Configuration) Working Group"; - - contact - "WG Web: - WG List: - - WG Chair: Bert Wijnen - - - WG Chair: Mehmet Ersue - - - Editor: Andy Bierman - - - Editor: Martin Bjorklund - - - Editor: Kent Watsen - "; - - description - "This module contains monitoring information about the YANG - modules and submodules that are used within a RESTCONF - server. - - Copyright (c) 2014 IETF Trust and the persons identified as - authors of the code. All rights reserved. - - Redistribution and use in source and binary forms, with or - without modification, is permitted pursuant to, and subject - to the license terms contained in, the Simplified BSD License - set forth in Section 4.c of the IETF Trust's Legal Provisions - Relating to IETF Documents - (http://trustee.ietf.org/license-info). - - This version of this YANG module is part of RFC XXXX; see - the RFC itself for full legal notices."; - - // RFC Ed.: replace XXXX with actual RFC number and remove this - // note. - - // RFC Ed.: remove this note - // Note: extracted from draft-ietf-netconf-restconf-03.txt - - // RFC Ed.: update the date below with the date of RFC publication - // and remove this note. - revision 2014-10-25 { - description - "Initial revision."; - reference - "RFC XXXX: RESTCONF Protocol."; - } - - typedef revision-identifier { - type string { - pattern '\d{4}-\d{2}-\d{2}'; - } - description - "Represents a specific date in YYYY-MM-DD format. - TBD: make pattern more precise to exclude leading zeros."; - } - - grouping module { - description - "The module data structure is represented as a grouping - so it can be reused in configuration or another monitoring - data structure."; - - grouping common-leafs { - description - "Common parameters for YANG modules and submodules."; - - leaf name { - type yang:yang-identifier; - description "The YANG module or submodule name."; - } - leaf revision { - type union { - type revision-identifier; - type string { length 0; } - } - description - "The YANG module or submodule revision date. - An empty string is used if no revision statement - is present in the YANG module or submodule."; - } - leaf schema { - type inet:uri; - description - "Contains a URL that represents the YANG schema - resource for this module or submodule. - - This leaf will only be present if there is a URL - available for retrieval of the schema for this entry."; - } - } - - list module { - key "name revision"; - description - "Each entry represents one module currently - supported by the server."; - - uses common-leafs; - - leaf namespace { - type inet:uri; - mandatory true; - description - "The XML namespace identifier for this module."; - } - leaf-list feature { - type yang:yang-identifier; - description - "List of YANG feature names from this module that are - supported by the server."; - } - leaf-list deviation { - type yang:yang-identifier; - description - "List of YANG deviation module names used by this - server to modify the conformance of the module - associated with this entry."; - } - leaf conformance { - type boolean; - mandatory true; - description - "If 'true', then the server is claiming conformance to - the YANG module identified in this entry. - - If 'false', then the server is not claiming any - conformance for the YANG module identified by this - entry. The module may be needed for reusable definitions - such as extensions, features, identifies, typedefs, - or groupings."; - } - container submodules { - description - "Contains information about all the submodules used - by the parent module entry"; - - list submodule { - key "name revision"; - description - "Each entry represents one submodule within the - parent module."; - uses common-leafs; - } - } - } // list module - } // grouping module - - container modules { - config false; - description - "Contains YANG module monitoring information."; - - leaf module-set-id { - type string; - description - "Contains a server-specific identifier representing - the current set of modules and submodules. The - server MUST change the value of this leaf if the - information represented by the 'module' list instances - has changed."; - } - - uses module; - - } - - } - - - -10. IANA Considerations +11. IANA Considerations -10.1. The "restconf" Relation Type +11.1. The "restconf" Relation Type This specification registers the "restconf" relation type in the Link Relation Type Registry defined by [RFC5988]: Relation Name: restconf Description: Identifies the root of RESTCONF API as configured on this HTTP server. The "restconf" relation defines the root of the API defined in RFCXXXX. Subsequent revisions of RESTCONF will use alternate relation values to support protocol versioning. Reference: RFC XXXX ` -10.2. YANG Module Registry +11.2. YANG Module Registry - This document registers three URIs in the IETF XML registry - [RFC3688]. Following the format in RFC 3688, the following - registration is requested to be made. + This document registers two URIs in the IETF XML registry [RFC3688]. + Following the format in RFC 3688, the following registration is + requested to be made. URI: urn:ietf:params:xml:ns:yang:ietf-restconf Registrant Contact: The NETMOD WG of the IETF. XML: N/A, the requested URI is an XML namespace. URI: urn:ietf:params:xml:ns:yang:ietf-restconf-monitoring Registrant Contact: The NETMOD WG of the IETF. XML: N/A, the requested URI is an XML namespace. - URI: urn:ietf:params:xml:ns:yang:ietf-yang-library - Registrant Contact: The NETMOD WG of the IETF. - XML: N/A, the requested URI is an XML namespace. - - This document registers three YANG modules in the YANG Module Names + This document registers two YANG modules in the YANG Module Names registry [RFC6020]. name: ietf-restconf namespace: urn:ietf:params:xml:ns:yang:ietf-restconf prefix: rc // RFC Ed.: replace XXXX with RFC number and remove this note reference: RFC XXXX name: ietf-restconf-monitoring namespace: urn:ietf:params:xml:ns:yang:ietf-restconf-monitoring prefix: rcmon // RFC Ed.: replace XXXX with RFC number and remove this note reference: RFC XXXX - name: ietf-yang-library - namespace: urn:ietf:params:xml:ns:yang:ietf-yang-library - prefix: yanglib - // RFC Ed.: replace XXXX with RFC number and remove this note - reference: RFC XXXX - -10.3. application/yang Media Sub Types +11.3. application/yang Media Sub Types The parent MIME media type for RESTCONF resources is application/ yang, which is defined in [RFC6020]. This document defines the following sub-types for this media type. - api - data - datastore - - collection - errors - operation - stream Type name: application Subtype name: yang.xxx Required parameters: TBD @@ -3221,200 +3172,297 @@ Encoding considerations: TBD Security considerations: TBD Interoperability considerations: TBD // RFC Ed.: replace XXXX with RFC number and remove this note Published specification: RFC XXXX -10.4. NETCONF Capability URNs +11.4. RESTCONF Capability URNs - This document registers several capability identifiers in "Network - Configuration Protocol (NETCONF) Capability URNs" registry + [Note to RFC Editor: + The RESTCONF Protocol Capability Registry does not yet exist; + Need to ask IANA to create it; remove this note for publication + ] + This document registers several capability identifiers in "RESTCONF + Protocol Capability URNs" registry Index Capability Identifier ------------------------ - :content - urn:ietf:params:restconf:capability:content:1.0 + :defaults + urn:ietf:params:restconf:capability:defaults:1.0 :depth urn:ietf:params:restconf:capability:depth:1.0 + :fields + urn:ietf:params:restconf:capability:fields:1.0 + :filter urn:ietf:params:restconf:capability:filter:1.0 :insert urn:ietf:params:restconf:capability:insert:1.0 - :page - urn:ietf:params:restconf:capability:page:1.0 - - :select - urn:ietf:params:restconf:capability:select:1.0 - :replay urn:ietf:params:restconf:capability:replay:1.0 -11. Security Considerations + :with-defaults + urn:ietf:params:restconf:capability:with-defaults:1.0 + +12. Security Considerations This section provides security considerations for the resources defined by the RESTCONF protocol. Security considerations for HTTPS are defined in [RFC2818]. Security considerations for the content manipulated by RESTCONF can be found in the documents defining data models. This document does not specify an authentication scheme, but it does require that an authenticated NETCONF username be associated with each HTTP request. The authentication scheme MAY be implemented in the underlying transport layer (e.g., client certificates) or within the HTTP layer (e.g., Basic Auth, OAuth, etc.). RESTCONF does not itself define an authentication mechanism, authentication MUST occur in a lower layer. Implementors SHOULD provide a comprehensive authorization scheme with RESTCONF and ensure that the resulting NETCONF username is made available to the RESTCONF server. Authorization of individual user access to operations and data MAY be configured via NETCONF Access Control Model (NACM) [RFC6536], as - specified in Section 3. Other authorization models MAY be used, but + specified in Section 4. Other authorization models MAY be used, but are outside of the scope of this document. Configuration information is by its very nature sensitive. Its transmission in the clear and without integrity checking leaves devices open to classic eavesdropping and false data injection attacks. Configuration information often contains passwords, user names, service descriptions, and topological information, all of which are sensitive. Because of this, this protocol SHOULD be implemented carefully with adequate attention to all manner of attack one might expect to experience with other management interfaces. Different environments may well allow different rights prior to and then after authentication. When an operation is not properly authorized, the RESTCONF server MUST return HTTP error status code 401 Unauthorized. Note that authorization information can be exchanged in the form of configuration information, which is all the more reason to ensure the security of the connection. -12. Acknowledgements +13. Acknowledgements - The authors would like to thank for following for lively discussions - on list and in the halls (ordered by last name): Rex Fernando + The authors would like to thank the following people for their + contributions to this document: Ladislav Lhotka, Juergen + Schoenwaelder, Rex Fernando, Robert Wilton, and Jonathan Hansford. -13. References +14. References -13.1. Normative References +14.1. Normative References - [I-D.ietf-netmod-json] - Lhotka, L., "Modeling JSON Text with YANG", draft-ietf- - netmod-yang-json-01 (work in progress), October 2014. + [I-D.ietf-netconf-yang-library] + Bierman, A., Bjorklund, M., and K. Watsen, "YANG Module + Library", draft-ietf-netconf-yang-library-00 (work in + progress), January 2015. + + [I-D.ietf-netmod-yang-json] + Lhotka, L., "JSON Encoding of Data Modeled with YANG", + draft-ietf-netmod-yang-json-02 (work in progress), + November 2014. [I-D.lhotka-netmod-yang-metadata] Lhotka, L., "Defining and Using Metadata with YANG", draft-lhotka-netmod-yang-metadata-00 (work in progress), September 2014. + [RFC2046] Freed, N. and N. Borenstein, "Multipurpose Internet Mail + Extensions (MIME) Part Two: Media Types", RFC 2046, + November 1996. + [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997. - [RFC2246] Dierks, T. and C. Allen, "The TLS Protocol, Version 1.0", - RFC 2246, January 1999. - [RFC2396] Berners-Lee, T., Fielding, R., and L. Masinter, "Uniform Resource Identifiers (URI): Generic Syntax", RFC 2396, August 1998. - [RFC2616] Fielding, R., Gettys, J., Mogul, J., Frystyk, H., - Masinter, L., Leach, P., and T. Berners-Lee, "Hypertext - Transfer Protocol -- HTTP/1.1", RFC 2616, June 1999. - [RFC2818] Rescorla, E., "The IETF XML Registry", RFC 2818, May 2000. [RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688, January 2004. [RFC3986] Berners-Lee, T., Fielding, R., and L. Masinter, "Uniform Resource Identifier (URI): Generic Syntax", STD 66, RFC 3986, January 2005. + [RFC4252] Ylonen, T. and C. Lonvick, "The Secure Shell (SSH) + Authentication Protocol", RFC 4252, January 2006. + + [RFC5246] Dierks, T. and E. Rescorla, "The Transport Layer Security + (TLS) Protocol Version 1.2", RFC 5246, August 2008. + [RFC5277] Chisholm, S. and H. Trevino, "NETCONF Event Notifications", RFC 5277, July 2008. [RFC5280] Cooper, D., Santesson, S., Farrell, S., Boeyen, S., Housley, R., and T. Polk, "Internet X.509 Public Key Infrastructure Certificate and Certificate Revocation List (CRL) Profile", RFC 5280, May 2008. [RFC5789] Dusseault, L. and J. Snell, "PATCH Method for HTTP", RFC 5789, March 2010. [RFC5988] Nottingham, M., "Web Linking", RFC 5988, October 2010. [RFC6020] Bjorklund, M., "YANG - A Data Modeling Language for the Network Configuration Protocol (NETCONF)", RFC 6020, October 2010. + [RFC6125] Saint-Andre, P. and J. Hodges, "Representation and + Verification of Domain-Based Application Service Identity + within Internet Public Key Infrastructure Using X.509 + (PKIX) Certificates in the Context of Transport Layer + Security (TLS)", RFC 6125, March 2011. + [RFC6241] Enns, R., Ed., Bjorklund, M., Ed., Schoenwaelder, J., Ed., and A. Bierman, Ed., "Network Configuration Protocol (NETCONF)", RFC 6241, June 2011. + [RFC6243] Bierman, A. and B. Lengyel, "With-defaults Capability for + NETCONF", RFC 6243, June 2011. + [RFC6415] Hammer-Lahav, E. and B. Cook, "Web Host Metadata", RFC 6415, October 2011. [RFC6536] Bierman, A. and M. Bjorklund, "Network Configuration Protocol (NETCONF) Access Control Model", RFC 6536, March 2012. [RFC6570] Gregorio, J., Fielding, R., Hadley, M., Nottingham, M., and D. Orchard, "URI Template", RFC 6570, March 2012. [RFC6991] Schoenwaelder, J., "Common YANG Data Types", RFC 6991, July 2013. [RFC7158] Bray, T., Ed., "The JSON Data Interchange Format", RFC 7158, March 2013. + [RFC7230] Fielding, R. and J. Reschke, "Hypertext Transfer Protocol + (HTTP/1.1): Message Syntax and Routing", RFC 7230, June + 2014. + + [RFC7231] Fielding, R. and J. Reschke, "Hypertext Transfer Protocol + (HTTP/1.1): Semantics and Content", RFC 7231, June 2014. + + [RFC7232] Fielding, R. and J. Reschke, "Hypertext Transfer Protocol + (HTTP/1.1): Conditional Requests", RFC 7232, June 2014. + + [RFC7235] Fielding, R. and J. Reschke, "Hypertext Transfer Protocol + (HTTP/1.1): Authentication", RFC 7235, June 2014. + + [RFC7320] Nottingham, M., "URI Design and Ownership", BCP 190, RFC + 7320, July 2014. + [W3C.CR-eventsource-20121211] Hickson, I., "Server-Sent Events", World Wide Web Consortium CR CR-eventsource-20121211, December 2012, . [W3C.REC-xml-20081126] Yergeau, F., Maler, E., Paoli, J., Sperberg-McQueen, C., and T. Bray, "Extensible Markup Language (XML) 1.0 (Fifth Edition)", World Wide Web Consortium Recommendation REC- xml-20081126, November 2008, . - [get-off-my-lawn] - Nottingham, M., "URI Design and Ownership", Best Current - Practice draft-ietf-appsawg-uri-get-off-my-lawn-05, May - 2014. + [draft-ietf-httpauth-basicauth-update-03] + Reschke, J., "The 'Basic' HTTP Authentication Scheme", + draft-ietf-httpauth-basicauth-update-03 (work in + progress), Dec 2014. + + [draft-ietf-httpauth-digest-09] + Shekh-Yusef, R., Reschke, D., and S. Bremer, "HTTP Digest + Access Authentication", draft-ietf-httpauth-digest-09 + (work in progress), Dec 2014. + + [draft-ietf-netconf-rfc5539bis-07] + Badra, M., Luchuk, A., and J. Schoenwaelder, "Using the + NETCONF Protocol over Transport Layer Security (TLS) with + Mutual X.509 Authentication", draft-ietf-netconf- + rfc5539bis-07 (work in progress), Dec 2014. + + [draft-thomson-httpbis-cant-01] + Thomson, M., "Client Authentication over New TLS + Connection", draft-thomson-httpbis-cant-01 (work in + progress), Jul 2014. [rest-dissertation] Fielding, R., "Architectural Styles and the Design of Network-based Software Architectures", 2000. -13.2. Informative References +14.2. Informative References + + [I-D.ietf-netconf-yang-patch] + Bierman, A., Bjorklund, M., and K. Watsen, "YANG Patch + Media Type", draft-ietf-netconf-yang-patch-03 (work in + progress), January 2015. [XPath] Clark, J. and S. DeRose, "XML Path Language (XPath) Version 1.0", World Wide Web Consortium Recommendation REC-xpath-19991116, November 1999, . Appendix A. Change Log -- RFC Ed.: remove this section before publication. -A.1. 02 - 03 + The RESTCONF issue tracker can be found here: https://github.com/ + netconf-wg/restconf/issues + +A.1. 03 - 04 + + o renamed 'select' to 'fields' (#1) + + o moved collection resource and page capability to draft-ietf- + netconf-restconf-collection-00 (#3) + + o added mandatory "defaults" protocol capability URI (#4) + o added optional "with-defaults" query parameter URI (#4) + + o clarified authentication procedure (#9) + + o moved ietf-yang-library module to draft-ietf-netconf-yang- + library-00 (#13) + + o clarified that JSON encoding of module name in a URI MUST follow + the netmod-yang-json encoding rules (#14) + + o added restconf-media-type extension (#15) + + o remove 'content" query parameter URI and made this parameter + mandatory (#16) + + o clarified datastore usage + + o changed lock-denied error example + + o added with-defaults query parameter example + + o added term "RESTCONF Capability" + + o changed NETCONF Capability URI registry usage to new RESTCONF + Capability URI Registry usage + +A.2. 02 - 03 o added collection resource o added "page" query parameter capability o added "limit" and "offset" query parameters, which are available if the "page" capability is supported o added "stream list" term @@ -3412,30 +3460,31 @@ o added collection resource o added "page" query parameter capability o added "limit" and "offset" query parameters, which are available if the "page" capability is supported o added "stream list" term o fixed bugs in some examples + o added "encoding" list within the "stream" list to allow different URLs for XML and JSON encoding. o made XML MUST implement and JSON MAY implement for servers o re-add JSON notification examples (previously removed) o updated JSON references -A.2. 01 - 02 +A.3. 01 - 02 o moved query parameter definitions from the YANG module back to the plain text sections o made all query parameters optional to implement o defined query parameter capability URI o moved 'streams' to new YANG module (ietf-restconf-monitoring) @@ -3459,32 +3508,32 @@ information is no longer in this resource o closed issue #1 'select parameter' since no objections to the proposed syntax o closed "encoding of list keys" issue since no objection to new encoding of list keys in a target resource URI. o moved open issues list to the issue tracker on github -A.3. 00 - 01 +A.4. 00 - 01 o fixed content=nonconfig example (non-config was incorrect) o closed open issue 'message-id'. There is no need for a message-id field, and RFC 2392 does not apply. o closed open issue 'server support verification'. The headers used by RESTCONF are widely supported. o removed encoding rules from section on RESTCONF Meta-Data. This - is now defined in "I-D.lhotka-netmod-json". + is now defined in "I-D.lhotka-netmod-yang-json". o added media type application/yang.errors to map to errors YANG grouping. Updated error examples to use new media type. o closed open issue 'additional datastores'. Support may be added in the future to identify new datastores. o closed open issue 'PATCH media type discovery'. The section on PATCH has an added sentence on the Accept-Patch header. @@ -3503,21 +3552,21 @@ the RESTCONF API using the /.well-known/host-meta. o added an "error" media type to for structured error messages o added Secure Transport section requiring TLS o added Security Considerations section o removed all references to "REST-like" -A.4. bierman:restconf-04 to ietf:restconf-00 +A.5. bierman:restconf-04 to ietf:restconf-00 o updated open issues section Appendix B. Open Issues -- RFC Ed.: remove this section before publication. The RESTCONF issues are tracked on github.com: https://github.com/netconf-wg/restconf/issues @@ -3804,36 +3852,35 @@ mandatory true; description "Song number in playlist to play"; } } } } Appendix D. RESTCONF Message Examples The examples within this document use the normative YANG module - defined in Section 7 and the non-normative example YANG module + defined in Section 8 and the non-normative example YANG module defined in Appendix C.1. This section shows some typical RESTCONF message exchanges. D.1. Resource Retrieval Examples D.1.1. Retrieve the Top-level API Resource The client may start by retrieving the top-level API resource, using the entry point URI "{+restconf}". GET /restconf HTTP/1.1 Host: example.com - Accept: application/yang.api+json, - application/yang.errors+json + Accept: application/yang.api+json The server might respond as follows: HTTP/1.1 200 OK Date: Mon, 23 Apr 2012 17:01:00 GMT Server: example-server Content-Type: application/yang.api+json { "ietf-restconf:restconf": { @@ -3842,137 +3889,135 @@ "play" : [ null ] } } } To request that the response content to be encoded in XML, the "Accept" header can be used, as in this example request: GET /restconf HTTP/1.1 Host: example.com - Accept: application/yang.api+xml, - application/yang.errors+xml + Accept: application/yang.api+xml The server will return the same response either way, which might be as follows : HTTP/1.1 200 OK Date: Mon, 23 Apr 2012 17:01:00 GMT Server: example-server Cache-Control: no-cache Pragma: no-cache Content-Type: application/yang.api+xml - + D.1.2. Retrieve The Server Module Information In this example the client is retrieving the modules information from the server in JSON format: GET /restconf/data/ietf-yang-library:modules HTTP/1.1 Host: example.com - Accept: application/yang.data+json, - application/yang.errors+json + Accept: application/yang.data+json The server might respond as follows. HTTP/1.1 200 OK Date: Mon, 23 Apr 2012 17:01:00 GMT Server: example-server Cache-Control: no-cache Pragma: no-cache Last-Modified: Sun, 22 Apr 2012 01:00:14 GMT Content-Type: application/yang.data+json { "ietf-yang-library:modules": { "module": [ { "name" : "foo", "revision" : "2012-01-02", - "schema" : "http://example.com/mymodules/foo/2012-01-02", + "schema" : "https://example.com/mymodules/foo/2012-01-02", "namespace" : "http://example.com/ns/foo", "feature" : [ "feature1", "feature2" ], "conformance" : true }, { "name" : "foo-types", "revision" : "2012-01-05", "schema" : - "http://example.com/mymodules/foo-types/2012-01-05", + + "https://example.com/mymodules/foo-types/2012-01-05", "schema" : [null], "namespace" : "http://example.com/ns/foo-types", "conformance" : false }, { "name" : "bar", "revision" : "2012-11-05", - "schema" : "http://example.com/mymodules/bar/2012-11-05", + "schema" : "https://example.com/mymodules/bar/2012-11-05", "namespace" : "http://example.com/ns/bar", "feature" : [ "bar-ext" ], "conformance" : true, "submodule" : [ { "name" : "bar-submod1", "revision" : "2012-11-05", "schema" : - "http://example.com/mymodules/bar-submod1/2012-11-05" + "https://example.com/mymodules/bar-submod1/2012-11-05" }, { "name" : "bar-submod2", "revision" : "2012-11-05", "schema" : - "http://example.com/mymodules/bar-submod2/2012-11-05" + "https://example.com/mymodules/bar-submod2/2012-11-05" } ] } ] } } D.1.3. Retrieve The Server Capability Information In this example the client is retrieving the capability information from the server in JSON format, and the server supports all the RESTCONF query parameters, plus one vendor parameter: GET /restconf/data/ietf-restconf-monitoring:restconf-state/ capabilities HTTP/1.1 Host: example.com - Accept: application/yang.data+json, - application/yang.errors+json + Accept: application/yang.data+json The server might respond as follows. HTTP/1.1 200 OK Date: Mon, 23 Apr 2012 17:02:00 GMT Server: example-server Cache-Control: no-cache Pragma: no-cache Last-Modified: Sun, 22 Apr 2012 01:00:14 GMT Content-Type: application/yang.data+json { "ietf-restconf-monitoring:capabilities": { "capability": [ "urn:ietf:params:restconf:capability:content:1.0", "urn:ietf:params:restconf:capability:depth:1.0", + "urn:ietf:params:restconf:capability:fields:1.0", "urn:ietf:params:restconf:capability:filter:1.0", "urn:ietf:params:restconf:capability:insert:1.0", "urn:ietf:params:restconf:capability:point:1.0", - "urn:ietf:params:restconf:capability:select:1.0", "urn:ietf:params:restconf:capability:start-time:1.0", "urn:ietf:params:restconf:capability:stop-time:1.0", "http://example.com/capabilities/myparam" ] } } D.2. Edit Resource Examples D.2.1. Create New Data Resources @@ -3989,21 +4034,21 @@ } } If the resource is created, the server might respond as follows. Note that the "Location" header line is wrapped for display purposes only: HTTP/1.1 201 Created Date: Mon, 23 Apr 2012 17:02:00 GMT Server: example-server - Location: http://example.com/restconf/data/ + Location: https://example.com/restconf/data/ example-jukebox:jukebox/library/artist=Foo%20Fighters Last-Modified: Mon, 23 Apr 2012 17:02:00 GMT ETag: b3830f23a4c To create a new "album" resource for this artist within the "jukebox" resource, the client might send the following request. Note that the request URI header line is wrapped for display purposes only: POST /restconf/data/example-jukebox:jukebox/ library/artist=Foo%20Fighters HTTP/1.1 @@ -4018,40 +4063,39 @@ } } If the resource is created, the server might respond as follows. Note that the "Location" header line is wrapped for display purposes only: HTTP/1.1 201 Created Date: Mon, 23 Apr 2012 17:03:00 GMT Server: example-server - Location: http://example.com/restconf/data/ + Location: https://example.com/restconf/data/ example-jukebox:jukebox/library/artist=Foo%20Fighters/ album=Wasting%20Light Last-Modified: Mon, 23 Apr 2012 17:03:00 GMT ETag: b8389233a4c D.2.2. Detect Resource Entity Tag Change In this example, the server just supports the mandatory datastore last-changed timestamp. The client has previously retrieved the "Last-Modified" header and has some value cached to provide in the following request to patch an "album" list entry with key value "Wasting Light". Only the "year" field is being updated. PATCH /restconf/data/example-jukebox:jukebox/ library/artist=Foo%20Fighters/album=Wasting%20Light/year HTTP/1.1 Host: example.com - Accept: application/yang.data+json, - application/yang.errors+json + Accept: application/yang.data+json If-Unmodified-Since: Mon, 23 Apr 2012 17:01:00 GMT Content-Type: application/yang.data+json { "example-jukebox:year" : "2011" } In this example the datastore resource has changed since the time specified in the "If-Unmodified-Since" header. The server might respond: HTTP/1.1 412 Precondition Failed @@ -4077,28 +4121,28 @@ leaf name { type string; } leaf description { type string; } leaf event-count { type uint32; config false; } } } Example 1: content=all + To retrieve all the child resources, the "content" parameter is set to "all". The client might send: GET /restconf/data/example-events:events?content=all HTTP/1.1 Host: example.com - Accept: application/yang.data+json, - application/yang.errors+json + Accept: application/yang.data+json The server might respond: HTTP/1.1 200 OK Date: Mon, 23 Apr 2012 17:11:30 GMT Server: example-server Cache-Control: no-cache Pragma: no-cache Content-Type: application/yang.data+json @@ -4122,22 +4166,21 @@ Example 2: content=config To retrieve only the configuration child resources, the "content" parameter is set to "config" or omitted since this is the default value. Note that the "ETag" and "Last-Modified" headers are only returned if the content parameter value is "config". GET /restconf/data/example-events:events?content=config HTTP/1.1 Host: example.com - Accept: application/yang.data+json, - application/yang.errors+json + Accept: application/yang.data+json The server might respond: HTTP/1.1 200 OK Date: Mon, 23 Apr 2012 17:11:30 GMT Server: example-server Last-Modified: Mon, 23 Apr 2012 13:01:20 GMT ETag: eeeada438af Cache-Control: no-cache Pragma: no-cache @@ -4161,22 +4204,21 @@ Example 3: content=nonconfig To retrieve only the non-configuration child resources, the "content" parameter is set to "nonconfig". Note that configuration ancestors (if any) and list key leafs (if any) are also returned. The client might send: GET /restconf/data/example-events:events?content=nonconfig HTTP/1.1 Host: example.com - Accept: application/yang.data+json, - application/yang.errors+json + Accept: application/yang.data+json The server might respond: HTTP/1.1 200 OK Date: Mon, 23 Apr 2012 17:11:30 GMT Server: example-server Cache-Control: no-cache Pragma: no-cache Content-Type: application/yang.data+json @@ -4206,22 +4248,21 @@ Example 1: depth=unbounded To retrieve all the child resources, the "depth" parameter is not present or set to the default value "unbounded". Note that some strings are wrapped for display purposes only. GET /restconf/data/example-jukebox:jukebox?depth=unbounded HTTP/1.1 Host: example.com - Accept: application/yang.data+json, - application/yang.errors+json + Accept: application/yang.data+json The server might respond: HTTP/1.1 200 OK Date: Mon, 23 Apr 2012 17:11:30 GMT Server: example-server Cache-Control: no-cache Pragma: no-cache Content-Type: application/yang.data+json @@ -4256,50 +4297,49 @@ } ] }, "playlist" : [ { "name" : "Foo-One", "description" : "example playlist 1", "song" : [ { "index" : 1, - "id" : "http://example.com/restconf/data/ + "id" : "https://example.com/restconf/data/ example-jukebox:jukebox/library/artist= Foo%20Fighters/album/Wasting%20Light/ song/Rope" }, { "index" : 2, - "id" : "http://example.com/restconf/data/ + "id" : "https://example.com/restconf/data/ example-jukebox:jukebox/library/artist= Foo%20Fighters/album/Wasting%20Light/song/ Bridge%20Burning" } ] } ], "player" : { "gap" : 0.5 } } } Example 2: depth=1 To determine if 1 or more resource instances exist for a given target resource, the value "1" is used. GET /restconf/data/example-jukebox:jukebox?depth=1 HTTP/1.1 Host: example.com - Accept: application/yang.data+json, - application/yang.errors+json + Accept: application/yang.data+json The server might respond: HTTP/1.1 200 OK Date: Mon, 23 Apr 2012 17:11:30 GMT Server: example-server Cache-Control: no-cache Pragma: no-cache Content-Type: application/yang.data+json @@ -4307,22 +4347,21 @@ "example-jukebox:jukebox" : [null] } Example 3: depth=3 To limit the depth level to the target resource plus 2 child resource layers the value "3" is used. GET /restconf/data/example-jukebox:jukebox?depth=3 HTTP/1.1 Host: example.com - Accept: application/yang.data+json, - application/yang.errors+json + Accept: application/yang.data+json The server might respond: HTTP/1.1 200 OK Date: Mon, 23 Apr 2012 17:11:30 GMT Server: example-server Cache-Control: no-cache Pragma: no-cache Content-Type: application/yang.data+json @@ -4337,52 +4376,51 @@ "description" : "example playlist 1", "song" : [ null ] } ], "player" : { "gap" : 0.5 } } } -D.3.3. "select" Parameter +D.3.3. "fields" Parameter In this example the client is retrieving the API resource, but - selecting only the "name" and "revision" nodes from each module, in + retrieving only the "name" and "revision" nodes from each module, in JSON format: - GET /restconf/data?select=modules/module(name;revision) HTTP/1.1 + GET /restconf/data?fields=modules/module(name;revision) HTTP/1.1 Host: example.com - Accept: application/yang.data+json, - application/yang.errors+json + Accept: application/yang.data+json The server might respond as follows. HTTP/1.1 200 OK Date: Mon, 23 Apr 2012 17:01:00 GMT Server: example-server Content-Type: application/yang.data+json { "ietf-yang-library:modules": { "module": [ { "name" : "example-jukebox", "revision" : "2014-07-03" }, { "name" : "ietf-restconf-monitoring", - "revision" : "2014-10-25" + "revision" : "2015-01-30" }, { "name" : "ietf-yang-library", - "revision" : "2014-10-25" + "revision" : "2015-01-30" } ] } } D.3.4. "insert" Parameter In this example, a new first entry in the "Foo-One" playlist is being created. @@ -4400,21 +4438,21 @@ artist=Foo%20Fighters/album/Wasting%20Light/song/Rope" } } Response from server: HTTP/1.1 201 Created Date: Mon, 23 Apr 2012 13:01:20 GMT Server: example-server Last-Modified: Mon, 23 Apr 2012 13:01:20 GMT - Location: http://example.com/restconf/data/ + Location: https://example.com/restconf/data/ example-jukebox:jukebox/playlist=Foo-One/song=1 ETag: eeeada438af D.3.5. "point" Parameter In this example, the client is inserting a new "song" resource within an "album" resource after another song. The request URI is split for display purposes only. Request from client: @@ -4432,98 +4470,25 @@ "name" : "Rope", "location" : "/media/foo/a7/rope.mp3", "format" : "MP3", "length" : 259 } } Response from server: HTTP/1.1 204 No Content - Date: Mon, 23 Apr 2012 13:01:20 GMT - Server: example-server - Last-Modified: Mon, 23 Apr 2012 13:01:20 GMT - ETag: abcada438af - -D.3.6. "limit" Parameter - In this example, the client requests the first two "album" resources - for a given artist: - - Request from client: - - GET /restconf/data/example-jukebox:jukebox/ - library/artist=Foo%20Fighters/album/?limit=2 HTTP/1.1 - Host: example.com - Content-Type: application/yang.collection+xml - - Response from server: - - HTTP/1.1 200 OK - Date: Mon, 23 Apr 2012 17:01:00 GMT - Server: example-server - Cache-Control: no-cache - Pragma: no-cache - Content-Type: application/yang.collection+xml - - - Foo Fighters - 1995 - ... - - - The Color and the Shape - 1997 - ... - - - -D.3.7. "offset" Parameter - - In this example, the client requests the next two albums, i.e., two - albums starting from two. - - Request from client: - - GET /restconf/data/example-jukebox:jukebox/ - library/artist=Foo%20Fighters/album/?limit=2&offset=2 HTTP/1.1 - Host: example.com - Content-Type: application/yang.collection+json - - Response from server: - - HTTP/1.1 200 OK - Date: Mon, 23 Apr 2012 17:02:00 GMT - Server: example-server - Cache-Control: no-cache - Pragma: no-cache - Content-Type: application/yang.collection+json - - { - "collection": { - "example-jukebox:album" : [ - { - "year" : 1999, - "name" : "There is Nothing Left to Loose", - ... - }, - { - "year" : 2002, - "name" : "One by One", - ... - } - ] - } - } + 1. Date: Mon, 23 Apr 2012 13:01:20 GMT Server: example-server Last- + Modified: Mon, 23 Apr 2012 13:01:20 GMT ETag: abcada438af -D.3.8. "filter" Parameter +D.3.6. "filter" Parameter The following URIs show some examples of notification filter specifications (lines wrapped for display purposes only): // filter = /event/event-class='fault' GET /mystreams/NETCONF?filter=%2Fevent%2Fevent-class%3D'fault' // filter = /event/severity<=4 GET /mystreams/NETCONF?filter=%2Fevent%2Fseverity%3C%3D4 @@ -4538,30 +4503,89 @@ GET /mystreams/critical-syslog? filter=%2F*%2Femail-addr[contains(.%2C'company.com')] // Note: the module name is used as prefix. // filter = (/example-mod:event1/name='joe' and // /example-mod:event1/status='online') GET /mystreams/NETCONF? filter=(%2Fexample-mod%3Aevent1%2Fname%3D'joe'%20and %20%2Fexample-mod%3Aevent1%2Fstatus%3D'online') -D.3.9. "start-time" Parameter +D.3.7. "start-time" Parameter // start-time = 2014-10-25T10:02:00Z GET /mystreams/NETCONF?start-time=2014-10-25T10%3A02%3A00Z -D.3.10. "stop-time" Parameter +D.3.8. "stop-time" Parameter // stop-time = 2014-10-25T12:31:00Z GET /mystreams/NETCONF?stop-time=2014-10-25T12%3A31%3A00Z +D.3.9. "with-defaults" Parameter + + Assume the same data model as defined in Appendix A.1 of [RFC6243]. + Assume the same data set as defined in Appendix A.2 of [RFC6243]. If + the server defaults-uri basic-mode is "trim", the the following + request for interface "eth1" might be as follows: + + Without query parameter: + + GET /restconf/data/interfaces/interface=eth1 HTTP/1.1 + Host: example.com + Accept: application/yang.data+json + + The server might respond as follows. + + HTTP/1.1 200 OK + Date: Mon, 23 Apr 2012 17:01:00 GMT + Server: example-server + Content-Type: application/yang.data+json + + { + "example:interface": [ + { + "name" : "eth1", + "status" : "up" + } + ] + } + + Note that the "mtu" leaf is missing because it is set to the default + "1500", and the server defaults handling basic-mode is "trim". + + With query parameter: + + GET /restconf/data/interfaces/interface=eth1 + ?with-defaults=report-all HTTP/1.1 + Host: example.com + Accept: application/yang.data+json + + The server might respond as follows. + + HTTP/1.1 200 OK + Date: Mon, 23 Apr 2012 17:01:00 GMT + Server: example-server + Content-Type: application/yang.data+json + + { + "example:interface": [ + { + "name" : "eth1", + "mtu" : 1500, + "status" : "up" + } + ] + } + + Note that the server returns the "mtu" leaf because the "report-all" + mode was requested with the "with-defaults" query parameter. + Authors' Addresses Andy Bierman YumaWorks Email: andy@yumaworks.com Martin Bjorklund Tail-f Systems