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

Re: notification motivation and requirements

To: "David T. Perkins" <dperkins@dsperkins.com>
Subject: Re: notification motivation and requirements
From: Juergen Schoenwaelder <j.schoenwaelder@iu-bremen.de>
Date: Wed, 29 Mar 2006 23:03:18 +0200
Cc: netconf@ops.ietf.org
In-reply-to: <Pine.LNX.4.10.10603290922350.26409-100000@shell4.bayarea.net>
Mail-followup-to: "David T. Perkins" <dperkins@dsperkins.com>, netconf@ops.ietf.org
References: <Pine.LNX.4.10.10603290922350.26409-100000@shell4.bayarea.net>
Reply-to: j.schoenwaelder@iu-bremen.de
User-agent: Mutt/1.5.10i

On Wed, Mar 29, 2006 at 09:28:11AM -0800, David T. Perkins wrote:
 
> *) notifications to report unexpected consequences of
>    a configuration change

How does a device distinguish between expected and unexpected
consequences of a configuration change?

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

Follow-Ups:
- Re: notification motivation and requirements
  - From: "David T. Perkins" <dperkins@dsperkins.com>

References:
- Re: notification motivation and requirements
  - From: "David T. Perkins" <dperkins@dsperkins.com>

Prev by Date: Re: Notifications with config change
Next by Date: Re: Why are we doing netconf?
Previous by thread: Re: notification motivation and requirements
Next by thread: Re: notification motivation and requirements
Index(es):
- Date
- Thread