RE: Re: [psg.com #471] Expert review comments on draft-ietf-ipcdn-doc sisevent-mib-03

"Jean-Francois Mule" <[email protected]>
Newsgroups gmane.ietf.ipcdn
Message-ID <[email protected]>
Eduardo wrote:
> My preference will be to remove just the EvText with the 
> clarification in OSSI spec as mentioned above and leave EvId 
> and EvLevel as part of the notification definition.

Just to be clear, your proposal is to keep event id & event level but remove the EvText (via a DOCSIS spec change?).

You also mentioned:
> Perhaps an ammend text to Annex D will be required to 
> indicate its usefulnes "Additional vendor specific text MAY 
> be added to the end of the event text." that is only 
> propagated to local-log and syslog messages.

 Are vendors doing this today? If yes, would the spec change cause them to treat local-log, syslog and SNMP reporting differently?  Any comments from vendors on this?

Jean-François 
  

> -----Original Message-----
> From: Nakanishi Greg-MGI8179 [mailto:[email protected]] 
> Sent: Tuesday, August 03, 2004 9:02 AM
> To: [email protected]
> Subject: FW: [ipcdn] Re: [psg.com #471] Expert review 
> comments on draft-ietf-ipcdn-doc sisevent-mib-03
> 
> 
> Forwarding comments from Eduardo on Event Notif MIB issue.
> 
> greg
> 
> -----Original Message-----
> From: Eduardo Cardona [mailto:[email protected]] 
> Sent: Tuesday, August 03, 2004 2:50 AM
> To: Nakanishi Greg-MGI8179; Matthew Schmitt; Greg White
> Cc: Jean-Francois Mule
> Subject: RE: [ipcdn] Re: [psg.com #471] Expert review 
> comments on draft-ie tf-ipcdn-doc sisevent-mib-03
> 
> 
> Greg, 
> 
> The Event messaging structure in DOCSIS rely in EvText for 
> the case of local-log and syslog messages. 
> In general EvText is variable depending upon the parameters 
> <Pn> defined in OSSI spec, not without notice that the 
> Parameters <Pn> are already vardinds from the 
> NOTIFICATION-TYPE definition It means that from the surface 
> there is no loss of information by suppressing the EvText varbind. 
> - Vendors have the option to add extra text to EvText, which 
> will be lost for the case of Notifications, 
> Perhaps an ammend text to Annex D will be required to 
> indicate its usefulnes "Additional vendor specific text MAY 
> be added to the end of the event text." that is only 
> propagated to local-log and syslog messages.
> 
> 
> In the case of EventId, It is also redundant if the lookup 
> table is present in the application but I believe that a 
> mechanism for notification filtering at the application is 
> well suitable by using Notification OID and EventLevel, 
> without the need of other elements like look-up tables
> 
> My preference will be to remove just the EvText with the 
> clarification in OSSI spec as mentioned above and leave EvId 
> and EvLevel as part of the notification definition.
> 
> Thanks
> 
> Eduardo
> 
> <-- deleted e-mail trail -->
> 
> _______________________________________________
> IPCDN mailing list
> [email protected]
> https://www1.ietf.org/mailman/listinfo/ipcdn
> 
>
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.