{"id":1146,"date":"2017-10-30T19:06:00","date_gmt":"2017-10-30T19:06:00","guid":{"rendered":"https:\/\/fir3netwp.gmsrrpobkbd.com\/2017\/10\/30\/an-introduction-to-netconf-yang\/"},"modified":"2021-07-31T17:07:35","modified_gmt":"2021-07-31T17:07:35","slug":"an-introduction-to-netconf-yang","status":"publish","type":"post","link":"https:\/\/www.fir3net.com\/Networking\/Protocols\/an-introduction-to-netconf-yang.html","title":{"rendered":"An Introduction to NETCONF\/YANG"},"content":{"rendered":"<div id=\"ez-toc-container\" class=\"ez-toc-v2_0_65 counter-hierarchy ez-toc-counter ez-toc-grey ez-toc-container-direction\">\n<p class=\"ez-toc-title\">Table of Contents<\/p>\n<label for=\"ez-toc-cssicon-toggle-item-662966df3146a\" class=\"ez-toc-cssicon-toggle-label\"><span class=\"\"><span class=\"eztoc-hide\" style=\"display:none;\">Toggle<\/span><span class=\"ez-toc-icon-toggle-span\"><svg style=\"fill: #999;color:#999\" xmlns=\"http:\/\/www.w3.org\/2000\/svg\" class=\"list-377408\" width=\"20px\" height=\"20px\" viewBox=\"0 0 24 24\" fill=\"none\"><path d=\"M6 6H4v2h2V6zm14 0H8v2h12V6zM4 11h2v2H4v-2zm16 0H8v2h12v-2zM4 16h2v2H4v-2zm16 0H8v2h12v-2z\" fill=\"currentColor\"><\/path><\/svg><svg style=\"fill: #999;color:#999\" class=\"arrow-unsorted-368013\" xmlns=\"http:\/\/www.w3.org\/2000\/svg\" width=\"10px\" height=\"10px\" viewBox=\"0 0 24 24\" version=\"1.2\" baseProfile=\"tiny\"><path d=\"M18.2 9.3l-6.2-6.3-6.2 6.3c-.2.2-.3.4-.3.7s.1.5.3.7c.2.2.4.3.7.3h11c.3 0 .5-.1.7-.3.2-.2.3-.5.3-.7s-.1-.5-.3-.7zM5.8 14.7l6.2 6.3 6.2-6.3c.2-.2.3-.5.3-.7s-.1-.5-.3-.7c-.2-.2-.4-.3-.7-.3h-11c-.3 0-.5.1-.7.3-.2.2-.3.5-.3.7s.1.5.3.7z\"\/><\/svg><\/span><\/span><\/label><input type=\"checkbox\"  id=\"ez-toc-cssicon-toggle-item-662966df3146a\"  aria-label=\"Toggle\" \/><nav><ul class='ez-toc-list ez-toc-list-level-1 ' ><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-1\" href=\"https:\/\/www.fir3net.com\/Networking\/Protocols\/an-introduction-to-netconf-yang.html\/#TLDR\" title=\"TL;DR\">TL;DR<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-2\" href=\"https:\/\/www.fir3net.com\/Networking\/Protocols\/an-introduction-to-netconf-yang.html\/#Introduction\" title=\"Introduction\">Introduction<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-3\" href=\"https:\/\/www.fir3net.com\/Networking\/Protocols\/an-introduction-to-netconf-yang.html\/#YANG\" title=\"YANG\">YANG<\/a><ul class='ez-toc-list-level-3' ><li class='ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-4\" href=\"https:\/\/www.fir3net.com\/Networking\/Protocols\/an-introduction-to-netconf-yang.html\/#OpenNative_Models\" title=\"Open\/Native Models\">Open\/Native Models<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-5\" href=\"https:\/\/www.fir3net.com\/Networking\/Protocols\/an-introduction-to-netconf-yang.html\/#Components\" title=\"Components\">Components<\/a><\/li><\/ul><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-6\" href=\"https:\/\/www.fir3net.com\/Networking\/Protocols\/an-introduction-to-netconf-yang.html\/#NETCONF\" title=\"NETCONF\">NETCONF<\/a><ul class='ez-toc-list-level-3' ><li class='ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-7\" href=\"https:\/\/www.fir3net.com\/Networking\/Protocols\/an-introduction-to-netconf-yang.html\/#Protocol_Stack\" title=\"Protocol Stack\">Protocol Stack<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-8\" href=\"https:\/\/www.fir3net.com\/Networking\/Protocols\/an-introduction-to-netconf-yang.html\/#Communication\" title=\"Communication\">Communication<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-9\" href=\"https:\/\/www.fir3net.com\/Networking\/Protocols\/an-introduction-to-netconf-yang.html\/#Operations\" title=\"Operations\">Operations<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-10\" href=\"https:\/\/www.fir3net.com\/Networking\/Protocols\/an-introduction-to-netconf-yang.html\/#Configuration_Datastores\" title=\"Configuration Datastores\">Configuration Datastores<\/a><\/li><\/ul><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-11\" href=\"https:\/\/www.fir3net.com\/Networking\/Protocols\/an-introduction-to-netconf-yang.html\/#References\" title=\"References\">References<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-12\" href=\"https:\/\/www.fir3net.com\/Networking\/Protocols\/an-introduction-to-netconf-yang.html\/#Further_Reading\" title=\"Further Reading\">Further Reading<\/a><\/li><\/ul><\/nav><\/div>\n<h2 id=\"h.fa43prmy0vqw\" class=\"c25\"><span class=\"ez-toc-section\" id=\"TLDR\"><\/span><span class=\"c15 c1 c16\">TL;DR<\/span><span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p class=\"c12\"><strong>NETCONF\/YANG<\/strong> provides a standardized way to programmatically\u00a0update and modify the configuration of a network device. To break this down further. <strong>YANG<\/strong> is the <em>modelling language<\/em> that describes the configuration changes. Whereas \u00a0<strong>NETCONF<\/strong> is the <em>protocol<\/em> that applies the changes to the relevant datastore (i.e running, saved etc) upon the device.<\/p>\n<h2 id=\"h.dg2wibqv471c\" class=\"c25\"><span class=\"ez-toc-section\" id=\"Introduction\"><\/span><span class=\"c15 c1 c16\">Introduction<\/span><span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p class=\"c12\">Let us start with the problem. <span class=\"c4 c1\">Historically, the main method of configuring a networking device had been via the CLI or in some cases SNMP. However these methods presented a number of issues. Such as:<\/span><\/p>\n<p class=\"c12\"><strong><span class=\"c14 c19\">CLI disadvantages<\/span><\/strong><span class=\"c4 c1\">,<\/span><\/p>\n<ul class=\"c3 lst-kix_osbkw06ytp8s-0 start\">\n<li class=\"c10\"><span class=\"c4 c1\">The CLI INPUT (commands) differs from vendor to vendor.<\/span><\/li>\n<li class=\"c10\"><span class=\"c4 c1\">The CLI OUTPUT from each vendor differs. Requiring separate parsing logic for each vendor.<\/span><\/li>\n<li class=\"c10\"><span class=\"c4 c1\">The CLI structure and syntax are prone to changes. Making our CLI scripts fragile.<\/span><\/li>\n<\/ul>\n<p class=\"c12\"><strong><span class=\"c14 c19\">SNMP disadvantages<\/span><\/strong><span class=\"c4 c1\">,<\/span><\/p>\n<ul class=\"c3 lst-kix_q51u7aimwv8-0 start\">\n<li class=\"c10\"><span class=\"c4 c1\">Unreliable as it inherently uses UDP as its transport protocol.<\/span><\/li>\n<li class=\"c10\"><span class=\"c1\">Traditionally insecure. Though SNMPv3 looks to address this, it still comes with its own security challenges. Mainly being the discovery messages used to negotiate the authentication and encryption keys are neither authenticated nor encrypted.<\/span><sup class=\"c1\"><a id=\"ftnt_ref1\" href=\"#ftnt1\">[1]<\/a><\/sup><\/li>\n<li class=\"c10\"><span class=\"c4 c1\">No clear delimiter between configuration data and monitoring data. Resulting in additional logic having to be performed on the client side in order to sort.<\/span><\/li>\n<li class=\"c10\"><span class=\"c1 c18\">Lacks standard MIBs for configuring networks. That is why, vendors have developed various proprietary MIBs which become a barrier to managing cross vendor platforms.<\/span><sup class=\"c1 c18\"><a id=\"ftnt_ref2\" href=\"#ftnt2\">[2]<\/a><\/sup><\/li>\n<li class=\"c10\"><span class=\"c1 c18\">Provides no real transactional operation model, to allow for simple rollbacks etc.<\/span><\/li>\n<\/ul>\n<p class=\"c12\"><span class=\"c4 c1\">With the adoption of network automation increasing (such as SDN, think NBI) there was a need to standardize and improve the way that networking devices were programmed. A way that provided,<\/span><\/p>\n<ul class=\"c3 lst-kix_hjq6927tevnf-0 start\">\n<li class=\"c10\"><span class=\"c4 c1\">A programmatic interface for device configuration.<\/span><\/li>\n<li class=\"c10\"><span class=\"c4 c1\">Separation of configuration and state data.<\/span><\/li>\n<li class=\"c10\"><span class=\"c4 c1\">The ability to configure services not just devices.<\/span><\/li>\n<li class=\"c10\"><span class=\"c4 c1\">Integrated error checking and recovery.<\/span><\/li>\n<\/ul>\n<p class=\"c12\"><span class=\"c4 c1\">The solution to this issue came from the IETF, in the form of NETCONF and YANG. In its simplest form (and to recap our previous TL;DR) YANG provides a language to describe your desired configuration (or state). NETCONF, on the other hand provides the protocol to deliver and perform the required operations in order to achieve the desired state, described within the YANG model.<\/span><\/p>\n<p class=\"c12\" style=\"text-align: center;\"><picture><source srcset=\"https:\/\/www.fir3net.com\/wp-content\/uploads\/2017\/10\/images_articles_netconf-stack6.avif 548w,https:\/\/www.fir3net.com\/wp-content\/uploads\/2017\/10\/images_articles_netconf-stack6-300x230.avif 300w\" sizes=\"(max-width: 548px) 100vw, 548px\" type=\"image\/avif\"><source srcset=\"https:\/\/www.fir3net.com\/wp-content\/uploads\/2017\/10\/images_articles_netconf-stack6.webp 548w,https:\/\/www.fir3net.com\/wp-content\/uploads\/2017\/10\/images_articles_netconf-stack6-300x230.webp 300w\" sizes=\"(max-width: 548px) 100vw, 548px\" type=\"image\/webp\"><img src=\"https:\/\/www.fir3net.com\/wp-content\/uploads\/2017\/10\/images_articles_netconf-stack6.png\" height=\"420\" width=\"548\" srcset=\"https:\/\/www.fir3net.com\/wp-content\/uploads\/2017\/10\/images_articles_netconf-stack6.png 548w, https:\/\/www.fir3net.com\/wp-content\/uploads\/2017\/10\/images_articles_netconf-stack6-300x230.png 300w\" sizes=\"(max-width: 548px) 100vw, 548px\" class=\" size-full wp-image-1142 sp-no-webp\" alt=\"netconf-stack6\" loading=\"lazy\" decoding=\"async\"  > <\/picture><\/p>\n<p class=\"c12\" style=\"text-align: center;\"><strong>Figure 1<\/strong>\u00a0&#8211; NETCONF\/YANG Stack.<\/p>\n<h2 class=\"c12\"><span class=\"ez-toc-section\" id=\"YANG\"><\/span>YANG<span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p class=\"c12\"><span class=\"c1\"><strong>YANG (Yet Another Next Generation)<\/strong> is a data modelling language, providing a standardized way to <\/span><span class=\"c1\">model the operational and configuration data of a network device. YANG, being a language is <\/span><span class=\"c1 c18 c39\">being protocol independent, can then be converted into any encoding format, e.g. <\/span><span class=\"c1 c31 c18\"><a class=\"c6\" href=\"https:\/\/www.google.com\/url?q=https:\/\/en.wikipedia.org\/wiki\/XML&amp;sa=D&amp;ust=1508706139373000&amp;usg=AFQjCNEI75uaX_kEWMOFH1a4yHJoLuVA_w\">XML<\/a><\/span><span class=\"c1 c39 c18\">\u00a0or <\/span><span class=\"c1 c18 c31\"><a class=\"c6\" href=\"https:\/\/www.google.com\/url?q=https:\/\/en.wikipedia.org\/wiki\/JSON&amp;sa=D&amp;ust=1508706139374000&amp;usg=AFQjCNElET0UaXR6buRlPvYzqseBiMI__A\">JSON<\/a><\/span><span class=\"c1\">.<\/span><sup class=\"c1\"><a id=\"ftnt_ref3\" href=\"#ftnt3\">[3]<\/a><\/sup><\/p>\n<h3 id=\"h.117ej946q0nx\" class=\"c24\"><span class=\"ez-toc-section\" id=\"OpenNative_Models\"><\/span><span class=\"c26 c1\">Open\/Native Models<\/span><span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p class=\"c12\"><span class=\"c4 c1\">You may be asking who creates these models? The models are classified as either Open or Native based, with different groups working across each one.<\/span><\/p>\n<ul class=\"c3 lst-kix_ie2oklmzrzgr-0 start\">\n<li class=\"c10\"><strong><span class=\"c14 c19\">Open Models<\/span><\/strong><span class=\"c1\">\u00a0&#8211; Designed to be independent of the underlying platform and normalize the per-vendor configuration of network devices. Open YANG Models are developed by<\/span><span class=\"c1 c18 c42\">\u00a0Vendors and Standards bodies, such as <\/span><span class=\"c1\">IETF, ITU, OpenConfig etc.<\/span><\/li>\n<li class=\"c10\"><strong><span class=\"c14 c19\">Native Models<\/span><\/strong><span class=\"c4 c1\">\u00a0&#8211; Native Models are developed by the vendors. They relate and are designed to integrate to features or configuration only relevant to that platform. <\/span><\/li>\n<\/ul>\n<h3 id=\"h.jcmxjvh7v4i\" class=\"c24\"><span class=\"ez-toc-section\" id=\"Components\"><\/span><span class=\"c26 c1\">Components<\/span><span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p class=\"c12\"><span class=\"c4 c1\">A YANG model is made up from various components. Let&#8217;s look at these components, in relation to our example (seen within Figure 2).<\/span><\/p>\n<p class=\"c12\" style=\"text-align: center;\"><picture><source srcset=\"https:\/\/www.fir3net.com\/wp-content\/uploads\/2017\/10\/images_articles_yang.avif 518w,https:\/\/www.fir3net.com\/wp-content\/uploads\/2017\/10\/images_articles_yang-300x248.avif 300w\" sizes=\"(max-width: 518px) 100vw, 518px\" type=\"image\/avif\"><source srcset=\"https:\/\/www.fir3net.com\/wp-content\/uploads\/2017\/10\/images_articles_yang.webp 518w,https:\/\/www.fir3net.com\/wp-content\/uploads\/2017\/10\/images_articles_yang-300x248.webp 300w\" sizes=\"(max-width: 518px) 100vw, 518px\" type=\"image\/webp\"><img src=\"https:\/\/www.fir3net.com\/wp-content\/uploads\/2017\/10\/images_articles_yang.png\" height=\"428\" width=\"518\" srcset=\"https:\/\/www.fir3net.com\/wp-content\/uploads\/2017\/10\/images_articles_yang.png 518w, https:\/\/www.fir3net.com\/wp-content\/uploads\/2017\/10\/images_articles_yang-300x248.png 300w\" sizes=\"(max-width: 518px) 100vw, 518px\" class=\" size-full wp-image-1143 sp-no-webp\" alt=\"yang\" loading=\"lazy\" decoding=\"async\"  > <\/picture><\/p>\n<p class=\"c12\" style=\"text-align: center;\"><strong>Figure 2<\/strong> &#8211; YANG Structure (Source : Cisco Live &#8211; DEVNET-1721).<\/p>\n<ul class=\"c3 lst-kix_3aslqa1cgqbz-0 start\">\n<li class=\"c10\"><strong><span class=\"c14 c19\">Container <\/span><\/strong><span class=\"c4 c1\">&#8211; A collection of information logically grouped. Such a container for configuration, and one for state. <\/span><\/li>\n<li class=\"c10\"><strong><span class=\"c14 c19\">List <\/span><\/strong><span class=\"c4 c1\">&#8211; Within a container you can have a list or even multiple lists. Such as a list of interfaces.<\/span><\/li>\n<li class=\"c10\"><strong><span class=\"c14 c19\">Key<\/span><\/strong><span class=\"c4 c1\">\u00a0&#8211; Each item within the list is references via a key. <\/span><\/li>\n<li class=\"c10\"><strong><span class=\"c14 c19\">Leaf <\/span><\/strong><span class=\"c4 c1\">&#8211; Inside our list we have leaf&#8217;s. Containing our information.<\/span><\/li>\n<li class=\"c10\"><strong><span class=\"c14 c19\">Data Type<\/span><\/strong><span class=\"c4 c1\">\u00a0&#8211; Each leaf is associated against a data type.<\/span><\/li>\n<\/ul>\n<h2 id=\"h.lgzx1jcsdkeu\" class=\"c30\"><span class=\"ez-toc-section\" id=\"NETCONF\"><\/span><span class=\"c15 c1 c16\">NETCONF<\/span><span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p class=\"c12\"><strong><span class=\"c1 c28 c18\">NETCONF (<\/span><span class=\"c1 c28 c18\">NETwork CONFiguration<\/span><\/strong><span class=\"c1 c18 c28\"><strong>)<\/strong> is a protocol defined by the IETF to \u201cinstall, manipulate, and delete the configuration of network devices\u201d.<\/span><sup class=\"c1 c28 c18\"><a id=\"ftnt_ref4\" href=\"#ftnt4\">[4]<\/a><\/sup><span class=\"c38 c1 c28 c18\">\u00a0NETCONF operations are performed via a RPC layer using XML based encoding.\u00a0\u00a0<\/span><\/p>\n<p class=\"c12\"><span class=\"c1 c28 c18\">Some of the key features to NETCONF are, ability to rollback configurations, ability to support any data model and the separation of config from operational state.<\/span><\/p>\n<h3 id=\"h.4omufsqr0pjh\" class=\"c24\"><span class=\"ez-toc-section\" id=\"Protocol_Stack\"><\/span><span class=\"c1 c26\">Protocol Stack<\/span><span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p class=\"c12\"><span class=\"c4 c1\">The NETCONF protocol can be broken down into 4 layers. They are,<\/span><\/p>\n<ul class=\"c3 lst-kix_t8q1q18vq6f5-0 start\">\n<li class=\"c10\"><strong><span class=\"c14 c19\">Content<\/span><\/strong><span class=\"c1\">\u00a0&#8211; <\/span><span class=\"c1\">NETCONF data models and protocol operations use the YANG modeling language (RFC 6020). A data model outlines the structure, semantics and syntax of the data.<\/span><sup class=\"c1\"><a id=\"ftnt_ref5\" href=\"#ftnt5\">[5]<\/a><\/sup><\/li>\n<li class=\"c10\"><strong><span class=\"c14 c19\">Operations<\/span><\/strong><span class=\"c1\">\u00a0&#8211; A set of <\/span><span class=\"c1\">base protocol operations initiated via by RPC methods using XML-encoding, in order to perform operations upon the device. Such as <span class=\"codeinline\">&lt;get-config&gt;<\/span>, <span class=\"codeinline\">&lt;edit-config&gt;<\/span> and <span class=\"codeinline\">&lt;get&gt;<\/span>.<\/span><\/li>\n<li class=\"c10\"><span class=\"c14 c19\"><strong>Messages<\/strong> &#8211; <\/span><span class=\"c21 c18\">A set of RPC messages and notifications are defined for use including <span class=\"codeinline\">&lt;rpc&gt;<\/span>, <span class=\"codeinline\">&lt;rpc-reply&gt;<\/span> and <span class=\"codeinline\">&lt;rpc-error&gt;<\/span>.<\/span><sup class=\"c18 c21\"><a id=\"ftnt_ref6\" href=\"#ftnt6\">[6]<\/a><\/sup><\/li>\n<li class=\"c10\"><strong><span class=\"c14 c19\">Transport<\/span><\/strong><span class=\"c4 c1\">\u00a0&#8211; The transport layer used to provide a communication path between the client\/server (manager\/agent). The protocol used is agnostic to NETCONF, but SSH is typically used.<\/span><\/li>\n<\/ul>\n<h3 class=\"c24\" style=\"text-align: center;\"><picture><source srcset=\"https:\/\/www.fir3net.com\/wp-content\/uploads\/2017\/10\/images_articles_netconf-redraw.avif 578w,https:\/\/www.fir3net.com\/wp-content\/uploads\/2017\/10\/images_articles_netconf-redraw-300x155.avif 300w\" sizes=\"(max-width: 578px) 100vw, 578px\" type=\"image\/avif\"><source srcset=\"https:\/\/www.fir3net.com\/wp-content\/uploads\/2017\/10\/images_articles_netconf-redraw.webp 578w,https:\/\/www.fir3net.com\/wp-content\/uploads\/2017\/10\/images_articles_netconf-redraw-300x155.webp 300w\" sizes=\"(max-width: 578px) 100vw, 578px\" type=\"image\/webp\"><img src=\"https:\/\/www.fir3net.com\/wp-content\/uploads\/2017\/10\/images_articles_netconf-redraw.png\" height=\"298\" width=\"578\" srcset=\"https:\/\/www.fir3net.com\/wp-content\/uploads\/2017\/10\/images_articles_netconf-redraw.png 578w, https:\/\/www.fir3net.com\/wp-content\/uploads\/2017\/10\/images_articles_netconf-redraw-300x155.png 300w\" sizes=\"(max-width: 578px) 100vw, 578px\" class=\" size-full wp-image-1144 sp-no-webp\" alt=\"netconf-redraw\" loading=\"lazy\" decoding=\"async\"  > <\/picture><\/h3>\n<p style=\"text-align: center;\"><strong>Figure 3<\/strong> &#8211;\u00a0 NETCONF protocol stack.<\/p>\n<h3 id=\"h.5lm29fegd7bs\" class=\"c24\"><span class=\"ez-toc-section\" id=\"Communication\"><\/span><span class=\"c26 c1\">Communication<\/span><span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p class=\"c12\"><span class=\"c4 c5\">NETCONF is based upon a client\/server model, as known (as per NETCONF\u2019s terminology) &#8211; <strong>Manager and Agent<\/strong>.<\/span><\/p>\n<p class=\"c12\">Within the communication flow of a NETCONF session there are 3 main parts. These are:<\/p>\n<ol>\n<li class=\"c12\"><strong><span class=\"c14\">Session Establishment<\/span><\/strong><span class=\"c4 c5\">\u00a0&#8211; Each side sends a <span class=\"codeinline\">&lt;hello&gt;<\/span>, along with its <span class=\"codeinline\">&lt;capabilities&gt;<\/span>. Announcing what operations (capabilities) it supports.<\/span><\/li>\n<li class=\"c12\"><strong><span class=\"c14\">Operation Request<\/span><\/strong><span class=\"c4 c5\">\u00a0&#8211; The client then sends its request (operation) to the server via the<span class=\"codeinline\">&lt;rpc&gt;<\/span> message. The response is then sent back to the client within <span class=\"codeinline\">&lt;rpc-reply&gt;<\/span>. <\/span><\/li>\n<li class=\"c12\"><strong><span class=\"c14\">Session Close<\/span><\/strong><strong>\u00a0<\/strong>&#8211; The session is then closed by the client via <span class=\"codeinline\">&lt;close-session&gt;<\/span>.<\/li>\n<\/ol>\n<h3 id=\"h.6ljwdilryryu\" class=\"c24\"><span class=\"ez-toc-section\" id=\"Operations\"><\/span><span class=\"c26 c1\">Operations<\/span><span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p class=\"c12\"><span class=\"c4 c5\">Actions are performed upon the network device (and its datastores) via a set of Operations.\u00a0<\/span><span class=\"c4 c5\">Each of the operations relate to the devices (client or server&#8217;s) capabilities. For example if we look at <span class=\"codeinline\">&lt;get-config&gt;<\/span> this is supported under the <span class=\"codeinline\">:base<\/span> capability.<\/span><\/p>\n<table class=\"table table-striped table-condensed\">\n<tbody>\n<tr class=\"c9\">\n<th class=\"c0\">Operation<\/th>\n<th class=\"c0\">Description<\/th>\n<\/tr>\n<tr class=\"c9\">\n<td class=\"c0\">&lt;get&gt;<\/td>\n<td class=\"c0\">Fetch running configuration and state information<\/td>\n<\/tr>\n<tr class=\"c9\">\n<td class=\"c0\">&lt;get-config&gt;<\/td>\n<td class=\"c0\">Fetch all or part of specified configuration data store<\/td>\n<\/tr>\n<tr class=\"c41\">\n<td class=\"c0\">&lt;edit-config&gt;<\/td>\n<td class=\"c0\">Load all or part of a configuration to the specified configuration data store<\/td>\n<\/tr>\n<tr class=\"c2\">\n<td class=\"c0\">&lt;copy-config&gt;<\/td>\n<td class=\"c0\">Replace the whole configuration data store with another data store<\/td>\n<\/tr>\n<tr class=\"c2\">\n<td>&lt;delete-config&gt;<\/td>\n<td>Delete a configuration data store<\/td>\n<\/tr>\n<tr class=\"c2\">\n<td>&lt;discard-changes&gt;<\/td>\n<td>Clear all changes from &lt;candidate\/&gt; and make it match the &lt;running\/&gt; configuration data store<\/td>\n<\/tr>\n<tr class=\"c2\">\n<td>&lt;create-subscription&gt;<\/td>\n<td>Create a NETCONF notification subscription<\/td>\n<\/tr>\n<tr class=\"c2\">\n<td>&lt;commit&gt;<\/td>\n<td>Copy candidate data store to running data store<\/td>\n<\/tr>\n<tr class=\"c2\">\n<td>&lt;cancel-commit&gt;<\/td>\n<td>Cancels an ongoing confirmed commit<\/td>\n<\/tr>\n<tr class=\"c2\">\n<td>&lt;lock&gt;<\/td>\n<td>Lock the entire configuration data store system so one my session can write<\/td>\n<\/tr>\n<tr class=\"c2\">\n<td>&lt;unlock&gt;<\/td>\n<td>Unlock the entire configuration data store system so any session can write<\/td>\n<\/tr>\n<tr class=\"c2\">\n<td>&lt;close-session&gt;<\/td>\n<td>Graceful termination of NETCONF session<\/td>\n<\/tr>\n<tr class=\"c2\">\n<td>&lt;kill-session&gt;<\/td>\n<td>Forced termination of NETCONF session<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<h3 id=\"h.qj45hv2vrxwt\" class=\"c24 c45\"><span class=\"ez-toc-section\" id=\"Configuration_Datastores\"><\/span>Configuration Datastores<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p class=\"c12\"><span class=\"c4 c1\">There are 4 NETCONF configuration datastores &#8211; <strong>Running, Startup, Candidate<\/strong> and <strong>URL<\/strong>.\u00a0<\/span><span class=\"c4 c1\">Actions are then performed against these datastores via the various NETCONF operations (as previously seen):<\/span><\/p>\n<ul class=\"c3 lst-kix_j0y90flomvvo-0 start\">\n<li class=\"c10\"><span class=\"c4 c1\"><strong>Running<\/strong> &#8211; The configuration datastore containing the configuration that is applied and running upon the network device.<\/span><\/li>\n<li class=\"c10\"><span class=\"c1\"><strong>Startup<\/strong> &#8211; <\/span><span class=\"c1 c23 c18\">The configuration datastore holding the configuration loaded by the device when it boots.<\/span><sup class=\"c1 c23 c18\"><a id=\"ftnt_ref7\" href=\"#ftnt7\">[7]<\/a><\/sup><\/li>\n<li class=\"c10\"><span class=\"c1\"><strong>Candidate<\/strong> &#8211; <\/span><span class=\"c1 c18 c23\">A configuration datastore that can be manipulated without impacting the device&#8217;s current configuration and that can be committed to the running configuration datastore.<\/span><sup class=\"c1\"><a id=\"ftnt_ref8\" href=\"#ftnt8\">[8]<\/a><\/sup><\/li>\n<li class=\"c10\"><span class=\"c4 c1\"><strong>URL<\/strong> &#8211; A configuration datastore thats configuration resides within a separate location, accessed via a URL.<\/span><\/li>\n<\/ul>\n<h2><span class=\"ez-toc-section\" id=\"References\"><\/span>References<span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p><a id=\"ftnt1\" href=\"#ftnt_ref1\">[1]<\/a><span class=\"c8\">\u00a0&#8220;Under New Management: Practical Attacks on SNMPv3 &#8211; Usenix.&#8221; <\/span><span class=\"c8 c20\"><a class=\"c6\" href=\"https:\/\/www.google.com\/url?q=https:\/\/www.usenix.org\/system\/files\/conference\/woot12\/woot12-final14.pdf&amp;sa=D&amp;ust=1508706139401000&amp;usg=AFQjCNFL2qhYnH0Pl28WqUk2vT1bxDIWGw\">https:\/\/www.usenix.org\/system\/files\/conference\/woot12\/woot12-final14.pdf<\/a><\/span><span class=\"c15 c5 c8\">. Accessed 17 Oct. 2017.<\/span><br \/>\n<a id=\"ftnt2\" href=\"#ftnt_ref2\">[2]<\/a><span class=\"c8\">\u00a0&#8220;Can NETCONF and YANG save from network disasters ? &#8211; TelcoCloud &#8230;.&#8221; 18 Jan. 2016, <\/span><span class=\"c20 c8\"><a class=\"c6\" href=\"https:\/\/www.google.com\/url?q=http:\/\/www.telcocloudbridge.com\/can-netconf-yang-save-network-disasters\/&amp;sa=D&amp;ust=1508706139402000&amp;usg=AFQjCNFY5hBRziocmqcbbTGWR-ZNGQbLFg\">http:\/\/www.telcocloudbridge.com\/can-netconf-yang-save-network-disasters\/<\/a><\/span><span class=\"c15 c5 c8\">. Accessed 17 Oct. 2017.<\/span><br \/>\n<a id=\"ftnt3\" href=\"#ftnt_ref3\">[3]<\/a><span class=\"c8\">\u00a0&#8220;YANG data modeling &#8211; Wikipedia.&#8221; <\/span><span class=\"c20 c8\"><a class=\"c6\" href=\"https:\/\/www.google.com\/url?q=https:\/\/en.wikipedia.org\/wiki\/YANG&amp;sa=D&amp;ust=1508706139402000&amp;usg=AFQjCNF7Z4I3E-iraJx1WSIxRnQ60Id4IA\">https:\/\/en.wikipedia.org\/wiki\/YANG<\/a><\/span><span class=\"c5 c8 c15\">. Accessed 19 Oct. 2017.<\/span><br \/>\n<a id=\"ftnt4\" href=\"#ftnt_ref4\">[4]<\/a><span class=\"c8\">\u00a0&#8220;Tail-f Systems.&#8221; <\/span><span class=\"c20 c8\"><a class=\"c6\" href=\"https:\/\/www.google.com\/url?q=http:\/\/www.tail-f.com\/&amp;sa=D&amp;ust=1508706139403000&amp;usg=AFQjCNFFhkWp7qYONy_8Op-Qmd7Ffbq_9g\">http:\/\/www.tail-f.com\/<\/a><\/span><span class=\"c15 c5 c8\">. Accessed 20 Oct. 2017.<\/span><br \/>\n<a id=\"ftnt5\" href=\"#ftnt_ref5\">[5]<\/a><span class=\"c1 c8\">\u00a0<\/span><span class=\"c1 c32\">&#8220;NETCONF: Introduction To An Emerging Networking Standard &#8230;.&#8221; 20 Jun. 2014, <\/span><span class=\"c1 c32 c33\"><a class=\"c6\" href=\"https:\/\/www.google.com\/url?q=https:\/\/www.networkcomputing.com\/networking\/netconf-introduction-emerging-networking-standard\/338840365&amp;sa=D&amp;ust=1508706139405000&amp;usg=AFQjCNGLMPxGpWdSheX0ifzCKc15e2shpg\">https:\/\/www.networkcomputing.com\/networking\/netconf-introduction-emerging-networking-standard\/338840365<\/a><\/span><span class=\"c1 c32\">. Accessed 22 Oct. 2017.<\/span><br \/>\n<a id=\"ftnt6\" href=\"#ftnt_ref6\">[6]<\/a><span class=\"c8\">\u00a0&#8220;NETCONF: Introduction To An Emerging Networking Standard &#8230;.&#8221; 20 Jun. 2014, <\/span><span class=\"c20 c8\"><a class=\"c6\" href=\"https:\/\/www.google.com\/url?q=https:\/\/www.networkcomputing.com\/networking\/netconf-introduction-emerging-networking-standard\/338840365&amp;sa=D&amp;ust=1508706139406000&amp;usg=AFQjCNERQXj3JP1V-APzEMxb0tBDXBOIpQ\">https:\/\/www.networkcomputing.com\/networking\/netconf-introduction-emerging-networking-standard\/338840365<\/a><\/span><span class=\"c15 c5 c8\">. Accessed 22 Oct. 2017.<\/span><br \/>\n<a id=\"ftnt7\" href=\"#ftnt_ref7\">[7]<\/a><span class=\"c8\">\u00a0&#8220;NETCONF Primer &#8211; NETCONFc.&#8221; <\/span><span class=\"c20 c8\"><a class=\"c6\" href=\"https:\/\/www.google.com\/url?q=http:\/\/www.seguesoft.com\/netconf-primer&amp;sa=D&amp;ust=1508706139404000&amp;usg=AFQjCNFG7qjvh2jXWkvNt2PLIsFnZ-A2Pg\">http:\/\/www.seguesoft.com\/netconf-primer<\/a><\/span><span class=\"c15 c5 c8\">. Accessed 20 Oct. 2017.<\/span><br \/>\n<a id=\"ftnt8\" href=\"#ftnt_ref8\">[8]<\/a><span class=\"c8\">\u00a0&#8220;NETCONF Primer &#8211; NETCONFc.&#8221; <\/span><span class=\"c20 c8\"><a class=\"c6\" href=\"https:\/\/www.google.com\/url?q=http:\/\/www.seguesoft.com\/netconf-primer&amp;sa=D&amp;ust=1508706139403000&amp;usg=AFQjCNHN8I-B-ESV2cf-Y9Z-dVEo82FbSQ\">http:\/\/www.seguesoft.com\/netconf-primer<\/a><\/span><span class=\"c15 c5 c8\">. Accessed 20 Oct. 2017.<\/span><\/p>\n<h2 id=\"h.aylpp76bp4yo\" class=\"c25\"><span class=\"ez-toc-section\" id=\"Further_Reading\"><\/span><span class=\"c15 c1 c16\">Further Reading<\/span><span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p><a href=\"http:\/\/jedelman.com\/home\/openconfig-data-models-and-apis\/\">http:\/\/jedelman.com\/home\/openconfig-data-models-and-apis\/<\/a><br \/>\n<a href=\"http:\/\/whatis.techtarget.com\/definition\/YANG-data-modeling-language\">http:\/\/whatis.techtarget.com\/definition\/YANG-data-modeling-language<\/a><br \/>\n<a href=\"https:\/\/www.fir3net.com\/wp-content\/uploads\/2017\/10\/www.cisco_.com_c_dam_global_cs_cz_assets_ciscoconnect_2014_assets_tech_sdn10_sp_netconf_yang_restconf_martinkramolis.pdf\">https:\/\/www.cisco.com\/c\/dam\/global\/cs_cz\/assets\/ciscoconnect\/2014\/assets\/tech_sdn10_sp_netconf_yang_restconf_martinkramolis.pdf<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"<p>TL;DR NETCONF\/YANG provides a standardized way to programmatically\u00a0update and modify the configuration of a network device. To break this down further. YANG is the modelling language that describes the configuration changes. Whereas \u00a0NETCONF is the protocol that applies the changes to the relevant datastore (i.e running, saved etc) upon the device. Introduction Let us start &#8230; <a title=\"An Introduction to NETCONF\/YANG\" class=\"read-more\" href=\"https:\/\/www.fir3net.com\/Networking\/Protocols\/an-introduction-to-netconf-yang.html\" aria-label=\"Read more about An Introduction to NETCONF\/YANG\">Read more<\/a><\/p>\n","protected":false},"author":2,"featured_media":1141,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1266],"tags":[],"yoast_head":"<!-- This site is optimized with the Yoast SEO plugin v22.5 - https:\/\/yoast.com\/wordpress\/plugins\/seo\/ -->\n<title>An Introduction to NETCONF\/YANG - Fir3net<\/title>\n<meta name=\"description\" content=\"TL;DR NETCONF\/YANG provides a standardized way to programmatically\u00a0update and modify the configuration of a network device. To break this down further.\" \/>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/www.fir3net.com\/Networking\/Protocols\/an-introduction-to-netconf-yang.html\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"An Introduction to NETCONF\/YANG - Fir3net\" \/>\n<meta property=\"og:description\" content=\"TL;DR NETCONF\/YANG provides a standardized way to programmatically\u00a0update and modify the configuration of a network device. To break this down further.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/www.fir3net.com\/Networking\/Protocols\/an-introduction-to-netconf-yang.html\" \/>\n<meta property=\"og:site_name\" content=\"Fir3net\" \/>\n<meta property=\"article:published_time\" content=\"2017-10-30T19:06:00+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2021-07-31T17:07:35+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/www.fir3net.com\/wp-content\/uploads\/2017\/10\/images_articles_netconf-stack4.png\" \/>\n\t<meta property=\"og:image:width\" content=\"548\" \/>\n\t<meta property=\"og:image:height\" content=\"420\" \/>\n\t<meta property=\"og:image:type\" content=\"image\/jpeg\" \/>\n<meta name=\"author\" content=\"Rick Donato\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"Rick Donato\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"6 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\/\/www.fir3net.com\/Networking\/Protocols\/an-introduction-to-netconf-yang.html#article\",\"isPartOf\":{\"@id\":\"https:\/\/www.fir3net.com\/Networking\/Protocols\/an-introduction-to-netconf-yang.html\"},\"author\":{\"name\":\"Rick Donato\",\"@id\":\"https:\/\/www.fir3net.com\/#\/schema\/person\/ab35009601b7687ee1c5310be6038037\"},\"headline\":\"An Introduction to NETCONF\/YANG\",\"datePublished\":\"2017-10-30T19:06:00+00:00\",\"dateModified\":\"2021-07-31T17:07:35+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\/\/www.fir3net.com\/Networking\/Protocols\/an-introduction-to-netconf-yang.html\"},\"wordCount\":1354,\"publisher\":{\"@id\":\"https:\/\/www.fir3net.com\/#organization\"},\"image\":{\"@id\":\"https:\/\/www.fir3net.com\/Networking\/Protocols\/an-introduction-to-netconf-yang.html#primaryimage\"},\"thumbnailUrl\":\"https:\/\/www.fir3net.com\/wp-content\/uploads\/2017\/10\/images_articles_netconf-stack4.png\",\"articleSection\":[\"Network Automation\"],\"inLanguage\":\"en-US\"},{\"@type\":\"WebPage\",\"@id\":\"https:\/\/www.fir3net.com\/Networking\/Protocols\/an-introduction-to-netconf-yang.html\",\"url\":\"https:\/\/www.fir3net.com\/Networking\/Protocols\/an-introduction-to-netconf-yang.html\",\"name\":\"An Introduction to NETCONF\/YANG - Fir3net\",\"isPartOf\":{\"@id\":\"https:\/\/www.fir3net.com\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\/\/www.fir3net.com\/Networking\/Protocols\/an-introduction-to-netconf-yang.html#primaryimage\"},\"image\":{\"@id\":\"https:\/\/www.fir3net.com\/Networking\/Protocols\/an-introduction-to-netconf-yang.html#primaryimage\"},\"thumbnailUrl\":\"https:\/\/www.fir3net.com\/wp-content\/uploads\/2017\/10\/images_articles_netconf-stack4.png\",\"datePublished\":\"2017-10-30T19:06:00+00:00\",\"dateModified\":\"2021-07-31T17:07:35+00:00\",\"description\":\"TL;DR NETCONF\/YANG provides a standardized way to programmatically\u00a0update and modify the configuration of a network device. To break this down further.\",\"breadcrumb\":{\"@id\":\"https:\/\/www.fir3net.com\/Networking\/Protocols\/an-introduction-to-netconf-yang.html#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/www.fir3net.com\/Networking\/Protocols\/an-introduction-to-netconf-yang.html\"]}]},{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\/\/www.fir3net.com\/Networking\/Protocols\/an-introduction-to-netconf-yang.html#primaryimage\",\"url\":\"https:\/\/www.fir3net.com\/wp-content\/uploads\/2017\/10\/images_articles_netconf-stack4.png\",\"contentUrl\":\"https:\/\/www.fir3net.com\/wp-content\/uploads\/2017\/10\/images_articles_netconf-stack4.png\",\"width\":548,\"height\":420},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/www.fir3net.com\/Networking\/Protocols\/an-introduction-to-netconf-yang.html#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\/\/www.fir3net.com\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Networking\",\"item\":\"https:\/\/www.fir3net.com\/networking\"},{\"@type\":\"ListItem\",\"position\":3,\"name\":\"Network Automation\",\"item\":\"https:\/\/www.fir3net.com\/networking\/automation\"},{\"@type\":\"ListItem\",\"position\":4,\"name\":\"An Introduction to NETCONF\/YANG\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/www.fir3net.com\/#website\",\"url\":\"https:\/\/www.fir3net.com\/\",\"name\":\"Fir3net\",\"description\":\"Keeping you in the know\",\"publisher\":{\"@id\":\"https:\/\/www.fir3net.com\/#organization\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/www.fir3net.com\/?s={search_term_string}\"},\"query-input\":\"required name=search_term_string\"}],\"inLanguage\":\"en-US\"},{\"@type\":\"Organization\",\"@id\":\"https:\/\/www.fir3net.com\/#organization\",\"name\":\"Fir3net\",\"url\":\"https:\/\/www.fir3net.com\/\",\"logo\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\/\/www.fir3net.com\/#\/schema\/logo\/image\/\",\"url\":\"https:\/\/www.fir3net.com\/wp-content\/uploads\/Fir3net-Background-Logo-compressed.png\",\"contentUrl\":\"https:\/\/www.fir3net.com\/wp-content\/uploads\/Fir3net-Background-Logo-compressed.png\",\"width\":390,\"height\":88,\"caption\":\"Fir3net\"},\"image\":{\"@id\":\"https:\/\/www.fir3net.com\/#\/schema\/logo\/image\/\"}},{\"@type\":\"Person\",\"@id\":\"https:\/\/www.fir3net.com\/#\/schema\/person\/ab35009601b7687ee1c5310be6038037\",\"name\":\"Rick Donato\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\/\/www.fir3net.com\/#\/schema\/person\/image\/\",\"url\":\"https:\/\/secure.gravatar.com\/avatar\/d75d69a54c0ca3b32c24c3a9703b623c?s=96&d=mm&r=g\",\"contentUrl\":\"https:\/\/secure.gravatar.com\/avatar\/d75d69a54c0ca3b32c24c3a9703b623c?s=96&d=mm&r=g\",\"caption\":\"Rick Donato\"},\"description\":\"Rick Donato is a Network Automation Architect\/Evangelist and the founder of Packet Coders.\"}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"An Introduction to NETCONF\/YANG - Fir3net","description":"TL;DR NETCONF\/YANG provides a standardized way to programmatically\u00a0update and modify the configuration of a network device. To break this down further.","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/www.fir3net.com\/Networking\/Protocols\/an-introduction-to-netconf-yang.html","og_locale":"en_US","og_type":"article","og_title":"An Introduction to NETCONF\/YANG - Fir3net","og_description":"TL;DR NETCONF\/YANG provides a standardized way to programmatically\u00a0update and modify the configuration of a network device. To break this down further.","og_url":"https:\/\/www.fir3net.com\/Networking\/Protocols\/an-introduction-to-netconf-yang.html","og_site_name":"Fir3net","article_published_time":"2017-10-30T19:06:00+00:00","article_modified_time":"2021-07-31T17:07:35+00:00","og_image":[{"width":548,"height":420,"url":"https:\/\/www.fir3net.com\/wp-content\/uploads\/2017\/10\/images_articles_netconf-stack4.png","type":"image\/jpeg"}],"author":"Rick Donato","twitter_card":"summary_large_image","twitter_misc":{"Written by":"Rick Donato","Est. reading time":"6 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/www.fir3net.com\/Networking\/Protocols\/an-introduction-to-netconf-yang.html#article","isPartOf":{"@id":"https:\/\/www.fir3net.com\/Networking\/Protocols\/an-introduction-to-netconf-yang.html"},"author":{"name":"Rick Donato","@id":"https:\/\/www.fir3net.com\/#\/schema\/person\/ab35009601b7687ee1c5310be6038037"},"headline":"An Introduction to NETCONF\/YANG","datePublished":"2017-10-30T19:06:00+00:00","dateModified":"2021-07-31T17:07:35+00:00","mainEntityOfPage":{"@id":"https:\/\/www.fir3net.com\/Networking\/Protocols\/an-introduction-to-netconf-yang.html"},"wordCount":1354,"publisher":{"@id":"https:\/\/www.fir3net.com\/#organization"},"image":{"@id":"https:\/\/www.fir3net.com\/Networking\/Protocols\/an-introduction-to-netconf-yang.html#primaryimage"},"thumbnailUrl":"https:\/\/www.fir3net.com\/wp-content\/uploads\/2017\/10\/images_articles_netconf-stack4.png","articleSection":["Network Automation"],"inLanguage":"en-US"},{"@type":"WebPage","@id":"https:\/\/www.fir3net.com\/Networking\/Protocols\/an-introduction-to-netconf-yang.html","url":"https:\/\/www.fir3net.com\/Networking\/Protocols\/an-introduction-to-netconf-yang.html","name":"An Introduction to NETCONF\/YANG - Fir3net","isPartOf":{"@id":"https:\/\/www.fir3net.com\/#website"},"primaryImageOfPage":{"@id":"https:\/\/www.fir3net.com\/Networking\/Protocols\/an-introduction-to-netconf-yang.html#primaryimage"},"image":{"@id":"https:\/\/www.fir3net.com\/Networking\/Protocols\/an-introduction-to-netconf-yang.html#primaryimage"},"thumbnailUrl":"https:\/\/www.fir3net.com\/wp-content\/uploads\/2017\/10\/images_articles_netconf-stack4.png","datePublished":"2017-10-30T19:06:00+00:00","dateModified":"2021-07-31T17:07:35+00:00","description":"TL;DR NETCONF\/YANG provides a standardized way to programmatically\u00a0update and modify the configuration of a network device. To break this down further.","breadcrumb":{"@id":"https:\/\/www.fir3net.com\/Networking\/Protocols\/an-introduction-to-netconf-yang.html#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/www.fir3net.com\/Networking\/Protocols\/an-introduction-to-netconf-yang.html"]}]},{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/www.fir3net.com\/Networking\/Protocols\/an-introduction-to-netconf-yang.html#primaryimage","url":"https:\/\/www.fir3net.com\/wp-content\/uploads\/2017\/10\/images_articles_netconf-stack4.png","contentUrl":"https:\/\/www.fir3net.com\/wp-content\/uploads\/2017\/10\/images_articles_netconf-stack4.png","width":548,"height":420},{"@type":"BreadcrumbList","@id":"https:\/\/www.fir3net.com\/Networking\/Protocols\/an-introduction-to-netconf-yang.html#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/www.fir3net.com\/"},{"@type":"ListItem","position":2,"name":"Networking","item":"https:\/\/www.fir3net.com\/networking"},{"@type":"ListItem","position":3,"name":"Network Automation","item":"https:\/\/www.fir3net.com\/networking\/automation"},{"@type":"ListItem","position":4,"name":"An Introduction to NETCONF\/YANG"}]},{"@type":"WebSite","@id":"https:\/\/www.fir3net.com\/#website","url":"https:\/\/www.fir3net.com\/","name":"Fir3net","description":"Keeping you in the know","publisher":{"@id":"https:\/\/www.fir3net.com\/#organization"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/www.fir3net.com\/?s={search_term_string}"},"query-input":"required name=search_term_string"}],"inLanguage":"en-US"},{"@type":"Organization","@id":"https:\/\/www.fir3net.com\/#organization","name":"Fir3net","url":"https:\/\/www.fir3net.com\/","logo":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/www.fir3net.com\/#\/schema\/logo\/image\/","url":"https:\/\/www.fir3net.com\/wp-content\/uploads\/Fir3net-Background-Logo-compressed.png","contentUrl":"https:\/\/www.fir3net.com\/wp-content\/uploads\/Fir3net-Background-Logo-compressed.png","width":390,"height":88,"caption":"Fir3net"},"image":{"@id":"https:\/\/www.fir3net.com\/#\/schema\/logo\/image\/"}},{"@type":"Person","@id":"https:\/\/www.fir3net.com\/#\/schema\/person\/ab35009601b7687ee1c5310be6038037","name":"Rick Donato","image":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/www.fir3net.com\/#\/schema\/person\/image\/","url":"https:\/\/secure.gravatar.com\/avatar\/d75d69a54c0ca3b32c24c3a9703b623c?s=96&d=mm&r=g","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/d75d69a54c0ca3b32c24c3a9703b623c?s=96&d=mm&r=g","caption":"Rick Donato"},"description":"Rick Donato is a Network Automation Architect\/Evangelist and the founder of Packet Coders."}]}},"_links":{"self":[{"href":"https:\/\/www.fir3net.com\/wp-json\/wp\/v2\/posts\/1146"}],"collection":[{"href":"https:\/\/www.fir3net.com\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.fir3net.com\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.fir3net.com\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/www.fir3net.com\/wp-json\/wp\/v2\/comments?post=1146"}],"version-history":[{"count":0,"href":"https:\/\/www.fir3net.com\/wp-json\/wp\/v2\/posts\/1146\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.fir3net.com\/wp-json\/wp\/v2\/media\/1141"}],"wp:attachment":[{"href":"https:\/\/www.fir3net.com\/wp-json\/wp\/v2\/media?parent=1146"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.fir3net.com\/wp-json\/wp\/v2\/categories?post=1146"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.fir3net.com\/wp-json\/wp\/v2\/tags?post=1146"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}