From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Cc: netconf@ietf.org
Reply-To: iesg@ietf.org
Subject: WG Review: Network Configuration (netconf)
The Network Configuration (netconf) WG in the Operations and Management Area
of the IETF is undergoing rechartering. The IESG has not made any
determination yet. The following draft charter was submitted, and is provided
for informational purposes only. Please send your comments to the IESG
mailing list (iesg@ietf.org) by 2026-06-02.
Network Configuration (netconf)
-----------------------------------------------------------------------
Current status: Active WG
Chairs:
Kent Watsen <kent+ietf@watsen.net>
Per Andersson <per.ietf@ionio.se>
Assigned Area Director:
Mahesh Jethanandani <mjethanandani@gmail.com>
Operations and Management Area Directors:
Mahesh Jethanandani <mjethanandani@gmail.com>
Mohamed Boucadair <mohamed.boucadair@orange.com>
Mailing list:
Address: netconf@ietf.org
To subscribe: https://www.ietf.org/mailman/listinfo/netconf
Archive: https://mailarchive.ietf.org/arch/browse/netconf/
Group page: https://datatracker.ietf.org/group/netconf/
Charter: https://datatracker.ietf.org/doc/charter-ietf-netconf/
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 working group should maintain parity between the NETCONF and
RESTCONF protocols.
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.
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.
Milestones:
WG action announcement
WG Action Announcement
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Cc: The IESG <iesg@ietf.org>,
netconf-chairs@ietf.org,
netconf@ietf.org
Subject: WG Action: Rechartered Network Configuration (netconf)
The Network Configuration (netconf) WG in the Operations and Management Area
of the IETF has been rechartered. For additional information, please contact
the Area Directors or the WG Chairs.
Network Configuration (netconf)
-----------------------------------------------------------------------
Current status: Active WG
Chairs:
Kent Watsen <kent+ietf@watsen.net>
Per Andersson <per.ietf@ionio.se>
Assigned Area Director:
Mahesh Jethanandani <mjethanandani@gmail.com>
Operations and Management Area Directors:
Mahesh Jethanandani <mjethanandani@gmail.com>
Mohamed Boucadair <mohamed.boucadair@orange.com>
Mailing list:
Address: netconf@ietf.org
To subscribe: https://www.ietf.org/mailman/listinfo/netconf
Archive: https://mailarchive.ietf.org/arch/browse/netconf/
Group page: https://datatracker.ietf.org/group/netconf/
Charter: https://datatracker.ietf.org/doc/charter-ietf-netconf/
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 working group should maintain parity between the NETCONF and
RESTCONF protocols.
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.
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.
Milestones:
Ballot announcement
Ballot Announcement
Technical Summary
Relevant content can frequently be found in the abstract
and/or introduction of the document. If not, this may be
an indication that there are deficiencies in the abstract
or introduction.
Working Group Summary
Was there anything in the WG process that is worth noting?
For example, was there controversy about particular points
or were there decisions where the consensus was
particularly rough?
Document Quality
Are there existing implementations of the protocol? Have a
significant number of vendors indicated their plan to
implement the specification? Are there any reviewers that
merit special mention as having done a thorough review,
e.g., one that resulted in important changes or a
conclusion that the document had no substantive issues? If
there was a MIB Doctor, Media Type, or other Expert Review,
what was its course (briefly)? In the case of a Media Type
Review, on what date was the request posted?
Personnel
Who is the Document Shepherd for this document? Who is the
Responsible Area Director? If the document requires IANA
experts(s), insert 'The IANA Expert(s) for the registries
in this document are <TO BE ADDED BY THE AD>.'
RFC Editor Note
(Insert RFC Editor Note here or remove section)
IRTF Note
(Insert IRTF Note here or remove section)
IESG Note
(Insert IESG Note here or remove section)
IANA Note
(Insert IANA Note here or remove section)