A NETCONF Extension for Data Fragmentation
draft-zheng-netconf-fragmentation-01
The information below is for an old version of the document |
Document |
Type |
|
Active Internet-Draft (individual)
|
|
Last updated |
|
2018-06-20
|
|
Stream |
|
(None)
|
|
Intended RFC status |
|
(None)
|
|
Formats |
|
plain text
pdf
html
bibtex
|
Stream |
Stream state |
|
(No stream defined) |
|
Consensus Boilerplate |
|
Unknown
|
|
RFC Editor Note |
|
(None)
|
IESG |
IESG state |
|
I-D Exists
|
|
Telechat date |
|
|
|
Responsible AD |
|
(None)
|
|
Send notices to |
|
(None)
|
Netconf G. Zheng
Internet-Draft M. Wang
Intended status: Informational Huawei
Expires: December 22, 2018 June 20, 2018
A NETCONF Extension for Data Fragmentation
draft-zheng-netconf-fragmentation-01
Abstract
This document introduces an extension to NETCONF (Network
Configuration) protocol. The extension allows NETCONF to handle
large size data as fragmented RPC messages. Specifically, this
document defines a new <get-block> capability and relevant operations
to handle the fragmentations.
Status of This Memo
This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79.
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 https://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 December 22, 2018.
Copyright Notice
Copyright (c) 2018 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
(https://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.
Zheng & Wang Expires December 22, 2018 [Page 1]
Internet-Draft Netconf Fragmentation June 2018
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Concept and Terminology . . . . . . . . . . . . . . . . . . . 3
2.1. Terminology . . . . . . . . . . . . . . . . . . . . . . . 3
3. Current Large size Handling Methods and Problems . . . . . . 3
3.1. Stream-Oriented Handling . . . . . . . . . . . . . . . . 3
3.2. Requesting a Portion of Data . . . . . . . . . . . . . . 4
3.3. Using tools to extract data respectively . . . . . . . . 4
4. Netconf Fragmentation Mechanism . . . . . . . . . . . . . . . 5
4.1. Fragmentation Requirements . . . . . . . . . . . . . . . 5
4.2. <get-block> extention . . . . . . . . . . . . . . . . . . 5
5. YANG data model . . . . . . . . . . . . . . . . . . . . . . . 6
6. Security Considerations . . . . . . . . . . . . . . . . . . . 8
7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 8
8. Normative References . . . . . . . . . . . . . . . . . . . . 8
Appendix A. Appendix A: Examples of the Candidate Solutions . . 9
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 10
1. Introduction
NETCONF [RFC6241] is the next generation network management protocol
for configuring devices. It is becoming more and more popular, and
some NMS (Network Management System) only use NETCONF as its
southbound interface. The message procedures of NETCONF are based on
RPC (Remote Procedure Call) interactions. A NETCONF client/server
sends a <rpc> message to the counterpart and then receives a replying
<rpc-reply> message.
In some situations, the <rpc-reply> message might be very large. For
example, when NMS is retrieving a large amount of routes in a core
router or doing a full-synchronizing with a device, the <rpc-reply>
data might exceed Mega-Byte amount. And also in some scenarios, the
client may retrieve a continuous stream of operational data from the
operational datastore [I-D.ietf-netmod-revised-datastores] to perform
network analytics. Then there comes the problem of how to handle the
large size data. This document briefly introduces two typical ways
of current handling on this issue; and analyzes the problems of them.
To fix the problems, in Section 4, this document proposes a method of
extending the NETCONF protocol to allow handling large size data as
fragmented <rpc-reply> messages. The fragmentation is done at the
NETCONF level, so it allows the NETCONF client to terminate the large
size data processing momentarily by protocol interactions; and also
allows the fragmented messages to be instantly parsed piece by piece.
Show full document text