RE: Size matters was Re: notification charter proposal

["Rainer Gerhards" <rgerhards@hq.adiscon.com>]

A comment from a lurker on this list. I have been working on syslog for
the past 3 years and been through the size discussion several times. I
have NOT read all documents of the NETCONF WG.

> I raised size because there are references appearing on the 
> list calling for
> something syslog-like and size has been an issue with syslog 
> that has not been
> satisfactorily resolved.  syslog unearthed two contrasting 
> viewpoints, one that
> messages should not exceed 2k or even 1k, the other that 64k 
> should be supported
> (for at least one application).

In my point of view, this WG is in a far better situation than the
syslog WG. The core problem with syslog is that it is strictly simplex,
without any way that a receiver could tell the sender anything. So in
syslog, there is no way a sender knows what size of message the receiver
can process. If that would be known, the issue would be considerably
less complex, as the sender could take appropriate measures (like
stripping out non-essential information, sending multiple notifications,
...).

If my understanding of NETCONF is correct, NETCONF has such
capabilities. As such, it should be in a much better position to handle
the size issue.

Rainer Gerhards

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