RE: Goals for netconf - moving towards the charter description

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

Dave,

Ah thanks for bringing me back to focus.  So does this mean we support
moving of the configuration data only and NOT configuration file?
Especially the type of configuration file that used for restart or
backup/restore/upgrade?  I thought netconf's proposal already have this
included so naturally I think they are part of the scope?  I might be
wrong but please clarify.

-faye

-----Original Message-----
From: David T. Perkins [mailto:dperkins@dsperkins.com] 
Sent: Monday, March 24, 2003 11:29 AM
To: xmlconf@ops.ietf.org
Subject: Re: Goals for netconf - moving towards the charter description

HI,

In listening to the reactions to the NETCONF BOF, it seems like
many people are skipping ahead instead of taking time to appreciate
the first goal. A short description of it is the following from
Ran...
"move vendor-proprietary blobs of configuration data around using
a common convention for transmission over the wire",

This seems too simple, to be important, but it has been a stumbling 
block and a source of extra cost in managing devices. The NETCONF
proposal starts with it and lays down the foundation for a new
standard way of managing network devices.

Regards,
/david t. perkins


--
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/>

--
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/>