WG Action: Rechartered Network Configuration (netconf)

The IESG <iesg-secretary@ietf.org> Fri, 21 February 2014 17:26 UTC

Return-Path: <iesg-secretary@ietf.org>
X-Original-To: ietf-announce@ietfa.amsl.com
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com []) by ietfa.amsl.com (Postfix) with ESMTP id 4B5A31A0217; Fri, 21 Feb 2014 09:26:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id lKNy3pAJ5gQt; Fri, 21 Feb 2014 09:26:07 -0800 (PST)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 83D031A0487; Fri, 21 Feb 2014 09:26:06 -0800 (PST)
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Subject: WG Action: Rechartered Network Configuration (netconf)
X-Test-IDTracker: no
X-IETF-IDTracker: 5.0.1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20140221172606.1843.68000.idtracker@ietfa.amsl.com>
Date: Fri, 21 Feb 2014 09:26:06 -0800
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf-announce/QgWQCva_sa4XpzpsekpkuHx2hpI
Cc: netconf WG <netconf@ietf.org>
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.15
Reply-To: ietf@ietf.org
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf-announce/>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 21 Feb 2014 17:26:10 -0000

The Network Configuration (netconf) working group 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

  Bert Wijnen <bertietf@bwijnen.net>
  Mehmet Ersue <mehmet.ersue@nsn.com>

Assigned Area Director:
  Benoit Claise <bclaise@cisco.com>

Mailing list
  Address: netconf@ietf.org
  To Subscribe: https://www.ietf.org/mailman/listinfo/netconf
  Archive: http://www.ietf.org/mail-archive/web/netconf/


Configuration of networks of devices has become a critical requirement
for operators in today's highly interconnected networks. Large and small
operators alike have developed their own mechanisms or have used vendor
specific mechanisms to transfer configuration data to and from a device
and to examine device state information which may impact the
configuration. Each of these mechanisms may be different in various
aspects, such as session establishment, user authentication,
configuration data exchange, and error responses.
The NETCONF protocol (RFC 6241) provides mechanisms to install,
manipulate, and delete the configuration of network devices. NETCONF is
based on the secure transport (SSH is mandatory to implement while TLS is
an optional transport) and uses an XML-based data representation. The
NETCONF protocol is data modeling language independent, but YANG (RFC
6020) is the recommended NETCONF modeling language, which introduces
advanced language features for configuration management.
Based on the implementation, deployment experience and interoperability
testing, the WG aims to produce a NETCONF status report in a later stage.
The result may be clarifications for RFC6241 and RFC6242 and addressing
any reported errata.
In the current phase of NETCONF's incremental development the workgroup
will focus on following items:
  1. Develop the call home mechanism for the mandatory SSH binding
(Reverse SSH) providing a server-initiated session establishment.

  2. Develop a zero touch configuration document (a technique to
establish a secure network management relationship between a newly
delivered network device configured with just its factory default
settings, and the Network Management System), specific to the NETCONF use
  3. Advance NETCONF over TLS to be in-line with NETCONF 1.1 (i.e.,
update RFC 5539) and add the call home mechanism to provide a
server-initiated session establishment.
  4. Combine the server configuration data models from Reverse SSH and
RFC5539bis drafts in a separate call home YANG module.
  5. Develop RESTCONF, a protocol based on NETCONF in terms of
capabilities, but over HTTP and with some REST characteristics, for
accessing YANG data using the datastores defined in NETCONF. An "ordered
edit list" approach is needed (the YANG patch) to provide client
developers with a simpler edit request format that can be more efficient
and also allow more precise client control of the transaction procedure
than existing mechanisms. The YANG patch operation, based on the  HTTP
PATCH method, will be prepared in a separate draft. RESTCONF should not
deviate from the NETCONF capabilities unless proper justification is
provided and documented. The RESTCONF work will consider requirements
suggested by the other working groups (for example I2RS).

  Feb 2014 - Submit initial WG draft for call home YANG module as WG item
  Feb 2014 - Submit initial WG draft for zero touch configuration as WG
  Feb 2014 - Submit initial WG drafts for RESTCONF and patch operation as
WG items
  Apr 2014 - WGLC for Reverse SSH
  Apr 2014 - WGLC for NETCONF server configuration data model
  Apr 2014 - WGLC for zero touch configuration
  Apr 2014 - WGLC for call home YANG module
  Apr 2014 - WGLC for RFC5539bis
  May 2014 - Submit call home YANG module to AD/IESG for consideration as
Proposed Standard
  May 2014 - Submit zero touch configuration to AD/IESG for consideration
as Proposed Standard
  May 2014 - Submit RFC5539bis to AD/IESG for consideration as Proposed
  May 2014 - Submit Reverse SSH to AD/IESG for consideration as Proposed
  Jun 2014 - WGLC for RESTCONF and patch operation drafts
  Aug 2014 - Submit RESTCONF to AD/IESG for consideration as Proposed