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

RE: netconf WG charter proposal



Weijing,

But who is at the other end of the channel?  Without the NMS app, any
management protocol/channel/data is a waste of time.

-faye

-----Original Message-----
From: Chen, Weijing [mailto:wchen@tri.sbc.com] 
Sent: Tuesday, April 15, 2003 9:08 AM
To: Faye Ly
Cc: xmlconf@ops.ietf.org
Subject: RE: netconf WG charter proposal

What does the channel have to do with data model?  A channel is a
channel.
You can have the following for the configuration:
<rpc>
	<edit-config>
	plain text
	</edit-config>
</rpc>

Why can't you have the following for the notification:
<rpc-notif>
	plain alarm text
</rpc-notif>


NMS do what they got to do with whatever they have.  It is not worse
than we
have now.



--
Weijing Chen
SBC Technology Resources
9505 Arboretum Blvd.
Austin, TX 78759
512 372 5710
wchen@tri.sbc.com



-----Original Message-----
From: Faye Ly [mailto:faye@pedestalnetworks.com] 
Sent: Tuesday, April 15, 2003 11:00 AM
To: Andy Bierman
Cc: David T. Perkins; Chen, Weijing; xmlconf@ops.ietf.org
Subject: RE: netconf WG charter proposal

Andy,

Certainly and I agree that is a good approach to get the most needed
stuff done first.  I do argue against the monitoring/notification
channel being done with this group as I don't think it can be achieved
without data modeling.  Take the existing 'trend analysis' tools for
example, it has to do inventory first to discover the interface that is
worth trending.  Different vendors can name their interfaces quite
differently and this could be a nightmare to try to figure out if one
interface from one box is actually symmetric to another interface from
another box. (They are physically or logically connected and thus need
to be trend and compared accordingly).

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