Yea I think some sub-areas for data models is a possible approach.
I must agree with the underlying sentiment of your comment. I guess I
might say it straight from my perspective. We attended this Netconf
session to see if we should think about contributing the current data
model work from various session based and config based efforts in our
OS's but given that the working group was a two party punching match
and the side group (I did not attend) went off on inventing some
replacement data modelling langauge because of some implementation
choices of Netconf filtering....
It does not look like we can have the discussions here.
-Ric
Andy Bierman wrote:
Hi,
I translated the syslog message format as defined
in draft-ietf-syslog-protocol-19.txt into XML encoding
for better subtree and Xpath filtering, as well as a TEXT encoding.
I doubt we can standardize any content given the
level of disagreement over every little detail.
But we still need to keep throwing darts at data models
until there is more agreement.
Simon asked an important question at the last IETF meeting:
"What do you think the NETCONF data model should look like"?
Debating the finer points of data modeling language design is
a nice academic exercise. Debating what the XML on the wire
looks like is much more important right now.
I am including the XSD and the NCX source file.
I hope the documentation is readable in the module header.
This is an attempt at a direct translation of syslog-19 message format.
If there is any interest, I will write up an I-D.
Andy
_______________________________________________
NGO mailing list
NGO@ietf.org
https://www1.ietf.org/mailman/listinfo/ngo
|