RE: Verbs or data model [was: Session reuse]

["Sharon Chisholm" <schishol@nortel.com>]

hi

I was driving home last night thinking about how of all the notification
receiver applications I've worked on over the years only one attempted
to perform automatic notification subscription. In thinking about why
this was, aside from the complexity issue which I've already discussed,
there is the support issue. Not all devices supported the MIB in SNMP.
You could argue again that this was the complexity issue, but I think it
also goes to the fact when we delegate everything to the data model,
implementations have a difficult time figuring out which are the
important bits to support or else start to support a proprietary chunk
of data model which they think is better/simpler/cooler instead. I think
this deviation is more obvious with verbs, assuming of course we have a
finite number of them.

So, verbs signal that this 'thing' is important so you should support it
and support it exactly this way. It's good for interoperability. I am
hoping there are other ways to solve this as well, since I am sure there
will be key bits of data model we will want people to support.

Sharon

-----Original Message-----
From: owner-netconf@ops.ietf.org [mailto:owner-netconf@ops.ietf.org] On
Behalf Of Chisholm, Sharon [CAR:ZZ00:EXCH]
Sent: Monday, June 19, 2006 4:09 PM
To: Netconf (E-mail)
Subject: RE: Verbs or data model [was: Session reuse]



<Andy>
Some people (including myself) believe that passing all
of the notification delivery parameters each time the
session restarts is inefficient and bad SW design.
  - It also forces the manager to store all the parameters
    for every device, instead of giving them the option to
    use agent NV-stored data.
  - It forces all the NMS apps to share or duplicate this data,
    instead of having the option of storing it on the agent. </Andy> Two
points on that:

1) I need to store a copy of my desired notification subscription
anyways because if configuration  doesn't exist I need to create it.
2) I am likely to be asking for the same information from all of my
devices. If they are stored on the device I then need to change them on
all of the devices. Much more work have to update those and then worry
about whether some other fool has the subscription configuration locked
or will step on my changes later on.

<Andy>
  - It forces the NMS and agent to replicate filter expressions
    instead of allowing them to be shared across applications,
    sessions, or even subscriptions.
</Andy>
You can use named profiles if you want to.

Sharon

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