Network Configuration Protocol (NETCONF)
RFC 6241
Document | Type |
RFC - Proposed Standard
(June 2011; Errata)
Obsoletes RFC 4741
|
|||||
---|---|---|---|---|---|---|---|
Authors | Rob Enns , Martin Björklund , Andy Bierman , Jürgen Schönwälder | ||||||
Last updated | 2020-01-21 | ||||||
Stream | Internent Engineering Task Force (IETF) | ||||||
Formats | plain text html pdf htmlized (tools) htmlized with errata bibtex | ||||||
Yang Validation | ☯ 0 errors, 1 warnings. | ||||||
Reviews | |||||||
Additional Resources |
|
||||||
Stream | WG state | WG Document | |||||
Document shepherd | No shepherd assigned | ||||||
IESG | IESG state | RFC 6241 (Proposed Standard) | |||||
Action Holders |
(None)
|
||||||
Consensus Boilerplate | Unknown | ||||||
Telechat date | |||||||
Responsible AD | Dan Romascanu | ||||||
IESG note | Bert Wijnen (bertietf@bwijnen.net) is the document shepherd. | ||||||
Send notices to | (None) |
Internet Engineering Task Force (IETF) R. Enns, Ed. Request for Comments: 6241 Juniper Networks Obsoletes: 4741 M. Bjorklund, Ed. Category: Standards Track Tail-f Systems ISSN: 2070-1721 J. Schoenwaelder, Ed. Jacobs University A. Bierman, Ed. Brocade June 2011 Network Configuration Protocol (NETCONF) Abstract The Network Configuration Protocol (NETCONF) defined in this document provides mechanisms to install, manipulate, and delete the configuration of network devices. It uses an Extensible Markup Language (XML)-based data encoding for the configuration data as well as the protocol messages. The NETCONF protocol operations are realized as remote procedure calls (RPCs). This document obsoletes RFC 4741. Status of This Memo This is an Internet Standards Track document. This document is a product of the Internet Engineering Task Force (IETF). It represents the consensus of the IETF community. It has received public review and has been approved for publication by the Internet Engineering Steering Group (IESG). Further information on Internet Standards is available in Section 2 of RFC 5741. Information about the current status of this document, any errata, and how to provide feedback on it may be obtained at http://www.rfc-editor.org/info/rfc6241. Enns, et al. Standards Track [Page 1] RFC 6241 NETCONF Protocol June 2011 Copyright Notice Copyright (c) 2011 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. This document may contain material from IETF Documents or IETF Contributions published or made publicly available before November 10, 2008. The person(s) controlling the copyright in some of this material may not have granted the IETF Trust the right to allow modifications of such material outside the IETF Standards Process. Without obtaining an adequate license from the person(s) controlling the copyright in such materials, this document may not be modified outside the IETF Standards Process, and derivative works of it may not be created outside the IETF Standards Process, except to format it for publication as an RFC or to translate it into languages other than English. Enns, et al. Standards Track [Page 2] RFC 6241 NETCONF Protocol June 2011 Table of Contents 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 6 1.1. Terminology . . . . . . . . . . . . . . . . . . . . . . . 7 1.2. Protocol Overview . . . . . . . . . . . . . . . . . . . . 8 1.3. Capabilities . . . . . . . . . . . . . . . . . . . . . . 10 1.4. Separation of Configuration and State Data . . . . . . . 10 2. Transport Protocol Requirements . . . . . . . . . . . . . . . 11 2.1. Connection-Oriented Operation . . . . . . . . . . . . . . 11 2.2. Authentication, Integrity, and Confidentiality . . . . . 12 2.3. Mandatory Transport Protocol . . . . . . . . . . . . . . 12 3. XML Considerations . . . . . . . . . . . . . . . . . . . . . 13 3.1. Namespace . . . . . . . . . . . . . . . . . . . . . . . . 13 3.2. Document Type Declarations . . . . . . . . . . . . . . . 13 4. RPC Model . . . . . . . . . . . . . . . . . . . . . . . . . . 13 4.1. <rpc> Element . . . . . . . . . . . . . . . . . . . . . . 13 4.2. <rpc-reply> Element . . . . . . . . . . . . . . . . . . . 15 4.3. <rpc-error> Element . . . . . . . . . . . . . . . . . . . 16 4.4. <ok> Element . . . . . . . . . . . . . . . . . . . . . . 19 4.5. Pipelining . . . . . . . . . . . . . . . . . . . . . . . 19 5. Configuration Model . . . . . . . . . . . . . . . . . . . . . 19 5.1. Configuration Datastores . . . . . . . . . . . . . . . . 19 5.2. Data Modeling . . . . . . . . . . . . . . . . . . . . . . 20Show full document text