[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: netconf WG charter proposal



Well, not the direction for the future.  But it is here and now, CLI/syslog
trumps everything else.  XMLCONF is attempting to structure the first task
(CLI), and with adequate data model in next phase, we can structure the next
task (trap/syslog). 




-----Original Message-----
From: David T. Perkins [mailto:dperkins@dsperkins.com] 
Sent: Monday, April 14, 2003 3:03 PM
To: Chen, Weijing; xmlconf@ops.ietf.org
Subject: RE: netconf WG charter proposal

HI,

Syslog... Let's see, the payload of syslog messages is unstructured
text, and there is no standard for them. And there is no standard
for documenting the payload. Or did I miss this. (If so, please
send me a URL or two). So you are saying that completely unstructured
and undocumented text is the direction for the future?

At 02:38 PM 4/14/2003 -0500, Chen, Weijing wrote:
>Why do the mapping at all?  Why can we ditch the SNMP altogether,
>configuration through XML, trap through syslog over XML, or structured
>native XML traps over XML.  There is no much detailed trap information from
>SNMP at the beginning.  All we got from most of equipments are linkUp/Down,
>etc.  Most of equipments have more detailed information from syslog rather
>than SNMP trap.

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