RESTCONF Extensions to Support List Pagination

RESTCONF Extensions to Support List Pagination Watsen Network

kent+ietf@watsen.net

Huawei

101 Software Avenue, Yuhua District Nanjing Jiangsu 210012 China bill.wu@huawei.com

Netgate

olof@hagsand.se

HPE

flycoolman@gmail.com

OPS Area NETCONF Working Group In some circumstance, a server may contain many instances of a particular YANG list or leaf-list. Retrieval of the entire list or leaf-list at once can be extremely inefficient. Pagination mechanisms are needed to allow a client to iterate through a large list, in a manner that is most efficient for the application. This document Updates RFC 8040 to declare "list" and "leaf-list" as resource targets for the RESTCONF operations such as GET, POST operations.

There is a need for standard mechanisms to control the filtering, sorting, and retrieval of data from the server. A server may contain many instances of a particular YANG list. Retrieval of the entire list or leaf-list at once can be extremely inefficient. Pagination mechanisms are needed to allow a client to iterate through a large list, in a manner that is most efficient for the application. The RPC operation defined in [I-D.wwlh-netconf-list-pagination-nc] can be used by the RESTCONF protocol if the RESTCONF server implements the "ietf-yang-list-pagination" module [I-D.wwlh-netconf-list-pagination-nc]. This document Updates RFC 8040 to declare "list" and "leaf-list" as resource targets for the RESTCONF operations such as GET, POST operations.

The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in BCP 14 when, and only when, they appear in all capitals, as shown here. The following terms are defined in and are not redefined here: server startup configuration datastore candidate configuration datastore running configuration datastore intended configuration datastore operational state datastore conventional configuration datastore datastore schema RPC operation The following terms are defined in this document as follows:

This section describes the RESTCONF extensions needed to support the Pagination mechanism.

The following resource type is defined in this document:

The "get-list-pagination" RPC operation defined in "ietf-yang-list-pagination" module [I-D.wwlh-netconf-list-pagination-nc] can use the RESTCONF target resource URI to identify the resource that will be filtered and returned. A collection resource contains a set of data resources. It is used to represent all instances or a subset of all instances in a YANG list or leaf-list. A collection resource can be used as target resource and retrieved with the GET method or POST method. The "ietf-restconf-list-pagination" YANG module contains the "yang-collection" yang data template with the "yang-data"extension which specifies the syntax and semantics of a "yang-collection" media type.

The "ietf-restconf-list-pagination" module defines conceptual definitions within groupings, which are not meant to be implemented as datastore contents by a server.

<CODE BEGINS> file "ietf-restconf-list-pagination@2020-11-02.yang" WG List: "; description "This module contains conceptual YANG specifications for the RESTCONF Collection resource type. 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. 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."; revision 2015-01-30 { description "Initial revision."; reference "RFC XXXX: RESTCONF Collection Resource."; } rc:yang-data yang-collection { uses collection; } grouping collection { description "Conceptual container representing the yang-collection resource type."; container yang-collection { description "Container representing the yang-collection resource type."; } } } ]]> <CODE ENDS>

This document registers one URI in the "ns" subregistry of the IETF XML Registry maintained at . Following the format in , the following registration is requested:

URI: urn:ietf:params:xml:ns:yang:ietf-restconf-list-pagination Registrant Contact: The IESG. XML: N/A, the requested URI is an XML namespace.

This document registers one YANG module in the YANG Module Names registry maintained at . Following the format defined in , the below registration is requested:

name: ietf-restconf-list-pagination namespace: urn:ietf:params:xml:ns:yang:ietf-restconf-list-pagination prefix: rlpg RFC: xxxx

This document registers two media types in the "application" subregistry of the Media Types registry maintained at Following the format defined in , the below registrations are requested:

Type name: application Subtype name: yang-collection+xml Required parameters: None Optional parameters: None Encoding considerations: 8-bit The "utf-8" charset is always used for this type. Each conceptual YANG data node is encoded according to the XML Encoding Rules and Canonical Format for the specific YANG data node type defined in RFC 7950. Security considerations: Security considerations related to the generation and consumption of RESTCONF messages are discussed in Section 5 of RFC 8072. Additional security considerations are specific to the semantics of particular YANG data models. Each YANG module is expected to specify security considerations for the YANG data defined in that module. Interoperability considerations: RFC 8072 specifies the format of conforming messages and the interpretation thereof. Published specification: RFC 8072 Applications that use this media type: Instance document data parsers used within a protocol or automation tool that utilize the YANG Patch data structure. Fragment identifier considerations: The syntax and semantics of fragment identifiers are the same as the syntax and semantics specified for the "application/xml" media type. Additional information: Deprecated alias names for this type: N/A Magic number(s): N/A File extension(s): None Macintosh file type code(s): "TEXT" Person & email address to contact for further information: See the Authors' Addresses section of RFC 8072. Intended usage: COMMON Restrictions on usage: N/A Author: See the Authors' Addresses section of RFC 8072. Change controller: Internet Engineering Task Force (mailto:iesg@ietf.org). Provisional registration? (standards tree only): no

Type name: application Subtype name: yang-collection+json Required parameters: None Optional parameters: None Encoding considerations: 8-bit The "utf-8" charset is always used for this type. Each conceptual YANG data node is encoded according to the XML Encoding Rules and Canonical Format for the specific YANG data node type defined in RFC 7950. Security considerations: Security considerations related to the generation and consumption of RESTCONF messages are discussed in Section 5 of RFC 8072. Additional security considerations are specific to the semantics of particular YANG data models. Each YANG module is expected to specify security considerations for the YANG data defined in that module. Interoperability considerations: RFC 8072 specifies the format of conforming messages and the interpretation thereof. Published specification: RFC 8072 Applications that use this media type: Instance document data parsers used within a protocol or automation tool that utilize the YANG Patch data structure. Fragment identifier considerations: The syntax and semantics of fragment identifiers are the same as the syntax and semantics specified for the "application/xml" media type. Additional information: Deprecated alias names for this type: N/A Magic number(s): N/A File extension(s): None Macintosh file type code(s): "TEXT" Person & email address to contact for further information: See the Authors' Addresses section of RFC 8072. Intended usage: COMMON Restrictions on usage: N/A Author: See the Authors' Addresses section of RFC 8072. Change controller: Internet Engineering Task Force (mailto:iesg@ietf.org). Provisional registration? (standards tree only): no

The YANG module defined in this document extends the base operations for NETCONF and RESTCONF . The lowest NETCONF layer is the secure transport layer, and the mandatory-to-implement secure transport is Secure Shell (SSH) . The lowest RESTCONF layer is HTTPS, and the mandatory-to-implement secure transport is TLS . The Network Configuration Access Control Model (NACM) provides the means to restrict access for particular NETCONF users to a preconfigured subset of all available NETCONF protocol operations and content. The security constraints for the base RESTCONF protocol (see Section 12 of ) apply to the new RESTCONF target resources defined in this document.

The examples within this document use the "example-module" YANG module defined in Appendix A of [I-D.wwlh-netconf-list-pagination-nc].

FIXME

Client requests all list entries:

Client requests an XML-based Response:

Response from the RESTCONF server: