* WGs marked with an * asterisk has had at least one new draft made available during the last 5 days

Netconf Status Pages

Network Configuration (Active WG)
Ops Area: Ignas Bagdonas, Warren Kumari | 2003-Apr-30 —  

2018-07-09 charter

Network Configuration (netconf)


 Current Status: Active

     Kent Watsen <kwatsen@juniper.net>
     Mahesh Jethanandani <mjethanandani@gmail.com>

 Operations and Management Area Directors:
     Ignas Bagdonas <ibagdona@gmail.com>
     Warren Kumari <warren@kumari.net>

 Operations and Management Area Advisor:
     Ignas Bagdonas <ibagdona@gmail.com>

 Mailing Lists:
     General Discussion: netconf@ietf.org
     To Subscribe:       https://www.ietf.org/mailman/listinfo/netconf
     Archive:            https://mailarchive.ietf.org/arch/browse/netconf/

Description of Working Group:

  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

Goals and Milestones:
  Done     - WGLC for NMDA NETCONF
  Done     - WGLC for NMDA RESTCONF
  Done     - WGLC for YANG Library bis (as Standards Track)
  Done     - WGLC for Zero-touch Configuration Mechanism
  Sep 2018 - WGLC for advanced Notification/Subscription Specifications
  Sep 2018 - WGLC for YANG Push
  Sep 2018 - WGLC for RESTCONF and HTTP Transport for Event Notifications
  Sep 2018 - WGLC for NETCONF Support for Event Notifications
  Sep 2018 - WGLC for YANG Notification Headers and Bundles
  Dec 2018 - WGLC for System-level Keystore Mechanism
  Dec 2018 - WGLC for Server and Client Configuration Models for NETCONF and RESTCONF
  Dec 2018 - WGLC for Client and Server Configuration Models for SSH and TLS
  Dec 2018 - Submit draft-ietf-netconf-udp-pub-channel to IESG for publication (as Standards Track)

All charter page changes, including changes to draft-list, rfc-list and milestones:

Generated from PyHt script /wg/netconf/charters.pyht Latest update: 24 Oct 2012 16:51 GMT -