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

RE: Named Profiles for notification configuration (unofficial issue #16)



hi

<Andy>

We don't have opaque string data models.
We have vendors defining explicit XML data models
in their own namespace.  There is a difference.
</Andy>

Ah. So, I guess we forgot to explicitly specify that it is necessary to
specify some data model for the named filters. That is why it is the
same issue. If they remain in the update, we shall add this
clarification.


<Andy>
I have provided an extensibility mechanism -- IANA registration.
Each event-type is itself a data model with implementation
requirements in the agent.  They should be registered with IANA
and be independent of the document this WG is chartered to create.
</Andy>

I'm confused. So, the proposal in the internet draft is that
notifications are defined in the data model, but are you proposing a
design alternative or suggesting that working group consensus has
already been reached and this is going to be done in another way?

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