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

Re: [NGO] syslog content for NETCONF stream

Romascanu, Dan (Dan) wrote:

I am quite sure that there is enough interest to write an I-D. In the
current phase of discussions and especially until a broader consensus is
reached on the data modeling language it helps to document the
contributions. It may also happen that in a first phase we shall rather
publish Informational or Experimental RFC documents rather than going
directly to standards track. In any case, I-Ds are good. 

I should be clear that I would not be including the NCX module
in the draft.  I just included it because the header is easier to read
without character entities in the examples.

The real XSD would have a substititionGroup defined for the sdparam
element, instead of type 'any'.

I think we would have better luck discussing data models
instead of data modeling languages.  If you don't know
what the XML on the wire should look like, then you don't
need a data modeling language yet.  A DML only helps if
you already understand the data model you are designing.



Dan


Andy





-----Original Message-----
From: Andy Bierman [mailto:ietf@andybierman.com] Sent: Friday, April 06, 2007 7:54 PM 
To: Netconf (E-mail)
Cc: NETCONF Goes On
Subject: [NGO] syslog content for NETCONF stream

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







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