# NETCONF version

**URL:** <https://dmap-community.ductus.global/t/netconf-version/842>\
**Category:** NETCONF\
**Created:** [November 16, 2016, 1:22pm UTC](https://dmap-community.ductus.global/t/netconf-version/842 "2016-11-16T13:22:22Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![InbalAmram](https://avatars.discourse-cdn.com/v4/letter/i/0ea827/32.png) [@InbalAmram](https://dmap-community.ductus.global/u/InbalAmram)\
**Post date:** [November 16, 2016, 1:22pm UTC](https://dmap-community.ductus.global/t/netconf-version/842/1 "2016-11-16T13:22:23Z")

</div>

Hi  
We have the ConfdBasic package.  
which NETCONF version we are using: NETCONF 1.0 or NETCONF 1.1?  
Where can we see this information ? How we modify this value ?

thanks,  
Inbal

---

<div class="post-metadata">

**Author:** ![jjohansson](https://avatars.discourse-cdn.com/v4/letter/j/b782af/32.png) [@jjohansson](https://dmap-community.ductus.global/u/jjohansson)\
**Post date:** [November 17, 2016, 6:09pm UTC](https://dmap-community.ductus.global/t/netconf-version/842/2 "2016-11-17T18:09:57Z")

</div>

Hi Inbal,

The level of NETCONF support in ConfD in general is detailed in the list of supported RFCs in the beginning of chapter 15 in the User Guide. There you can see both RFC 4741 (NETCONF 1.0) and RFC 6241 (NETCONF 1.1).

For a particular ConfD instance you can look at the NETCONF hello message:

```auto
<?xml version="1.0" encoding="UTF-8"?>
<hello xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
  <capabilities>
    <capability>urn:ietf:params:netconf:base:1.0</capability>
    <capability>urn:ietf:params:netconf:base:1.1</capability>
    <capability>urn:ietf:params:netconf:capability:writable-running:1.0</capability>
    <capability>urn:ietf:params:netconf:capability:xpath:1.0</capability>
    <capability>urn:ietf:params:netconf:capability:validate:1.0</capability>
    <capability>urn:ietf:params:netconf:capability:validate:1.1</capability>
    <capability>urn:ietf:params:netconf:capability:rollback-on-error:1.0</capability>
    <capability>http://tail-f.com/ns/netconf/actions/1.0</capability>
    <capability>http://tail-f.com/ns/netconf/extensions</capability>
    <capability>urn:ietf:params:netconf:capability:with-defaults:1.0?basic-mode=explicit&amp;also-supported=report-all-tagged</capability>
    <capability>urn:ietf:params:xml:ns:yang:ietf-netconf-with-defaults?revision=2011-06-01&amp;module=ietf-netconf-with-defaults</capability>
    <capability>urn:ietf:params:netconf:capability:yang-library:1.0?revision=2016-06-21&amp;module-set-id=ed3fe55031c3873653a27108afb48ab6</capability>
    <capability>http://tail-f.com/ns/aaa/1.1?module=tailf-aaa&amp;revision=2015-06-16</capability>
    <capability>http://tail-f.com/ns/example/dhcpd?module=dhcpd</capability>
    <capability>http://tail-f.com/ns/kicker?module=tailf-kicker&amp;revision=2016-05-03</capability>
    <capability>http://tail-f.com/ns/webui?module=tailf-webui&amp;revision=2013-03-07</capability>
    <capability>http://tail-f.com/yang/acm?module=tailf-acm&amp;revision=2013-03-07</capability>
    <capability>http://tail-f.com/yang/common-monitoring?module=tailf-common-monitoring&amp;revision=2013-06-14</capability>
    <capability>http://tail-f.com/yang/confd-monitoring?module=tailf-confd-monitoring&amp;revision=2013-06-14</capability>
    <capability>http://tail-f.com/yang/netconf-monitoring?module=tailf-netconf-monitoring&amp;revision=2014-11-13</capability>
    <capability>urn:ietf:params:xml:ns:yang:iana-crypt-hash?module=iana-crypt-hash&amp;revision=2014-04-04&amp;features=crypt-hash-sha-512,crypt-hash-sha-256,crypt-hash-md5</capability>
    <capability>urn:ietf:params:xml:ns:yang:ietf-inet-types?module=ietf-inet-types&amp;revision=2013-07-15</capability>
    <capability>urn:ietf:params:xml:ns:yang:ietf-netconf-acm?module=ietf-netconf-acm&amp;revision=2012-02-22</capability>
    <capability>urn:ietf:params:xml:ns:yang:ietf-netconf-monitoring?module=ietf-netconf-monitoring&amp;revision=2010-10-04</capability>
    <capability>urn:ietf:params:xml:ns:yang:ietf-netconf-notifications?module=ietf-netconf-notifications&amp;revision=2012-02-06</capability>
    <capability>urn:ietf:params:xml:ns:yang:ietf-yang-library?module=ietf-yang-library&amp;revision=2016-06-21</capability>
    <capability>urn:ietf:params:xml:ns:yang:ietf-yang-types?module=ietf-yang-types&amp;revision=2013-07-15</capability>
  </capabilities>
  <session-id>12</session-id>
</hello>

```

The two first lines shows that the ConfD instance support both NETCONF 1.0 and NETCONF 1.1.

The `/confdConfig/netconf/versions` tag in confd.conf can be used to specify which NETCONF versions ConfD will understand and advertise. You can read more about this in the confd.conf(5) man-page.