Network Configuration
charter-ietf-netconf-20

• Status
• IESG review
• IESG writeups
• Email expansions
• History

• Versions
• 13
• 13-00
• 13-01
• 13-02
• 13-03
• 13-04
• 14
• 14-00
• 14-01
• 14-02
• 14-03
• 15
• 15-00
• 15-01
• 15-02
• 15-03
• 15-04
• 15-05
• 15-06
• 15-07
• 15-08
• 15-09
• 15-10
• 15-11
• 15-12
• 15-13
• 15-14
• 15-15
• 15-16
• 15-17
• 15-18
• 15-19
• 15-20
• 15-21
• 16
• 16-00
• 17
• 17-00
• 17-01
• 17-02
• 17-03
• 17-04
• 17-05
• 18
• 18-00
• 18-01
• 18-02
• 18-03
• 18-04
• 18-05
• 18-06
• 18-07
• 18-08
• 18-09
• 18-10
• 18-11
• 18-12
• 18-13
• 18-14
• 18-15
• 18-16
• 18-17
• 18-18
• 18-19
• 18-20
• 19
• 19-00
• 19-01
• 19-02
• 19-03
• 19-04
• 19-05
• 20

Charter
charter-ietf-netconf-20

The NETCONF Working Group, previously named after the NETCONF protocol,
now renamed as the NETwork CONFiguration Working Group, is responsible for the
development and maintenance of protocols such as NETCONF and RESTCONF for YANG
data model-driven management (for the purposes of, for example, configuration,
monitoring, telemetry, and zero-touch), their transports and encodings,
defining data models necessary to support the protocols, and defining
mechanisms supporting the operational deployment of systems using the protocols.

The NETCONF protocol is data modeling language independent, but YANG (RFC 7950)
is the recommended NETCONF data modeling language, which introduces advanced
language features for configuration management.

The NETCONF WG is currently responsible for:

   a) The network management protocol NETCONF (RFC 6241). This effort entails
   periodically updating the NETCONF related specifications to address new
   requirements as they arise.

   b) The network management protocol RESTCONF (RFC 8040). This effort entails
   periodically updating the RESTCONF related specifications to address new
   requirements as they arise.

   c) The transports and encodings used by the data model-driven protocols.

   d) The data models and mechanisms related to network management protocols.
   Specifically, data models enabling the configuration and/or monitoring of
   the protocols themselves. Other examples include data models for configuring
   access controls or discovering server metadata.

   e) The data models for subscriptions to data, and protocol bindings for
   pushing subscribed data to clients, for the purpose of monitoring and
   telemetry.

   f) The mechanisms enabling devices zero-touch provisioning and the related
   call home functions.

   The NETCONF working group consults with the NETMOD working group to
   ensure that new requirements are understood and can be met by the
   YANG data modeling language (RFC 7950) developed within that working
   group.