[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: [Syslog-sec] syslog-protocol and RFC 3164 (BSD Syslog)
Sharon,
> This seems more of a rehash of RFC3164 than explaining the
> relationship
> between the two specifications to me.
I thought this was at least one of the most important things of the
relation. Actually, this compatibility issue was what drove the header
format.
> I was thinking more
> along the lines of
> text currently buried in A7.
>
> " Implementors of earlier syslog implementations may note that
> SENDER-NAME, together with SENDER-INST is similar to the TAG field
> described in [12]. The SENDER-NAME is without the instance
> description that often could be found in TAG while SENDER-INST is
> just that instance description."
>
I agree, I can add this similarities. I'll see that I compile a list,
which will probably be very short.
> In addition, I don't think keeping the main body of the
> document short by
> moving content to the appendix a generally useful strategy. I think it
> detracts from the readability of the specification. I know
> other standards
> bodies like moving non-normative content to the appendix, but
> I believe
> using RFC2119 type language is a more typical method of
> delineating between
> normative and informative discussion within the IETF.
Actually... I don't like this approach either. HOWEVER, there was a
really looooooong discussion on the WG and it was the concensus that we
should keep the normative body very short. I didn't like it but I
accepted that concensus. I restructured the whole document so that only
the bare essentials are left in the "core document". Of course, we can
undo that change, but I think we would just go through the same cycle
again. So for the sake of getting this ready, I would prefer to stick
with the current approach, even though some of us might think it is
sub-optimal.
Rainer
_______________________________________________
Syslog-sec mailing list
Syslog-sec@www.employees.org
http://www.employees.org/mailman/listinfo/syslog-sec