RE: Netconf Event Message as Working Group Document

["Hector Trevino \(htrevino\)" <htrevino@cisco.com>]

See in-line
Hector

 

-----Original Message-----
From: Andy Bierman [mailto:ietf@andybierman.com] 
Sent: Tuesday, November 08, 2005 12:11 PM
To: Hector Trevino (htrevino)
Cc: Wijnen, Bert (Bert); j.schoenwaelder@iu-bremen.de; Sharon Chisholm;
netconf@ops.ietf.org
Subject: Re: Netconf Event Message as Working Group Document

Hector Trevino (htrevino) wrote:

>Yes, you may assume that.
>
Is this syslog, SNMP notification, or something new?

HT: You could say that this is a combination of syslog and something
new. syslog has been around for a long time, people will continue to use
it and there are some things that could/should be re-used. However,
syslog alone is not sufficient for many reasons. So, if you look at
Appendix D of the netconf-event-01 you'll see there is a proposal for a)
re-using some syslog field definitions (semantics) and b) being able to
carry syslog messages within a NETCONF notification. The latter provides
a migration path to/when XML notifications are widely available,
co-existence, etc. 

IMO, notifications in the original charter are not clearly enough
specified to be useful in this debate.

HT: Ok

The first debate I want to have is whether NETCONF should invent a new
event system or adopt/invent NETCONF XML encodings of syslog and/or SNMP
notifications.

HT: There are at least two maybe three parts to this: 
a) the NETCONF protocol extensions 
b) the event framework - this and the previous are within the scope of
the current document 
c) the event types/classes and their content - this is not dependent on
NETCONF but this is a critical part and should be done.

Ideally you wouldn't want client applications to have to support
multiple management protocols. It happens today but I believe the goal
should be to avoid that. If you agree with that then points a and b
above are needed. In addition to that there are shortcomings in both of
the two possibilities you list above. 

The last point (c) is currently not addressed in existing work. syslog
covers some things, SNMP covers others but there isn't a single
specification for event types and their contents. So, I think this work
also needs to be done. I'm not suggesting re-inventing things since
there's much of this already done so existing specifications may be
re-used to generate this new spec. 

Hector

 

Anyone one the list with an opinion, please speak up!

> 
>Hector
>  
>

Andy

> 
>
>-----Original Message-----
>From: Wijnen, Bert (Bert) [mailto:bwijnen@lucent.com]
>Sent: Tuesday, November 08, 2005 11:02 AM
>To: Hector Trevino (htrevino); j.schoenwaelder@iu-bremen.de
>Cc: Sharon Chisholm; netconf@ops.ietf.org
>Subject: RE: Netconf Event Message as Working Group Document
>
>So may I assume you guys are implementing on top of an existing Cisco 
>NetConf implementation?
>
>Bert
>
>  
>
>>-----Original Message-----
>>From: owner-netconf@ops.ietf.org [mailto:owner-netconf@ops.ietf.org]On
>>Behalf Of Hector Trevino (htrevino)
>>Sent: Tuesday, November 08, 2005 18:44
>>To: j.schoenwaelder@iu-bremen.de
>>Cc: Sharon Chisholm; netconf@ops.ietf.org
>>Subject: RE: Netconf Event Message as Working Group Document
>>
>>
>>
>>Hi, that would be various people at Cisco who are interested in 
>>NETCONF and think notification support is needed.
>>Hector
>>  
>>
>>-----Original Message-----
>>From: Juergen Schoenwaelder [mailto:j.schoenwaelder@iu-bremen.de]
>>Sent: Tuesday, November 08, 2005 12:57 AM
>>To: Hector Trevino (htrevino)
>>Cc: Sharon Chisholm; netconf@ops.ietf.org
>>Subject: Re: Netconf Event Message as Working Group Document
>>
>>On Mon, Nov 07, 2005 at 07:43:16PM -0800, Hector Trevino (htrevino)
>>wrote:
>>    
>>
>>>Sharon,
>>>
>>>Agree with your suggestion. We'd like to see this work move
>>>      
>>>
>>ahead in
>>    
>>
>>>the NETCONF WG.
>>>      
>>>
>>Who is "we" here?
>>
>>/js
>>
>>-- 
>>Juergen Schoenwaelder		    International University Bremen
>><http://www.eecs.iu-bremen.de/>	    P.O. Box 750 561, 
>>28725 Bremen,
>>Germany
>>
>>--
>>to unsubscribe send a message to netconf-request@ops.ietf.org with the
>>    
>>
>
>  
>
>>word 'unsubscribe' in a single line as the message text body.
>>archive: <http://ops.ietf.org/lists/netconf/>
>>
>>    
>>
>
>--
>to unsubscribe send a message to netconf-request@ops.ietf.org with the 
>word 'unsubscribe' in a single line as the message text body.
>archive: <http://ops.ietf.org/lists/netconf/>
>
>
>  
>

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