Anton & all:
comments to just to those things that I think I need to comment on - the
others are snipped out (basically agreement from my side).
> > > > - esay human interaction - not just reading but also (telnet)
> > > > crafting messages
> > > > (I couldn't envision troubleshooting SMTP conf
Rainer & all:
Let me comment on something...
> > > - esay human interaction - not just reading but also (telnet)
> > > crafting messages
> > > (I couldn't envision troubleshooting SMTP configs without
> > > the ability to
> > > telnet SMTP commands)
This is analogy is not quite kosher IMO.
Hi
You might want to read RFC3535, the Overview of the 2002 IAB Network
Management Workshop and draft-jones-opsec-05.txt.
The focus of the workshop was largely on configuration but many of the
observations would also apply to a protocol like syslog.
In particular during the workshop, in the opse
ore we get more comments from
others ;)
Rainer
> -Original Message-
> From: Anton Okmianski [mailto:[EMAIL PROTECTED]
> Sent: Friday, April 23, 2004 5:31 PM
> To: Rainer Gerhards; [EMAIL PROTECTED]
> Subject: RE: binary fields in syslog
>
> Rainer & all:
>
&g
Rainer & all:
I see your concerns, but I don't think -protocol and -transport have
to either both do a complete binary or neither. For one, you can think
of them as protocols which operate at different layers of the OSI
model.
Keep in mind that we already do "binary" in -protocol because we
suppo
