RFC 6244: An Architecture for Network Management Using NETCONF and YANG
In plain English — editorial summary, not part of the RFC
The Network Configuration Protocol (NETCONF) gives access to native capabilities of the devices within a network, defining methods for manipulating configuration databases, retrieving operational data, and invoking specific operations. YANG provides the means to define the content carried via NETCONF, both data and operations. Using both technologies, standard modules can be defined to give interoperability and commonality to devices, while still allowing devices to express their unique capabilities. This document describes how NETCONF and YANG help build network management applications that meet the needs of network operators. This document is not an Internet Standards Track specification; it is published for informational purposes.
Document record
- Document ID
- RFC6244
- Published
- June 2011
- Authors
- P. Shafer
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- ops
- Pages
- 30
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 6243With-defaults Capability for NETCONFCurrent
June 2011
- RFC 6242Using the NETCONF Protocol over Secure Shell (SSH)Current
June 2011
- RFC 4742Using the NETCONF Configuration Protocol over Secure SHell (SSH)Obsoleted
December 2006
- RFC 4741NETCONF Configuration ProtocolObsoleted
December 2006
- RFC 5607Remote Authentication Dial-In User Service (RADIUS) Authorization for Network Access Server (NAS) ManagementCurrent
July 2009
- RFC 5381Experience of Implementing NETCONF over SOAPCurrent
October 2008
- RFC 6241Network Configuration Protocol (NETCONF)Updated
June 2011
- RFC 6248RFC 4148 and the IP Performance Metrics (IPPM) Registry of Metrics Are ObsoleteCurrent
April 2011
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?