Goals for netconf - moving towards the charter description

["Faye Ly" <faye@pedestalnetworks.com>]

Andy,

Here are some suggestions to the slides titled "Netconf BOF 56th IETF"
in particular to the 'Goals' bullet item on slide 3.  This is also
proposing a set of charter description for 'netconf' WG. 

You currently have:

>Goals:
>Achieve standards-based network management
>Phase out proprietary screen-scraping scripts
>Manage networks, not just network devices

These goals have proven to be controversial and a bit too ambitious for
this working group to tackle.  Suggest using the following:
========================================================================
===

Develop a standards-based network management protocol specifically
addressing the need of configuration management (CM) where CM is
described as:

Enable file based and transactional based configuration and
configuration information retrieval to one or more network devices to
meet the following needs:

1. Enable or disable user traffic on one or a set of heterogeneous
network devices where this user traffic traverses.  Note that management
channel is categorized as a special type of user traffic which has the
same set of requirement with the user's traffic.
2. Enable or disable network devices and physical/logical interfaces for
inventory management.
3. Enable or disable all levels of diagnostic and fault triggering
function to ensure network device, user data path as well as physical
port and/or path for fault management.
4. Enable or disable operator and operator access (Role based
configuration).
5. Enable or disable data integrity and secrecy for all user traffic as
well as management traffic on a per user traffic, per device or per
network basis.
6. enable/disable file management for upgrade, save, backup, restore and
execute for full or partial configuration set on a single or multiple
network devices.

This protocol is also required to address the need of 'transaction'
based configuration model for one or a set of heterogeneous network
devices where the typical property of the 'transaction' should be
supported.  (Such as but not limited to configure, commit, and
rollback).  

This protocol is designed to solve the lack of consistency for
configuring network device(s) and network device to network device
configuration discrepancy problem.  Specifically it is designed to
address the pain of using CLI based scripting tools to configure one
network device at a time and hence no transactional support for applying
configuration to all network devices that are involved.

This protocol is not designed to attach to a certain data model but
focused on addressing all the configuration management needs depicted
above. 

========================================================================
=== 

-faye
  

--
to unsubscribe send a message to xmlconf-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://ops.ietf.org/lists/xmlconf/>