Re: Real Notification Requirements

["Tom Petch" <nwnetworks@dial.pipex.com>]

Plugging in a new blade.  Most of the network boxes I deal with are chassis with
hot-pluggable blades.  When  a new blade is plugged in, or an old one removed,
then I want a notfication so that the other party has a chance to amend the
configuration.

Tom Petch



----- Original Message -----
From: "Andy Bierman" <ietf@andybierman.com>
To: "Netconf (E-mail)" <netconf@ops.ietf.org>
Sent: Monday, March 27, 2006 5:48 PM
Subject: Real Notification Requirements


> Hi,
>
> This new thread is for people to articulate use cases
> to support functional requirement requests.
>
> Translation: What is the developer or operator doing now, and
> how will it change to something great and wonderful because
> of this new feature?
>
> Let's try some top-down design, since ad-hoc design isn't
> going so well.
>
> I believe there is consensus so far for 2 uses of notifications
> in the NETCONF protocol:
>
>
> Content Layer Requirements
> --------------------------
>
> C1) 'Full XML' or 'XML Wrapper' notification for SYSLOG content
>
> C2) NETCONF configuration change notification
>
> C3) ???
>
> Andy


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