Hi,
OK, I'm reviewing today. :)
On Thu, 21 Nov 2002, Jon Callas wrote:
> On 11/21/02 3:11 AM, "Albert Mietus" <[EMAIL PROTECTED]> wrote:
>
> > ** The TAG is defined to be ending ('MUST')with a _colon_.
> > This wrong, as rfc3164 defines it can end with a _space_
> > Adv Rewrite: it terminates with any not alfanum char.
> >
>
> Hmmm. Let me look.
We discussed (a long time ago) that the TAG should be included in the
HEADER rather than in the MSG for people writing code. See the 3rd
paragraph in Section 2. This should mean that the TAG should be able to
contain things like:
syslog[1234]:
Since the next character may, or may not be a space, then we need some way
to define a terminator to the field. I'll suggest that the colon stay.
That would still allow things like:
syslog[1234]:Here is my syslog message
That does bring up a point, however. In "traditional" syslog messages,
there is nothing between the ":" and the message itself in many cases.
Should there be a space between the ":" and the Signature Block, and the
Certifiate Block in the syslog-sign messages? If so then a Signature
Block would look like:
syslog[1234]: @#sigSIG 0111 ...
and the Certificate Block would be:
syslog[1234]: @#sigCER 0111 ...
Thanks,
Chris
