RE: NETCONF Notifications: Consensus Points

["David B Harrington" <dbharrington@comcast.net>]

Hi,

I personally prefer "notification" to "event message" because I would
like to see consistency in the terminology used for IETF O&M
protocols. There seem to be three variations - notification, event
notification, and event message; everywhere event notification is
used, the same document also refers to it simply as a notification,
and no document seems to identify what other type of notification
besides event notification is possible. 

Here's my research on the use of "notification" vs. "event message" in
O&M documents:

"notification" - SNMP (rfc3413), IPFIX requirements (rfc3917),
Diameter (rfc3588), Syslog (rfc3164), Opsec Practices
(draft-ietf-opsec-current-practices-02)  

"event message" - Syslog (rfc3164), netconf
(draft-chisholm-netconf-event-01.txt) 

Widening this to a search of RFCs which use notification or event in
their title, and checking for "notification" or "event message" in the
text of the document:

"notification" - Simple New Mail Notification (rfc4146), Requirements
for IPP Notifications (rfc3997), Internet Printing Protocol (IPP):
Event Notifications and Subscriptions (rfc3995), The SPIRITS (Services
in PSTN requesting Internet Services) Protocol (rfc3910), A Presence
Event Package for the Session Initiation Protocol (SIP) (rfc3856),
Message Disposition Notification (MDN) profile for Internet Message
Access Protocol (IMAP) (rfc3503), An Extensible Message Format for
Delivery Status Notifications (rfc3464), Simple Mail Transfer Protocol
(SMTP) Service Extension for Delivery Status Notifications (DSNs)
(rfc3461), Session Initiation Protocol (SIP)-Specific Event
Notification (rfc3265), The Addition of Explicit Congestion
Notification (ECN) to IP (rfc3168), An INVITE-Initiated Dialog Event
Package for the Session Initiation Protocol (SIP) (rfc4235), Session
Initiation Protocol (SIP) Extension for Event State Publication
(rfc3903), etc.

"event message" - 

Nuff said?

David Harrington
dbharrington@comcast.net




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