I agree whole-heartedly with Randy (the other one). Protocols move bits, they don't describe information. Information structure in a protocol is either ad-hoc, or it comes from an underlying information model.
regards,
John
John Strassner
Chief Strategy Officer
Intelliden Corporation
90 South Cascade Avenue
Colorado Springs, CO 80903 USA
phone: +1.719.785.0648
FAX: +1.719.785.0644
email: john.strassner@intelliden.com
-----Original Message-----
From: Randy Presuhn [mailto:randy_presuhn@mindspring.com]
Sent: Friday, April 04, 2003 12:42 AM
To: xmlconf@ops.ietf.org
Subject: Re: netconf WG charter proposal
Hi -
> From: "Andy Bierman" <abierman@cisco.com>
> To: "Randy Bush" <randy@psg.com>
> Cc: <xmlconf@ops.ietf.org>
> Sent: Thursday, April 03, 2003 11:04 PM
> Subject: Re: netconf WG charter proposal
...
> >> The Netconf Working Group is chartered to produce a protocol
> >> suitable for network configuration, with the following
> >> characteristics:
> >>
> >> - Provides a clear separation of configuration data
> >> from non-configuration data
> >
> >is this necessary to the task? clearly universally achievable?
>
> It was listed as an operator requirement at the NM workshop. It could
> be easy to achieve. It was never realized with SNMP.
...
As a property of the protocol per se? It might be better to consider it a property of the information model that should be represented in the data model so that configuration management applications can focus on the right bits.
Randy (the other one)
--
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/>