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

Re: Issue 2.3) Notification types

To: Andy Bierman <abierman@cisco.com>
Subject: Re: Issue 2.3) Notification types
From: Rob Enns <rpe@juniper.net>
Date: Fri, 12 Dec 2003 11:49:55 -0800
Cc: netconf@ops.ietf.org
In-reply-to: <4.3.2.7.2.20031202155201.0272fcc0@fedex.cisco.com>
Mail-followup-to: Andy Bierman <abierman@cisco.com>, netconf@ops.ietf.org
References: <4.3.2.7.2.20031202155201.0272fcc0@fedex.cisco.com>
User-agent: Mutt/1.4i

On Tue, Dec 02, 2003 at 03:52:37PM -0800, Andy Bierman wrote:
> Should NETCONF define specific notification formats?

We should use companion documents for notification formats.

> If so, should RFC 3195 (Reliable syslog) be supported?
> Should other notification schemes be defined?
> 
> 
> --
> 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/>

References:
- Issue 2.3) Notification types
  - From: Andy Bierman <abierman@cisco.com>

Prev by Date: Re: Issue 2.2) Notifications Proposal
Next by Date: Re: Issue 2.4) <notification> wrapper
Previous by thread: Issue 2.3) Notification types
Next by thread: Issue 2.4) <notification> wrapper
Index(es):
- Date
- Thread